Makecode deleted 98% of my code

AND EVERY. SINGLE. ASSET. FROM ALL OF MY GAMES. YES, THAT’S RIGHT

ALL OF THEM

I WORKED ON THOSE FOR MONTHS IF NOT, YEARS! AND YOU KNOW WHAT?

I QUIT

IM DONE
GOODBYE MAKECODE
ANIMATION HERE I CO-

(Thank you for all of the support everyone. This has been an amazing ride. However that was my last straw.
Remember, it was all of my projects)

Thank you all
(I may check the forum once in a while,
Since this place is so caring towards others and i have literally never seen anything like it. It has been a crazy ride, goodbye makecode.)

20 Likes

@_jupiter I’m very sorry to hear that! This is the first example I’ve heard of multiple projects being affected like this, and would greatly appreciate if you could help me do a little debugging. Can you try downloading all of your projects to a zip file? Here’s a gif showing how to do it:

save-as-zip

That GIF is for micro:bit, but it’s exactly the same for arcade

Also, I know that this is not the most comforting thing to hear at this moment, but we do have a new feature coming called “Version History” which hopefully make recovering from these sorts of problem much more easily. This feature is already available in makecode.microbit.org, and you can see it in action in this GIF:

version-history

7 Likes

usually I refresh my page and the assets are back, but if you change any code, their gone forever

7 Likes

I’m sure the mods can help!

1 Like

I am so sorry to hear that! I lost it whenever it happened to one of my projects, but I couldn’t imagine losing all of them. I understand that you would react this way. I would find that kind of dataloss or corruption completely unacceptable. It’s really not fair that we have to worry about our coding community being inconsistent or untrustworthy with months of time that we’ll never get back. I know that this won’t do you any justice, but I just wanted to say that I support you with any path that you choose to go down after this.

2 Likes

This happened to me 2 years ago and since then I’ve been super careful with my projects saving.

I’m sorry it happened to you.

5 Likes

Turns out I was overeacting and it was only 2 projects, however they were highly major ones that i was working on for a while

4 Likes

also to help i was working on my games with a school device, idk how that would incorporate, but i think it might help

2 Likes

The first project was coconutty, which had all of its assets deleted and about 98% of its code,
the second was a nextbot game that had EVERY SINGLE ASSET permanently erased
again, im sorry for saying it was all of my projects, i checked 2 and lost my sanity

5 Likes

That is actually crazy. Maybe I should use a different game engine instead…

1 Like

Ouch! I know how devastating it can be to lose your hard work! As an educator, here are some tips I suggest for classrooms, just to keep everyone’s projects safe:

When you are signed in:

  1. If you lose your work, ask for help from the MakeCode Admins immediately. Sometimes, with an account name and a date, we can rescue your previous version.
  2. Watch for @richard’s Version History feature and once that appears in your settings, you can select it yourself and find your previous version
  3. Try uploading your game to your GitHub account regularly. You can do this with the little GitHub icon to the right of the save disk in the bottom toolbar.

Whether or not you are signed in:

  1. Every time you make major strides in your game, save a copy to your device. Do this by downloading a png using the save icon in the tool, downloading a uf2 with the “Download” button, or copying a _ link (snapshot) to a master document to be opened like a back-up at a later date.
  2. Consider using image packs for your games. Not only will this allow your games to load faster, but you’ll have a GitHub trail of all changes in case something happens to your assets.

I hope these tips help everyone keep their projects safe in the future!

2 Likes

Or save copies of your games as files to your computer! Always works for me. The cloud is unpredictable…