Receiving the value of a cvar from a client

[Lathain Valtiel]

I'm horrifically new to Q3 coding, but yeah.

 

Let's say for the sake of argument that I made a new cvar named 'cg_string'.

 

How do I make it so that I could get clients to send the value of 'cg_string' to other clients for use in certain client-side functions? You know, similarly to how we receive the R, G, and B values of their clothing or the color of their saber?

[stubert]

one of the cvar flags will keep it updated to the other clients

 

it's like CVAR_CLIENTINFO or some ****

 

 

you'll also have to add some other **** too but it's been to long for me to remember

 

someone else will know

[ensiform]

clothes color is already handled in ClientUserinfoChanged...

 

char_color_red, char_color_green, char_color_green.

 

and its CVAR_USERINFO not CVAR_CLIENTINFO

[razorace]

Well, it's not that simple since client cvar data isn't directly communicated between players. Its gotta be processed by the server and then added to the player's configstring stuff. Look at the rgbsaber code in the OJP code to see an example of how it's done.

 

In addition, code3arena is a great resource for cvar related stuff.

[ensiform]

by the way razor, that client fix for buffer overflow for rgb sabers also applies to the UI, i believe you forgot to fix the UI code.

[razorace]

buffer overflow? Where at? Which file/line number?

[ensiform]

See rv1.36 for cg_players.c

 

That must also be applied for ui_main.c and i think some stuff in ui_saber.c needs cleaning up too.

[razorace]

Ok, I added the fix to the UI_ParseScriptedSaber function, but I'm not sure what you mean by the ui_saber.c stuff.

[ensiform]

might be easier to discuss this on aim.

[razorace]

good point. I'll try to catch you the next time you're online.