KRIMZON_SV_PARSECLIENTCOMMAND

[Cobalt]

[Spike]

cmd foo
->"foo"

remember that its parsed on the server, and the server doesn't see all the cvar etc commands the user enters. it only sees the commands that are actually sent to it.
'cmd' sends its arguments as a string, allowing you to send arbitary client commands (eg: csqc can localcmd("cmd foo\n") to send messages to the server).
say, say_team, kill, etc, commands automatically forward themselves to the server too, as client commands.

that test code you pasted is basically a no-op. add a print so that you know something is happening. or just return instantly and puzzle over why you no longer have a name set, etc.

[Cobalt]

[Cobalt]

Ok did more tests...seems when a valid command is entered, that viod () gets called, IE: color 5 2 for example. I was misunderstanding the operation as if you could add new commands , but it seems not to be able to do so.

[Spike]

clc_stringcmd is your clientcommand client-to-server message, containing a string.
think of it as a reverse stuffcmd. instead of the server asking the client to do things, it is the client asking the server to do things (like change its name). obviously, you don't have full console access with it, but the ssqc is allowed to see/block/intercept/change the text of the command.

if you do not define that function, the engine will internally treat it as if you defined it as:
void(string s) SV_ParseClientCommand =
{
clientcommand(self, s);
};

which basically causes the engine to use its normal clientcommand handler to handle the command.
as the command is just a string, you need to tokenize (ie: split up into tokens) the command string (aka: s) in order to see the first token and thus what the command is actually asking the ssqc/server to do.
tokenize says how many tokens there were, while argv gives you the text of each token.
you can actually call clientcommand from anywhere, so clientcommand(self, "say hello world"); will of course make the server think that the client wanted to say hello to the world.
so you can use it to block colour changes by noticing that its a colour change command and just ignoring it. and you can directly change player colours by using clientcommands instead of stuffcmds - basically have the server update colours instantly instead of bouncing the command off the client and hoping it doesn't try cheating.

remember, you can always stuffcmd(player, "alias hello \"cmd hello\"\n"); then when the user types 'hello' at the console, it fires off a client command to the server and the ssqc can handle it. this works in all clients, even vanilla, both nq and qw. actually handling it properly in the ssqc is where you need the extension.

[Cobalt]

Interesting, gonna play with it later. One thing I did was put a bprint in the void so I know when its called, and when the player is dead, its calling the function like once per second. I thought maybe a stuffcmd would be giving it a false positive, but I'm not stuffing when player is dead anymore than during regular play. It does not seem suceptable to stuffcmds in any way it seems.

[Cobalt]

Lets see, could we use this to have the server execute a changelevel? If I type in E1M2, it does a localcmd of changelevel e1m2 ?


UPDATE:

Ok, still confused by this function. I placed it in Client.qc at the very bottom - does it matter? Anyway, I put a brpint inside to know when its being called, and its only being called during the intermission, pressing tab (showscores) or when dead.... ? It seems to detect when I type in the color command with arguements like color 5 9 , then it will perform the assigned clientcommand......but seems its also performing the color command as well.


Ok, I found this link which explains you have to use "cmd" as a prefix on your console commands:

http://quakewiki.org/wiki/KRIMZON_SV_PARSECLIENTCOMMAND

Now its starting to make more sense.

[Cobalt]

@Spike:

I also noticed during my tests that the client sends a string : "pings" when tab is pressed.

I dont seem to able to declare an exact alias type command with this unless its prefixed by : "cmd" first

IE: cmd [ string ]

Then you parse whatever that string is suppose to do thereafter.

[Spike]

what? you want all console commands like +left etc to bounce off the server before they're executed on the client? that would be laggy as hell.
also, the quit command would be quite exploitable.

[Cobalt]

Ok made some headway with this function thanks to Spike.

Next issue, I want to intercept the "c" string like its doing and identify the "color" command that the client is sending to the server. So far I have it logging to the console something like this when the client connects:

^7 ‚ Typed: name Player
^7 Player‚ Typed: color 6 11

What I want to do is stof(6) in the color string and work with it localy. I suspect we use argv or something but not sure?

[Spike]