Me and Joris butted heads about this yesterday after he kicked me for bhopping and threatened to ban me. I want him to know this isn't specifically about our little incident, but the rule itself and how there's a wide spectrum of interpretations of it by admins and players alike. First, the rule as stated: Do not Bunnyhop (bhop). This means you can not use bunnyhopping to gain an unfair advantage - this causes significant balancing issues. (from the ZE rules page) Note the "to gain an unfair advantage" part. I believe the spirit of the rule is to punish 1) humans who slingshot far ahead of the rest of their team in order to trigger map events early, and 2) zombies who use it to catch up to humans unusually fast. This is all fine so far, and I understand when the rule is enforced under these circumstances. The problem is with the other 99% of situations: Isolated bhops. How many is considered rule-breaking? 2 jumps? 3? I can tell you with certainty that I've witnessed admins, even LSAs, do this themselves (obviously without consequence). Bhopping as a zombie to get into a hold point (e.g. over a box). Again, this is something that every skilled player is inclined to do. That includes admins/LSAs. Bhopping to pass the time. Bhopping as a human to catch up to your team. Bhopping in (NOT ahead of) the crowd. The list goes on. The reaction from admins to this sort of activity is... uneven, to say the least. Most of the time, they don't care. After all, nobody's hurt by it, so why bother? But on the odd occasion that someone does get kicked, it calls the definition of the rule into question, as well as undermining the competency of the admin team as whole and their ability to enforce the rules in a fair and even-handed manner. There is another component to this discussion, and that's the anti-bhop plugin. This didn't yet exist the last time we had a thread about this issue back in april. What does it do? You go too fast, you get slammed into the ground and your velocity is reset. Works as intended, right? One wonders then, why the higher-ups can't simply let the server software do its job, and instead focus on cracking down on other rule-breaking behaviour that isn't as easily automated. Even the server settings (not taking the anti-bhop plugin into account) are so stacked against bhopping, most of the time there is no reason whatsoever for an admin to step in. I've yet to see a player bhop more than 20 feet ahead of the pack. It's just too difficult to keep that kind of momentum going. The timing required is incredibly delicate compared to how it works on ZM. That's about all I have to say. In short, there's no need to be overzealous. In reality, the advantage gained from bhopping is slim to none (nevermind these hypothetical "significant balancing issues" which have never materialized), so relax and let people play the damn game.