the "cmdline" cvar

[szo]

Does anyone know why the "cmdline" cvar is marked as "server" and is sent to the client upon CCREQ_RULE_INFO (e.g. upon the "test2" command)? Does anything out there really relies on this cvar's value's presence in the queries?
I think sending the command line with which the server is launched is evil and the client shouldn't have any right to know it. If there isn't anything that rely on that (I myself don't), I plan on removing its server flag.

[Baker]

Quakeworld and Quake II don't share that information.

Likely served as kind of a support mechanism for "Why isn't my server working?" to validate server setup. The info conveyed like the executable, the -game mod running, the maxplayers and so forth.

GameSpy used to have some sort of game tab that would use the info so you could group Quake 1 servers by mod running, which would have needed to utilize that info but that ages ago.

Killing it or leaving it won't make a difference.

[szo]

The executable name may very well has path information which many people (myself included) may not like to share.
Killing it should be the best IMO.

[mh]

No reason to just not add argv[0] to the cvar then is there?

My best guess is that it's a remnant from an earlier version of Quake, but I've really no idea. I guess it's worth commenting out, doing some testing on, and seeing what breaks.

[szo]

Well, I went ahead and removed the server flag from it in quakespasm as of svn r568. Will possibly release v0.85.6 with that setting. If someone screams (which I doubt very much), then I'll think about it.