Raox2 / sunrust-issues

A place for bugs and the like.
2 stars 0 forks source link

[ZS] Limit kill feed spam #15

Open ghost opened 6 years ago

ghost commented 6 years ago

https://developer.valvesoftware.com/wiki/PVS

Anything that the client can handle, it should handle, instead of leaving all of the work to the server. Split the kill feed into the following: Server: forced notifications and for notifications out of pvs. Client: notifications within the client's pvs. Local: notifications only for the individual client.

The intent of this is to cut down on useless networking, minor fps loss, reduce kill feed spam and to give the client some degree of control.

This may need to be refined multiple times to make sure there are no issues.

Affects fps in:


Kill feed notifications

- Don't display an avatar if the attacker/victim is a bot. Done.

The scoreboard is a better place to handle displaying escaped players. https://github.com/JetBoom/noxiousnet-issues/issues/230


Options

Add options to personally choose what information you want displayed: Examples of what could be added:

A checkbox system would better serve the client, as they can choose what information they want to request including the ability to override forced notifications from the serverside, clientside pvs, local, or a mix.

Other options:

Raox2 commented 5 years ago

I can do this if there's no considerable serverside cost downside to iterating through player options as kills are sent. Otherwise I'd need to cache it. There's considerable downsides since it's managed by the server. It may not be as performance friendly as you'd like.