Over in the weekly challenge thread,
@devieus said in Weekly High Score Challenge #55:
Just kinda wish I could see where I was when I'm above the top of the screen.
Yeah, that's a bit of unintended cruelty I tried to avoid... a classic case of developer blindness. You don't have to go fully above the screen, it's always avoidable, and even if you do, well, I had kind of assumed you could 'feel' approximately where you are. But of course, I had to play each level a bazillion times myself...
Anyway, I did manage to compress the saw movement code from five to three lines, stupid iteration over all the collision instances is completely unnecessary there. And two lines are enough for an offscreen indicator. I'll share the update when the challenge is over to avoid disrupting it.
Of course, I could have just redesigned the levels, but that would have been less fun and more work :) I also could have allowed the screen to scroll to keep the player visible, that would have been less code, but that would be against the single screen constraint.
