Ah dang... I did encounter this error once but it was less than an hour before the deadline. I did a quick check of the memory usage after it happened but I didn't see it increasing, it was hovering at an amount nowhere near the limit. So I don't know what causes the crash.
I read that the jam allows for bug fixes after submitting, so I'll look into it later. (idk if the rules still matter after the jam is over)
Yes the issue of the out of memory is an infinite loop in your WHILE when every platform has negative y due to the overlow at 32768.
It is very unlikely this happens in one run so maybe you could reset every y (player, platforms, etc..) as soon as you end your run landing on a platform? Or whatever takes less chars
yeah I just now realized this might be the issue, thanks for helping me pinpoint it! I had a feeling there would be issues with relying on the number wrapping (overflow)... I already used an alternate overflow-friendly way of comparing values elsewhere in the code because I found out that < and > don't wrap around (which makes sense, it's how most people would expect it to behave), I should've done the same thing for the while statement (and other places where comparisons are used, I'm now noticing...)
I think I've fixed it, overflow looping seems to behave seamlessly now. I'll upload the updated version in a bit
