Another fun example (Destiny)

by Kahzgul, Friday, September 25, 2015, 06:55 (3444 days ago) @ CruelLEGACEY

Yeah, they may feel like evil Bungie is out to get them, but I'm very sympathetic to how difficult it is to maintain this ecosystem they have built, and I think these exploits have a ripple effect that disrupt the ecosystem, and have the potential to make the game less fun for everyone.

On the other hand, I doubt that kind of analysis is the deciding factor that often. The ease and impact of the fix probably weighs heavy, and as outsiders, any theories we make about that are likely rubbish.

A friend of mine once likened the process of dealing with software bugs to dealing with actual bugs.

He said "if you're at the cottage and you're surrounded by Mosquitos, you swat anything that lands on you... even if it isn't a mosquito."

I don't know how accurate that is, but it makes me smile :)

Having spent over a decade as a tester, I can tell you that it's not a very apt analogy at all. Basically you class your bugs as either A (must fix, major issues such as corrupted saves, crashes, missions that can't be completed), B (should fix, big issue, such as holes in the world, a character in a cutscene missing his face, melee attacks dealing small amounts of splash damage back to yourself), C (minor issue, usually art bugs like "suros logo on gun A is red, but is orage on gun B, should be more consistent), DNF (do not fix, which is usually stupid stuff the producer doesn't want you to waste your time on), WNF (will not fix, which is usually complicated stuff the programmers don't want to spend time on), or NAB (not a bug, which is stuff that isn't actually a bug at all, such as "Enemies with orange shields appear to take extra damage from solar weapons").

Exploits are almost always class A, especially in multiplayer games.

Likewise, horrible boss glitches that completely wipe the raid should be class A. An argument could be made, I suppose, for them being class B as they don't prevent you from trying again, but if I were on that team I'd have fought for it to be class A.

--

It's all beside the point though: Once Bungie acknowledges a problem, 6 months without motion on it is too long.