3 ms·

> it also does not take significant resources to fix This is where you are wrong. Even small fixes can destabilize builds. Every change needs code review, test

> it also does not take significant resources to fix This is where you are wrong. Even small fixes can destabilize builds. Every change needs code review, testing, a build, release (and possibly release notes). You need to schedule time to work on it, which means prioritization meetings and advocating why this bug should be fixed and not the other large pile of bugs. Maybe you need to update some unit tests or automated feature tests. Maybe stop by the level designer's desk to make sure there weren't any baked in assumptions about player movement and space. Probably a good idea to chat with a gameplay designer as well to make sure it wasn't intentional (and also to validate that the fix doesn't actually make the game less fun.) Wouldn't hurt to go to a playtest and mention that it's been changed, see if anyone on the team notices. Actually, come to think of it, maybe you could put your fix behind a console command! Then you could quickly flip back and forth and see what you like better. But that also means adding a little more code and probably a little more documentation. Sure, on the face of it you've just changed one arithmetic function. But there is a ton of hidden work and complexity that surrounds that. As someone who made games for a living, there's a huge amount of unseen work that goes into even small changes. Players consistently underestimate the complexity of even minor fixes.

Retric 7y ago
This this is not some obscure off by one error. You see it in basic game building tutorials. Hell, I will admit to making this mistake on an early game, but only once. Not making the mistake in the first place should generally prevent the issue even if it was never fixed in any game ever. I am calling it incompetence specifically because it’s the kind of mistake you make when you don’t know what you’re doing. PS: If detecting and fixing an issue like this is a significant issue for your team, that’s a much larger issue you need to deal with.

Retric 7y ago

This this is not some obscure off by one error. You see it in basic game building tutorials. Hell, I will admit to making this mistake on an early game, but only once. Not making the mistake in the first place should generally prevent the issue even if it was never fixed in any game ever. I am calling it incompetence specifically because it’s the kind of mistake you make when you don’t know what you’re doing. PS: If detecting and fixing an issue like this is a significant issue for your team, that’s a much larger issue you need to deal with.