Quake c - server and client controls tutorial - qc

For reference: Cataboligne.org we will be looking at the section of the quake c manual at that link. You can make a local copy - I did a scroogle search and couldnt even find it. (There are other manuals, but that is my favorite.)

These are the two quake c instructions referenced:

stuffcmd (entity client, string text);

client = player that is to receive the command

text = text of the command, ended by \n (newline).

Send a command to a given player, as if it had been typed on the player's
console. Don't forget the \n (newline) at the end, otherwise your command
will not be executed, and will stand still on the console window.

localcmd (string text);

text = text of the command, ended by \n (newline).

Execute a command on the server, as if it had been typed on the server's console.

*** Important NOTE: these two pieces of code are not interchangeable!

The first - stuffcmd - is used to send console commands to a client connected to the server. There are any number of variables server code might want to change, however, the most frequent use is "bf\n" - flash the screen.

The second - localcmd - tends to be used for code controlled server admin type functions such as loading new maps, and changing control vars.

In both cases the engine interprets the text as if typed and a terminator <\n> char MUST be sent, or the command will languish in the console buffer.

This segment is something for the coder to keep in mind - I just ran into this during development. There is a .cfg file that gets executed based on in game action. And it wasnt working for the network client. I checked and sure enough, I had threw in localcmd when I wanted stuffcmd.