So if you are editing a shared project and you click save/Scratch saves automatically, the shared project is updated. Your project will be glitchy for a bit though because what you change isn't finished yet. My suggestion is that once you share a project, the share button changes to this:

Clicking “Save Now” saves the project for you. Clicking “Update project” updates the shared project. This way glitchy or unfinished projects won't accidentally be shared with the public.

Support. I usually update my projects that are shared and I have to make construction screens in order to prevent Scratchers from playing those projects that may have bugs in them.

I support this. Sometimes when I update a project the thumbnail and project gets messed up.

Good idea, but maybe replace the word save with autosave to be less confusing.

Alzter wrote:

Good idea, but maybe replace the word save with autosave to be less confusing.

Why? It's possible to click that button to save.

A lot of people don't have the Scratch app, so support. I've also had the issue that I want to save my project but not officially update it.

bump

neeb132 wrote:

bump

Good thing you bumped!
Anyways, support, because you don't have to create a copy, edit that, download the copy to your computer, upload the downloaded file back into the original, change the title back (for some reason, the title always changes to match the current file name w/o extension) to the title before it was uploaded, permanently delete the copy, remove the URL of the copy from your browsing history, and then tell everyone it's updated (optional).

I like this idea. This'll prevent people from forgetting a project is “down for updates” and having that project's construction screen showing for a month. (This actually happened to me once.)

B - bring
U - up
M - my
P - post

bump

Support! This would be a GREAT way to deal with buggy updates, and how I think it would work is the Scratch Servers store 2 copies, an Updated and a Saved one. When the user Saves, the Saved one gets overwrited, when the user Updates, the updated (shared) one gets overwrited

Support! I HATE having to deal with multiple projects that are almost the same, just to update the project! And using the backpack to send the finished scripts to the unfinished project using the backpack! This would be AMAZING!

Support! Great idea!

Bump

Bump

idea!
Maybe there could be a button in the file tab that would say (Save as an updater) and that would create a copy of the project that instead of having the share button, it would have the update button, and the updater project would be saved like a normal project!

i hope scratch sees this forum

100% agree with all the points made above, and,

whilst this is technically possible by saving a separate unshared copy and uploading and overriding the shared copy once all modification has been made… that is terrible UX (User Experience) which is something Scratch prides itself on making easy and accessible. I see no reason why this suggestion shouldn't be implemented (and I don't believe it'd be terribly difficult either?)

Well yes, but actually no
(no support)

I mean, it's a good idea, but I'm surprised that no one has considered yet that:
- you can just unshare the project, update it, and reshare it. I mean, griffpatch does that!
- you can work on your project on Scratch Desktop and then upload your updated project. Unless like me, you run on Linux and you have to use solution 1 or wait.

All in all I don't think it's worth it