Pretext
---
Some bed time reading before-hand, if needed:
server.cfg and Server Side Scripting
In short basically regularCheck checks the users addons every once in a while
during a mission.
If you want to get more context, search with the keyword 'regularCheck' and
check the last two pages of the search hits.
The problem
---
Back in a1 days when introduced, regularCheck caused some people to time
out and getting kicked from the server.
Maybe it also had an impact on the server performance - especially with new
players joining (JIP) and large number of players.
This lead to most server admins disable the check by:
Code:
regularCheck = "{}";// aka add some nonsense to make it not work
Now as it turns out to open a way for people to cheat on the server.
While it is obvious in theory, there are known ways to abuse this too nowadays.
The problem - part 2
---
The above reason, as well as many people and dedicated server guides have
suggested to use 'regularCheck = "{}";' lead to most servers having this
setting active now - in other words they have regularCheck disabled.
The solution?
---
The question is now, if people can activate regularCheck again, without the timeout
issues from back in the day or other negative impacts on the server/players.
Feedback
---
If you want to make the game less cheat prone, please participate in testing
and sharing your experience with regularCheck active.
ToDo: open the server.cfg and set:
To have it working you also need to have the sig system active:
Code:
verifySignatures = 1;
Please gather feedback from players, if you can see any negative impact
or a rise in people getting kicked (with sig check timeout).
Important note
---
Unfortunately it appears the client gets only the unspecific message:
"You were kicked off the game."
And the server console.log only shows:
"Player Test disconnected."
So in other words it is rather hard to gather statistics on the number of
people kicked with timeout.