Fair enough. Bugs slip by too easily when working on a tight deadline. I literally just discovered a bug (fortunately one that's just visual and not game breaking) in my game that was caused by me using '==' when I should have used '<='. I just wasn't sure if it was a bug or not, since it could have theoretically been made that way intentionally for the sake of difficulty.
Viewing post in Sands of Avarice jam comments
Yeah, at the time it made sense to use '==' since it had to do with player health and there were some specific things that needed to happen when health was exactly zero (and it was easier to just let the player keep taking damage afterwards, and to work around that). This wasn't an issue since everything in the game did exactly 1 damage. Then I introduced sea mines which do double damage if you're too close and completely forgot to update the original code. It doesn't actually affect gameplay (you still lose if your health goes below 1), it's just annoying.