Saving Backgrounds for a Art game to then load in later

Does anyone know how I would save backgrounds to memory or as like a key so that the player could for example save a artwork and then close the tab. And then like say a couple days later they go back to the game and reload in their art work. I’ve tried using the settings extension and the better setting extension (by @Sarge ) but I kept getting streams of errors and when I got it to partially work, It was very buggy and didn’t save correctly. The game in question that I’ve been trying to add it to is my game called ARCANE DRAWINGS. (A actual working painting game) [COMPUTER ONLY] any help would be greatly appreciated :smiley:

Have you tried this yet? I have no idea if this will even work just fyi.

1 Like

or the better settings extension https://github.com/sargedev/bettersettings

Which has a image save block

In the post I said that I already tried the better setting extension

Yes I’ve tried this, it also didn’t work

oh sorry

If you’re loading screen size images into storage you will run out of storage very quickly… I assume that’s what’s causing your errors. Which error code or exception is makecode showing?

Yes, below is a image of me trying to use your extension for my game. My plan is for the player to only be able to save one image, which they can then load in later on. I’m still relatively new to makecode with only having about a hundred hours of coding with blocks. Any help is greatly appreciated :smiley: . (I actually lost all of my versions to the game I wanted to add it too bc all of my projects got deleted due to a bug in the makecode website, but I will use a older version to show you what is happening)

Due to me no longer having access to the original game link here is this one: https://arcade.makecode.com/S36288-67298-14087-59602 (If you want to do it in JavaScript then that’s okay too)

@Sarge (I meant to @ you for the post above)

Panic code 920 means you’re storing too much stuff

1 Like

How could I make it more optimized if it is even possible to?

Not sure… maybe writing the image data to a buffer but I think that would only be slightly more efficient than the current method. It’s just a limitation of makecode storage I guess

2 Likes