// playerState_t is the information needed by both the client and server to predict player motion and actions
// nothing outside of pmove should modify these, or some degree of prediction error will occur
// you can't add anything to this without modifying the code in msg.c

The above, found in q_shared.h, is absolutely true, and has stopped me from adding in a new variable for a new "g_blah" cvar I was going to cross-reference in g_active.c, as you have done with g_speed, for example:

// set speed
client->ps.speed = g_speed.value;

I wanted to do this so I could use the format "pm->ps->blah" in bg_pmove.c, as I cannot seem to refer to "g_blah" and get the compiler to recognise it.  I've noticed that none of the bg_* files actually refer to any of the game's cvars, and this is probably why.

Oh, and I can't find msg.c anywhere.  

--=--

In short - please tell me how to use a conditional statement ( "if (g_blah.integer) { }" ) in bg_pmove.c, where g_blah is any given cvar, such as g_speed, g_friendlyFire etc.

Many thanks in advance!

Setup a regular g_bla cvar with the CVAR_SERVERINFO flag set.
Then detect said cvar client side

ie. bg_allowProne from ManDown :
In g_main.c near the top :
vmCvar_t bg_allowProne;

In g_main.c at the end of gameCvarTable :
{ &bg_allowProne, "g_allowProne", "1", CVAR_SERVERINFO|CVAR_ARCHIVE, 0.0, 0.0, 0, qtrue  },

In bg_public.h somewhere :
extern vmCvar_t bg_allowProne;

In cg_main.c near the top :
vmCvar_t bg_allowProne;

In cg_info.c, CG_DrawInformation() :
bg_allowProne.integer = atoi(Info_ValueForKey(info, "g_allowProne"));
In cg_servercmds.c, CG_ParseServerinfo() :
bg_allowProne.integer = atoi(Info_ValueForKey(info, "g_allowProne"));

In bg_pmove.c, anywhere I need to use it :
if (bg_allowProne.integer  bla bla bla

Hope that helps.

Haven't tried it yet, but just reading that makes perfect sense.  

Thanks m8, my trusty brain just couldn't work this one out.  

You're a star!

ugh, I hate all caps in titles  

anyways

msg.c is part of the engine code...so you can stop looking


you can't add anything to the playerstate*



(*note: well you can sorta, but its not really worth it)

Thanks m8, the ManDown example worked a treat.  

And I only put Apoxol's name in caps...  

All depends on how often your blah cvar is going to be changing.  If it changes alot then you definately dont want to do it via a cvar like was described above.

You cannot change playerstate as a mod maker, but, you can hijack stuff.  For example, if there is something Sof2 that you dont need and uses a playerstate variable then just disconnect the old sof2 code and start using the variable.

In the example of speed it is essential that the speed be in the playerstate and not there as a cvar because if it changes the prediction would get all messed up.

Gotcha.  Thanks Apoxol, good points also.  

My mod gets released next week, and I think Raven will be particularly interested in how it's turned out - as it merges your current and your previous Soldier of Fortune projects into one.  

The PhoeniX is rising...

Hehe, quite.