01.01.2014, 13:28
dominik's solution, although working, is not the best. And could end up with false positives of course.
I have another sort of check in place, which takes action if:
1. it has been less than 2 seconds from the last connection
2.1. the connecting player has the same name as the last connection OR
2.2. the connecting player has the same IP as the last connection
I haven't seen bots which would use the same name but a different IP when connecting so far, all I have encountered is bots using different names from the same IP real frequently. These sorts of attacks, though, can be made "invisible" to the other players in your server - detect them before sending any connection messages or spending ANY time on them (this would include calling queries, "registering" them with the streamer or sscanf, etc). This way you will encounter less lag, if any.
JernejL has released something a bit more complicated when it comes to detecting bots. I believe you'll find it if you search for it.
I have another sort of check in place, which takes action if:
1. it has been less than 2 seconds from the last connection
2.1. the connecting player has the same name as the last connection OR
2.2. the connecting player has the same IP as the last connection
I haven't seen bots which would use the same name but a different IP when connecting so far, all I have encountered is bots using different names from the same IP real frequently. These sorts of attacks, though, can be made "invisible" to the other players in your server - detect them before sending any connection messages or spending ANY time on them (this would include calling queries, "registering" them with the streamer or sscanf, etc). This way you will encounter less lag, if any.
JernejL has released something a bit more complicated when it comes to detecting bots. I believe you'll find it if you search for it.