Defining a STAT_

[DusterdooSmock]

I used this tutorial () to add reloading to quake, and then i added my own animations to it, it works fine, but now i'm trying to add a bullet counter to my engine.

I already have the code for the counter itself but i have to make a STAT_ that shows the count of self.pistolclip, not self.ammo_shells.

How would i go about doing this?

[Jukki]

[Spike]

the easy way from QC is to writebyte(msg_foo, svc_updatestat); writebyte(msg_foo, stat_mine); writelong(msg_foo, myvaluehere);

probably msg_foo=msg_one.
stat_mine is whatever value you want. if its <32 you'll not break network compatibility. DP, FTE, and other QW clients have specific interpretations for many <32 stats. CSQC states that 32-128 are for mod use. If you don't care about compatibility then it doesn't matter, just be aware that you might end up changing DP/FTE's zoom and stuff :)
myvaluehere is whatever value your mod wants to send for that stat.

then you can send what you want, when you want to send it. don't flood it! make it a function to be used to set a field and delta check it. that works too. logically you're limited to integer values, though really all that matters is that its 4 bytes. you can mangle them clientside if you really wanted to send a float instead, but you'd need a union or a *(float*)&cl.stats[foo] or something. If you want to send a full 32bit int bitmask, send two shorts, the first is the lower 16 bits, the second is the upper (floats can only retain precision to about 24 bits).

An NQ engine will flood the client with regular stat updates once per frame, but at least its only one byte per stat (see svc_clientdata), while QuakeWorld deltas them, but knowing this isn't too important.

The QC-directed stat sending is the easiest to explain. An engine could easily be configured to send fields, but that's far far more lines of code (field access with delta storage+delta code, or protocol changes, depending on how you want it).

[DusterdooSmock]

@Spike thanks for the help, but i figured out how to do it.

I just used the normal STAT_AMMO function, and made the self.pistolclip the current ammo when the bullets are taken away or the clip is reloaded. (don't know if that's the right way to do it, but it works!)

[Jukki]

hmm spike. Could you lil explain to this no c noob how to do that lol. I am only coder on our team XD

[DusterdooSmock]

[Jukki]

[DusterdooSmock]

[Jukki]

[DusterdooSmock]

[Jukki]