Skip to content

Game Command Line Arguments

360900 edited this page Aug 2, 2026 · 2 revisions

Steam uses different sources for game command line arguments.

  • those provided via Steam Launch Options are user-customizable and empty by default
  • those provided via Appinfo are "hardcoded" (upstream) and can't be modified (or regularly even seen) by the user

TinkerGame not only adds another option for directly customizing additional command line arguments, GAMEARGS, in the Game Menu, but it also "unlocks" the "hardcoded" Appinfo ARGUMENTS and makes them configurable and deletable via HARDARGS in the Game Menu. This is accomplished by writing the ARGUMENTS, when found in the current command line, into the HARDARGS only when HARDARGS is nope (default). To disable the HARDARGS completely, they can be set to none, or the variable can be emptied (it will then be stored as none as well). The original, unmodified arguments can always be accessed from the options dropdown menu.

The Steam Launch Options command line arguments cannot be modified from within TinkerGame, as that would make no sense, but they are available as a read-only entry SLOARGS in the Game Menu.

To enable the "unlock" mode, the option SORTGARGS in the Game Menu needs to be enabled. The option can also be activated via Steam Collection.

By default this is disabled, as the function needs further testing. For example, if Steam offers an option menu when starting a game, it likely has multiple different arguments. TinkerGame only reads the first one found, and it is possible that it gets falsely categorized as a SLOARGS argument, in which case the argument could not be disabled. This could be overridden by allowing a user-defined ARGUMENTS variable in the Game Menu, which might be added later.

Clone this wiki locally