Sorry for the late response to this week-old thread, but as I get PMs by people who want to become an admin to kick/ban "hackers", this post might be needed to explain something RedEnchilada mentioned before.
I'll simply paste the relevant part of my PM answer. :)
You'd like to kick/ban hackers, which is normally an awesome idea, as hackers hurt everybody with their unfair advantage. Hacking is very common and problematic in games with millions of players. These games (like World of Warcraft) have so many players that the servers can't really check everyone's actions. In games like World of Warcraft, every player sends their current position to the server. Hacking is easy there: just tell the server "I am in the city" and the server will believe you, so you can "teleport" to the city, for example.
SRB2 matches, however, have much less players. The server has no problem to calculate the position and movement of every player in the game (up to 32, that's nearly nothing for a computer). The SRB2 server does *not* blindly believe what the clients say. The server accepts only *actions* from the players, like "I want to thok now and run as fast as I can in this direction". The server calculates how the player moves with this action, and sends the result back to all players at the same time. The server will wait until everybody received the new position of all players. This is why a player with a slow connection can cause the server to wait ("lag") until even the player with the slow connection finally learned that Tails player 5 has now moved a bit upwards.
Because of this design, no player needs to be trusted by the server. The game can not be abused by someone who sends wrong information to the server. The server checks and computes every action done by the players, and nobody can cheat.
It would be theoretically possible to write a bot that does all actions for you. This bot could not cheat in any way, but the server can't check if you are really sitting at your keyboard. It can only check if the commands you send are legal. However, as there is no way for anyone else to tell if somebody uses a bot, we have to assume that nobody is using a bot. We can't kick/ban players for playing as good as a bot, because they could really be a human playing as good as a bot. An "aimbot" is a bot that only assists you with shooting while you have to move yourself. This is even harder to detect, as a good rail shooter could do exactly the same things. Again, kicking people for being good shooters will be very unfair to people who are really good at manual aiming.
Freezing the game, maybe done easiest by pulling the Ethernet cable, plugging it in again and repeating this forever, causes the server to wait for you. There is a timeout after which the server says "Your connection is so horrible that I can't let you play here" and kicks you, and that does work relatively well. There might be ways to make the server wait forever (just like the
Slowloris attack on HTTP servers), but this would be a bug and not intended by the developers. The 2.0.7 update fixed such an attack possibility, if I understand it correctly.
In a nutshell: If there is a "hacked" version of SRB2, it can only work in single player games or if you host a multiplayer match yourself. If you are the server, you have to check if everybody adheres to the rules, and you do the movement calculations. In your own (single player / self-hosted) game, you might be able to "hack" because you are trusted by all other players.
In multiplayer SRB2 games, as a client, there is no way to "hack". There are ways to be annoying, but there is no way to get any advantage in the game by using a modified client. The reason is not "This mysterious SRB2Hacked.exe does not exist", but the reason is "Even if this thing exists, it is completely useless."
