Talk:SiN and SiN: Wages of Sin/Game Mechanics and Glitches

General Movement

Boosts

Weapons

NPCs

Health, Armor, Damage

Drops table

Optimizations

Saving and loading

General

Using the console

Useful Aliases

Glitching/Experimental Stuff

Unsolved Mysteries

Level-specific (but not category-specific) notes:

Side notes

I'm trying to get the shortcut command parameters to do what I want: I just can't get it to happen consistently. In fact it only set the player and skipped the logon menu once and persistently failed ever after. Editing the autoexec might be more reliable?

• Any ideas on what might be going wrong? If the parameters are in fact there when you start the shortcut, I can't think of any reason why it shouldn't just work. How does your shortcut look? Unfortunately, autoexec.cfg is not a "replacement" for shortcut parameters, see below.
• Not every command or cvar will have the same effect, compared to putting them directly in the shortcut. For example setting player in the autoexec does not have any effect, and +menu_main will not skip the intro videos if set in the autoexec. This is why I prefer using both an autoexec file as well as the shortcut. It's also just quicker for me to edit the SiN shortcut on my desktop if I want to practise a specific map.
• The order of execution seems to be: shortcut -> default.cfg -> autoexec.cfg -> config.cfg. This means that the next one will potentially overwrite values of the prior one. defaultm.cfg and defaultk.cfg are only executed when you click on "Restore default keyboard only configuration..." or "Restore default keyboard and mouse configuration..." in Player Controls, so they can be ignored (or deleted). To give an example; if you exit the game while crosshair is set to 0, then it simply won't matter what you set it to in your shortcut, default.cfg or autoexec.cfg: If you start up the game again, config.cfg will be loaded last, setting crosshair (back) to 0, overwriting the value set in any of the other sources. It seems pointless to use both default.cfg and autoexec.cfg, I think both are always executed, so you might as well delete/empty one of them.