News | Forum | People | FAQ | Links | Search | Register | Log in
General Abuse
Talk about anything in here. If you've got something newsworthy, please submit it as news. If it seems borderline, submit it anyway and a mod will either approve it or move the post back to this thread.

News submissions: https://celephais.net/board/submit_news.php
First | Previous | Next | Last
Quake Command Line 
I would like to know the significance of the - and + in a quake command line 
Quake Command Line 
I'm not sure, but I think "+" is used for commands or cvars that could also be typed in console, for example quake.exe +exec imba.cfg +skill 2 +map start.

While "-" is used for command line parameters that are used only once for the launch of the executable, for example quake.exe -winmem 16 -listen 8 -nocdaudio.

Most sourceports of the last decade however added a few of the command line parameters as console commands that can be used when the game is running, for example -game parameter can be used as "game xxx" from console to switch mods without exiting and restarting the executable again. Same thing for -hipnotic and -rogue command line parameters, the sourceports recognize the switch to mission packs if you use "game hipnotic" or "game rogue" in the console. 
 
commandline:
`-foo` - stuff the engine has to explicitly check for at startup.
`+foo` - stuff the engine inserts into its command buffer to execute like any other command you might type at the console.

Note that Quake2-onwards (and thus also FTE) recognises `+set cvar value` (and +seta) as special and ensures those named cvars are set even before the engine can register them, which allows such cvars to affect initialisation before configs can even be read. These cvars will then ALSO be executed via the cbuf which will replace any config.cfg values for them (which a -set would fail to do, hence the need for such a hack).

Note that many engines will accept either -game and +game/+gamedir. -game will force the engine to initialise that specific gamedir from the start, while +game[dir] will execute configs from your id1 gamedir THEN try switching to the new gamedir after, which may result in your quake.rc/default.cfg/autoexec.cfg values getting mixed up between mods.
So you probably want to stick with -game.
Note that 'game hipnotic' or 'game rogue' commandline parameters are not special, and thus will probably not tweak the network protocol nor enable the mission-pack-specific huds.


binds:
`+foo` - will issue a `-foo` release event when the key is released.
`-foo` - not special, treated like any other bind.

Note that `bind a "+forward;+back` will insert `-forward;+back` when released, which is often not what was intended. create a pair of aliases to work around that. 
 
Although in Quakespasm and its derivatives, and probably several other modern Quake engines too, if you try to activate hipnotic or rogue mod folders using the "-game" cmdline option or the "game" console command, those mod folders _are_ treated specially. The program will enable the engine code paths for the correct missionpack as if you had done "-hipnotic" or "-rogue" on the cmdline. This was to help keep people from shooting themselves in the foot since it's pretty clear what they're trying to do in those cases... although it does muddy the water about how all these ways of doing things are meant to behave.

(Similarly, activating the "quoth" mod folder is special-cased to implicitly activate "-hipnotic" as well.) 
Episdoe 4 Replacements? 
Fuck Sandy 
#31938 
try Nehahra (without using nomonsters 1) 
Tremor E4 
 
1 post not shown on this page because it was spam
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors.