They've said that? (Destiny)

by Kahzgul, Thursday, October 15, 2015, 18:36 (3422 days ago) @ slycrel

network manipulation is the only known reason of cracking down on "cheating" that I'm aware of. (Also here)

Even AFKers weren't labeled as cheaters, just bad citizens who got warnings.

Pushing atheon off a ledge was an exploit/cheese.
Shooting the nexus mind via glitching through the wall for nightfalls was an exploit/cheese.
Hiding under the platform for winter's run was an exploit/cheese.
Sword jumping across the chasm in crota was an exploit/cheese, as was making everything despawn then completing it. Among other things.

What about final round snipers in trials? Sucks, yes, bad sportsmanship, yes, but is it cheating?

All of these things were corrected by bungie and not labelled as cheating. I think there are a few things in PvP like this as well, but I'm not as avid of a PvPer, so I'd have a harder time to compile a list. Besides, I'm out of time. =)

Cheating != bad sportsmanship. Cheating != exploits. Cheating is breaking the rules. This is working around them. It's still a dick move, and I don't do it nor would I condone it.

Fun fact: "Cheating" isn't actually a term in classifying game bugs. We call them exploits. So exploits == cheating actually. "Cheats" in game design speak are usually in-code debug scripts or unlockable buffs that the players can turn on or off in single player, non-competitive modes (think one hit kills or invincibility in Golden Eye, or the god mode codes in Quake). A player who is using cheats is playing the game as designed, whereas a player who is cheating is using exploits to play the game in a way other than as it was designed. Weird, right?

Here's how I'd have classed these things back when I was testing games (and I was lead tester and database manager, so I was generally the final word on what the things were, which is why I think my opinion is worth anything here):

- Network Manipulation: Exploit of net code, provides advantage to individual players and their teams. Class A bug.
- AFK: Player behavior, NAB (NAB means Not a Bug). Suggestion: add code to prevent/reduce AFK behaviors. Class C bug.
- Aetheon off the ledge: Exploit of AI code (poor design, really, but I'd never say that in the bug report), provides advantage to raid team bypassing intended course of fight. Class A bug.
- Any glitch through a wall in any area: Exploit of map geometry, provides advantage to player and their team, bypassing intended course of fights. Class A bugs (possibly only class B in most cases, with class A reserved for boss fights such as the nexus one listed). Same with Winter's Run.
- Sword jumping across the chasm in crota: Exploit of game mechanics and map geometry (poor design, really, but I wouldn't have said that explicitly in my bug report), allowing player to bypass intended course of encounter. Class A Bug.
- Final Round in snipers: NAB / by design (same with luck in the chamber). Suggest we remove these perks from snipers as they are too powerful in pvp (but this is working as intended and is therefore neither bad sportsmanship nor cheating). Needs NERF.

If any of these need clarification, please let me know. Generally speaking I would not consider any "poor design" exploit (Aetheon, sword over chasm), to be bannable, but I would consider a "bug exploit" to be (geometry clipping, infinite supers, network manipulation).