You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The AntiBot class checks that in the last 5 seconds not more than x players have joined. This is being solved with threads, so a task with a wait time is scheduled to decrease the counter again. Find a better way of doing this without scheduling threads.
The text was updated successfully, but these errors were encountered:
With the current implementation AntiBot can also enable after a server restart, when all players try to rejoin again. Maybe there should be an option that AntiBot only triggers on X unregistered players? I think you don't have to check regular players.
If I get a botattack the probabilty that there are known players is very low, especially if they have names like "gd52heg2hd6u".
@Platinteufel this is the intended behavior of AntiBot (only fire if X unregistered players are observed). Please open another issue if this is not the case
The AntiBot class checks that in the last 5 seconds not more than x players have joined. This is being solved with threads, so a task with a wait time is scheduled to decrease the counter again. Find a better way of doing this without scheduling threads.
The text was updated successfully, but these errors were encountered: