@waldron Yeah, eventually I got the code, (although it's still pending) but the error is still happening just as randomly even though i've not shared anything recently
The code is S8Y23MNDX5
@gothon Oh man! That worked perfectly. Thank you very much. Did not know that.
I converted the code from Pico 8 (Lua programming language), so you are probably right with your guess. haha
Now it runs like charme. <3
@SteveZX81 on step 4. I’ll try it with different tiles and see if I can get anything to work maybe even a completely different sprite sheet. I’ll let y’all know what happens when I get the chance
Btw, is there a description or an example of not single- but multy-dimensional array in this bult-in help? I coudn't find it yesterday, found it only here on a forum..
@evilblade Yes, you are right, @Kat hunted that down too. Actually 45 was just the first case I notified...and it makes the bug a bit more mysterious. Also, 42 would have turned this into a famous easter egg. 420 wouldn't do any good though. 😂
Hi @Z-Mann, I can confirm that this is an existing issue in version 3.0.0 and has already been addressed on our end. You'll be able to run this program multiple times successfully in the next patch!
Thanks for the report @Z-Mann - we are aware that sprites intersecting multiple collision boxes at once can cause some issues. We'll look into your example.