[Not a Bug] Ping Checker timelimit bug

NakedSwede

New member
Sep 6, 2017
17
1
0
Here's another bug for ya :)

This time the "Time Between Checks" and "Failures before action" is working against eachother.
Look at screenshots..

Most possible is because when detecting a player exceeding pinglimit the first try, the code is probably starting a 5 min countdown...but since it needs to "ping-fail" 3 times before taking the kick-action, the real time that the player is booted for is actually only 3 minutes.


Chatlog showing timestamp when player is being kicker and reconnecting:
411WNZd

View: https://imgur.com/a/GJDDV



Screenie showing the ping checker settings:
View: https://imgur.com/a/I2IdR

OUYBMOZ
 
This appears to be working fine.

The time between checks at one minute, will check every minute. After 3 failures, the action will happen. In your case, you have it set to kick the player, and then RAT does that. Since this is a kick event, there is no "duration", so the 5 minutes displayed isn't in effect.

Kicking a player will not prevent the player from rejoining. The default RAT event, bans someone instead of kicks, so the kick message makes sense. So you have two options, change the kick to more accurately say what you want, or change the event back to a ban and it'll work as it says there.

Let me know if I'm misunderstanding. =)
 
yea i actually noticed that theres no kick-timeout. So its a matter of userfriendly GUI then. Grey out the field if kick is chosen.
 
  • Like
Reactions: Trekkan