Just to clarify the Screenshot wasn't the part where the game crashed I just took that because I just found it funny how bad of a solution I was using for the Level. And the part where it crashed was definitely way worse then that. But yes its possible the crash happened because of something completely unrelated.
As for the 1000 number bit, if you do still want to stick to it then you probably need to find a way to incentivise players a bit more to actually give it a shot, not exactly sure how you could achieve that maybe a completionist sticker or achievement. It's not that I didn't understand I could have 9 numbers delivered at once, its just my focus was more on getting to the next level. So maybe this would depend from player to player and how they approach the game.
Either way good luck making your game.
Viewing post in Numflow jam comments
I found the bug! It happens when playing levels 1–6 without restarting the game. The problem was with WebGL resources not being released properly, which caused the crash.
And thanks for clarifying the 1000-number challenge! Now I understand your suggestion about limiting buildings. I originally designed Numflow as a puzzle game, but thought expanding factory production would fit well too. Now I think adding restrictions to make the puzzles more challenging is a better direction.
Thanks again! =)