-
Notifications
You must be signed in to change notification settings - Fork 127
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
Remove ns_startup_args*.txt
functionality
#507
Comments
I think enough time has passed and we should finally do this. |
The only problem I have with this, is it's now more difficult to have a mod manager be able to change the launch options. As, unless it's launching the Unless I'm mistaken, and there's some easy way to do this? |
See how FlightCore does it |
According to this, FlightCore simply doesn't support changing launch arguments. Unless thats outdated? |
|
Ah, I stand corrected, I wasn't aware you could add launch arguments to |
bump |
Why
GetCommandLineA
to support these.txt
files, but before doing so we already read the commandline meaning some args dont work in the .txt.strstr
ingGetCommandLineA
can lead to false positives with arguments that start with the same prefix.What
tier0.dll
exportsCommandLine()
with which we can check the command line. We already have this mapped out and use in some cases so this is just improving code consistency.How
Print warning, discord announcement ?
Add support to directly passing arguments to the process when creating it
Patch versions mainly serve for small fixes and small features, this is a pretty big change in behavior
The text was updated successfully, but these errors were encountered: