[FEATURE REQUEST] - Command Line startup arguments (--game, --profile)

[jahshuwaa]

What problem does the feature request solve? Adding command line arguments to any number of custom shortcuts would allow the user to bypass Game selection, Profile selection, or both.

Example mock-up (optional) r2modman.exe --game=Valheim --profile="MP Server modset"

Additional information (optional)

• --game value must be present and valid for --profile to be parsed

• if --game value is invalid or not supplied, --profile value is discarded

• invalid or empty parameter values fall back to the respective selection screen

• this feature could be added in stages if the current startup sequence / network data fetch makes it difficult to load all the way through to a Profile. That is to say, add the --game parameter first, and continue to require manual Profile selection. Then add the --profile parameter later, perhaps

[cedws]

I would also like to request a parameter to override the data directory, so something like --data-dir. This would make the program easier to package manage.

[MarSond]

I would really love this

Combined with a "create shortcut on desktop" to start current game+profile modded

[kevindevm]

yes, this please

[paulosincos]

I came to suggest exactly what this request asks.

Arguments for game, profile and data-dir.

[gamrtiem]

hi hello can yog add this pretty please !!!!! would be nice to launch profiles through steam skipping the gui !!!!!!!!!

[21Joakim]

I would love if there was some basic support for command line options, I want to make it as easy as possible for my friends to import a profile from a code and launch into it automatically. This way I can just give them a single command to run and avoid having to walk them through what to do as that is time consuming and takes away from the time we have to play games.

On-top of the already proposed --game and --profile options I suggest another one for importing a profile, --import, it would probably be best if it auto-detects whether it is from a code or file but if that's not ideal it could be separated into --import-from-code and --import-from-file (mutually exclusive).

Example usage r2modman.exe --game="Lethal Company" --profile=MyAwesomeModpack --import=9a0e567d-5a77-42ee-bb56-91b68af8bcff

Proposed behaviour

1. It will use the --profile option to determine which profile to import to, if it is not specified it will use the name of the profile from the code
2. If a profile with that name already exists it can either
   1. Replace it without warning
   2. Not do anything unless a new --overwrite option is also specified. I think this would be preferable for my use-case as I could simply give my friends the following command line r2modman.exe --game="Lethal Company" --import=9a0e567d-5a77-42ee-bb56-91b68af8bcff and it would install it if it doesn't exist otherwise just select the existing one, reducing the friction
3. After the profile has been imported it will automatically be selected

[SirenGlitch]

Glad I went looking for this, any news on efforts towards it?