Air combo counter

[divVerent]

Then it can't be shown in comparison to other players.

[Alien]

I thought it was suggested as a personal stat, not as a stat used to compare one player with others. Is accuracy compared between players too?

[morfar]

Obviously "maximum speed gained" would be changed all the time... so this and some other stats should only be sent to server at intermission.
While other stats may be sent while playing.

[mand1nga]

Well .. you guessed right that maybe, perhaps I can do it

Client side sounds fine to me, but I don't know yet how to detect there if an enemy is flying, etc. I care about bandwidth, but now I'm thinking that one byte of data should be enough for this. So .. first lets define if we really want this

How do you think it should look like? I imagine the text in bold font, centered vertically with options for being placed at the left or right of the screen, it should be visible but not too distracting. I'll make some blueprints of this later.

However it would be nice if someone with experience on visual things can share his thoughts here

I'll look for some inspiration in other games about the "combo" concept, like mortal kombat, street fighter, etc, etc

[mand1nga]

I thought it was suggested as a personal stat, not as a stat used to compare one player with others. Is accuracy compared between players too?

Yes you are right ... but maybe this time we shouldn't worry too much about adding a little of this to server side .. I really don't see any significant performance impact or bandwidth usage

How about the max speed reached? I think it would be nice for race and ctf modes, and only considering speed gained by own weapons ... I think we can mix subjects a little and discuss how do you want it displayed, maybe I can help you with code

[Alien]

I suggest that everything should go to client side to in order to worry div less. If people would really like it then it could be moved to server side.

[divVerent]

This has nothing to do with worrying ME, but with bandwidth for everyone. The server will only send 25k/sec per player, and also only 1400 bytes per packet.

But yes, if it is only shown personally, the best way would be letting the client count the events, possibly using a CSQC networked entity that's only sent to the owning client.

[mand1nga]

Well .. what can I say, a great deal of ppl that I truly respect voted already, so I think I'll start to play with this idea

But please lets discuss a little more about the best way to display this information to the end player

[Alien]

Why 1400 limit is clear for me (packet should be smaller than MTU) but why 25kb(ytes)/s? Is that the current network architecture limitation or imposed by developers to limit the bandwidth that people with smaller bandwidth be able play?

sys_ticrate is 0.05 = 20 packets/second Would increasing ticrate make packets somehow smaller (?) or rate would be > 25 ?

[divVerent]

The 25k/sec is a configurable limit of the bandwidth the server will send per player.

If it were fully used, one player slot could use 60GB per month. A 16p server can have 965GB per month for the in-game data alone, if you send so much spam. And most server admins pay for their bandwidth.

However, 28k/sec is the theoretical limit, as there can be only one packet per frame.

Reducing sys_ticrate would eat too much CPU on the servers, and noticably change player physics (especially laser jumps).