thanks a lot

@pianofire Thanks. That works. I'm only losing the map, but that's ok. I had just started building that when the project corrupted.

I'll probably have to make periodic backups to stay safe.

Sorry for the late reply Vin. Thanks for reporting this.

@linkcraft good luck 👍

Thank you @richard and @Kat !

Hey Vin, that's a good suggestion. Hopefully we should be able to make a few improvements in this area in a future patch.

Thank you, Steve! I've logged the issue.

just tested in 3.1.0 bug still exists

@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

Just put textsize() back to what it was.

One minor addition regarding the fonts: the naming is also a bit inconsistent. I suggest naming the files:

glassSet1Cap instead of glassCapSet1 and
glassSet2Cap instead of glassCapSet2

Also the letter casing of SPC postfix varies from font to font.

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.

I’d love a way to break out of a running program back into the code editor, change something, and then resume the program where it left off. For ease of use/quality of life reasons, similar to yours.

Ahh ok that makes sense. Glad you got to the bottom of it! :)

@Dinocoder duplicating the same line of code twice will apply the offset it's a minor fix for now.