Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Add CLI arguments for autostarting the proxy on launch #535

Open
Lerohi opened this issue Dec 28, 2024 · 1 comment
Open

[Feature] Add CLI arguments for autostarting the proxy on launch #535

Lerohi opened this issue Dec 28, 2024 · 1 comment

Comments

@Lerohi
Copy link

Lerohi commented Dec 28, 2024

It would be really useful to be able to automate the starting of the proxy with command line arguments.

Example usage:
On Windows, open cmd in SWEX working directory and type SWEX.exe --start_proxy_steam or SWEX.exe --start_proxy_remote

Expected behaviour:
SWEX should launch normally and try to start the proxy in steam/remote mode automatically without the user having to interact with the respective UI each time.

This would allow to fully automate the process of starting SWEX when SW is launched via Steam. This setup would include a custom bat script using this functionality (see above commands), which gets called via Steams Game Launch Options through the %COMMAND% flag. This would look like this: custombat.bat %COMMAND%

@Xzandro
Copy link
Owner

Xzandro commented Dec 28, 2024

This should be possible already.

if (process.env.autostart) {
Probably have to adjust the starting script to set that to true.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants