New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't reset cl_antiping subconfig on restart
#333
Conversation
| { | ||
| g_Config.m_ClAntiPingPlayers = 1; | ||
| g_Config.m_ClAntiPingGrenade = 1; | ||
| g_Config.m_ClAntiPingWeapons = 1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should probably only set this to 1 if m_ClAntiPing is 0.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not keeping the previously set config variables here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because the old behavior reset all these to 0 when the player set m_ClAntiPing to 0. With the new system, they don't get set to 1 automatically when the m_ClAntiPing setting is set to 1, thus all antiping measures would be disabled by default if someone used an old config without this workaround.
If cl_antiping is 1, the previous version of the code would have set all other antiping variables to 1 anyway, so with this commit the user can retain their antiping config if they configured after the last start of the old client.
This would also happen anyway as no config is treated as config version 0, since cl_antiping is 0, all the subconfigs would be set to 0.
|
everything worked while testing and code looks fine too, gonna merge |
Don't reset `cl_antiping` subconfig on restart
With backward-compatiblity (sets
cl_antiping_*to 1 on first start.)Fixes #327.