Muscular Beaver wrote on Sep 1, 2020, 04:48:
"Exploiting a bug is not cheating"
I dont remember how many times I heard that in multiplayer games, especially from the bunnyhop crowd. But I would be rich if I always got a penny for it.
Coaches of esport teams being that stupid.. Now thats something new.
Bunny hopping has been a deliberate feature in FPS games since quake 1 (1996). There is dedicated movement code for it. It was added to make movement another skill to develop.
The sheer popularity and endurance of CounterStrike basically erased the normalcy of bunnyhopping from the collective FPS gaming psyche. CounterStrike (which patched bunnyhopping out around beta 3 ish IIRC) was all many people played for years, and so many games tried to copy it, that it just became the new normal.
That said, I tend to side with the 'if the engine allows it, then it's fair' crowd. The engine defines the rules. What it allows, is allowed. If you don't want players doing it, patch it out.
Since doom, for a decade+, it was considered a skill to find and master anything that the engine allows for an advantage. From silent BFG firing and wall run speed boosting, to making pixel-precise jumps to ledges (that 99.99% of players can't make) where you can fire from an advantage.
Overwatch was infuriating to play widowmaker on. There are countless off-limit areas where you can't grapple to. I've died countless times planning an attack and escape, only to find out that my escape path has an invisible wall. Absolutely COUNTLESS. Then the opposite happens - someone else escapes from me using a route that I just assumed would be blocked because 100 other similar routes had invisible walls. FFS. The inconsistency is far worse than just allowing a general purpose grapple to anywhere. (Or at least make invisible walls translucent, so we know places are magically off limits).