Another fun example (Destiny)

by dogcow , Hiding from Bob, in the vent core., Thursday, September 24, 2015, 20:30 (3444 days ago) @ Kahzgul

"Hey, people are making new characters to buy strange coins." Fixed that weekend(maybe even that day, I wasn't playing then).

"Xur isn't selling heavy ammo packs while everyone is complaining about losing 2-3 rockets on death." Takes month(s) to add back to his inventory.

Some things are trivial to fix. Other things aren't.

Are you saying that trivial things should be ignored until the important, difficult ones are fully finished? (Do you even think the same people are working on the two classes of bugs?)

While this example is one design bug and another code bug, his point really does strike me as valid. Destiny's exploits have been fixed very quickly (Aetheon grenade - dodging off the ledge, Crota disconnect during AoE grenade damage, others I can't immediately recall) while Destiny's more anti-player bugs (Aetheon not teleporting anyone, Crota attacking before standing up, sword disappearing during the Crota fight, etc.) lingered for very long times.

The net result is that it feels like Bungie is intentionally favoring bug fixes which aid the player, but leaving in bugs which put the player at a disadvantage. Heck, some of the "bugs" Bungie fixed were really just very novel approaches to the existing fights, but those got "fixed" anyway.

I'm going to parrot the "Some things are trivial to fix, other things aren't." I have a sneaking suspicion that the buggy bosses were/are much more difficult to debug & fix than the exploits due to the underlying nature of the thing. Networking, lag, & synchronization all can make things quite tricksey.