i was looking around in my game for the source of some bug. i took apart a bunch of scripts and edited some lists, thinking no harm would be done. but the project saved itself without my permission, causing my edits to be permanent. this is an awful feature and it should be removed. projects should only save when you want them to.

I don't like this feature either.

The workaround is to remix your own project. Or, unshare before making edits.

I support! When I was re-doing my project I messed up and wanted to go back to the old version. I refreshed the page but it had already saved! I had to completely redo my project from scratch. (No pun intended)

I don't like it either, for the same reason as Wes64. I was playing around with some high scores and threw away a script that I thought was the thing causing the problem. But, that script had no impact, and it also messed up another thing. So now, I have two problems that I can't fix and it is really annoying.

Annoying. There should be an option to disable this. Or, for now, remix your own project like BoltBait said.

Yep, this is a weakness in our current implementation in that we autosave, but don't provide a list of “versions” in case you want to revert to a previous save.

However - autosave has a lot of advantages for new users, so as a strategy I think it is sound. After all, the real world is “autosave.” If you rearrange a stack of blocks, you don't need to hit save - they're just there.

Once we add a revision list, it should solve most of the problems you guys are experiencing. That is - if you tinker around and don't want to keep your changes, it should be easy to revert.

It'll take more technical users more time to get used to (because we're used to saving). But of course our main goal is to support non-technical users.

Lightnin
It'll take more technical users more time to get used to (because we're used to saving). But of course our main goal is to support non-technical users.

What about enabling the undo/redo arrows when working in blocks. This would be easily recognizable for new users with some background in standard software packages.

learnegy

Lightnin
It'll take more technical users more time to get used to (because we're used to saving). But of course our main goal is to support non-technical users.

What about enabling the undo/redo arrows when working in blocks. This would be easily recognizable for new users with some background in standard software packages.

Oh yes- that's on the list, should be ready by beta or sooner! It should help as well.

You should be able to turn it on and off.

Mokat
You should be able to turn it on and off.

I don't agree. Autosave prevents users from losing any of their work, and that's very important for new Scratchers and helpful for more experienced ones. If you have versions available to you as well, you can revert to a previous version of the project, so you will never lose work by making changes, either.

What would be useful for me is to be able to declare a certain version of a project as the shared version and continue working on that project without further changes being shared.

Lightnin
Yep, this is a weakness in our current implementation in that we autosave, but don't provide a list of “versions” in case you want to revert to a previous save.

However - autosave has a lot of advantages for new users, so as a strategy I think it is sound. After all, the real world is “autosave.” If you rearrange a stack of blocks, you don't need to hit save - they're just there.

Once we add a revision list, it should solve most of the problems you guys are experiencing. That is - if you tinker around and don't want to keep your changes, it should be easy to revert.

It'll take more technical users more time to get used to (because we're used to saving). But of course our main goal is to support non-technical users.

thats good.

Maybe shared projects wouldn't auto-save and unshared projects would.

There's already been a discussion about this, to which I had offered my opinion/solution.

I quite like nXIII's idea above (keeping some sort of timeline of changes so that you can revert whenever you feel like it, and choose the public version) but I understand that it's not very practical to use or even easy to code.

Since the issue has been brought up again, maybe the current solution isn't the best way to approach the problem, is it…

Revivions.

Please

I think the best way to manage auto saves is to have them in case of accidental closes or crashes. Don't overwrite the project file, but allow for protect recovery on next start up. Of course, easier said than implemented.

Well, I like this feature, (since I haven't mixed with huge scripts yet,) but since it troubled lot's of scratchers, maybe you can turn it on and off.

Mokat
You should be able to turn it on and off.

But maybe Scratch should make a program that saves 5 last saves. So maybe you could undo saves. It took a lot of times anyway.

The auto saves should save your progress as a draft, so you can recover it later, but you can just discard the changes also.

Auto-save spams up my projects with Untitled-number every time I click Create, then think, “Oh wait, wrong button.”

ka-doink4545o0
Auto-save spams up my projects with Untitled-number every time I click Create, then think, “Oh wait, wrong button.”

That's not autosave, that's the way the create button works.