You read the title. 3.0 is a bit problematic. It feels like using a beta, except it's the full site and there's no way to avoid it.

My main issue is that there are tons of missing features that we had in 2.0: remix trees, tags, sound editor features, save to local file, project restore, centering in costume editor, embedding projects, and numerous other things I'm sure.
Is it too much to ask to have the new version at least include the features of the old one?

Actually, my main issue is that I can't save one (or more) project(s). I edit something, click save, and it loads for 30 seconds or so before crashing the page.
That's really useful.

My other projects save fine, albeit much slower than in 2.0, but this one doesn't work. It was right around 49.5 MB in 2.0, near to the project limit. Has the size limit been lowered? Or has it been corrupted somehow? I've been working on it for months on end and will not be pleased if it's broken.

And there are obvious visual bugs that weren't there in 2.0. Everything is blurry and offset, especially text. Exactly whose idea was it to replace the fonts with new ones with different spacing than the old ones? Centered text is now to the side, some overlaps with button edges, and generally looks bad.
Also, variables now default to being in front of all sprites, which messes up fade effects and such. And why doesn't loving/favoriting projects show up in recent activity anymore?

Aside from actual functional issues that shouldn't exist in a final release, it seems to me that there have been changes for the sake of changes. What I mean can be shown by things like the flag and stop sign. They are now swapped with the full-screen button so that they are on the left, instead of the right, for no logical reason other than to be different than 2.0. This doesn't help with transitioning. The stage being locked to the right inside the editor is different to be different, and the scripts and tab buttons were moved as well.

And then there's the new style of it all. It's massive and impossible to fit everything on the screen at once, with bright annoying colors and huge blocks and tons of buffer space between comments and descriptions and stuff. It's just poorly used space for the sake of it. I have to zoom out to 90% to even fit the whole costume editor on my screen. I have a 15.6“ monitor, which isn't terribly small, and yet I can't see anything at 100%. The ”add sprite" button now covers whatever sprite is to the far right in the scrolling list, which is annoying and makes everything harder to see and click. It's cumbersome to use and look at, and all for few new features.

New features are minimal. Experimenting with the editor, all I've found so far are things I could do in 2.0, but not in 3.0. Please correct me if I'm wrong, but it seems underwhelming.

To end positively, at least projects run much faster. Working on mobile is a nice touch, or it would be, if it worked, but as of a few hours ago it just breaks the page if you try to open a project.

But as I was saying, there is minimal lag now. Yay for that, at least.

Overall, though, it feels unfinished and under-polished, and I haven't enjoyed it thus far.

Mainly, though, can anyone help my save my project?

I hope that 3.0 can be improved, because visually, it does look more modern, if less functional, and HTML5 is much better than Flash. The new project pages are nice, aside from the lack of an ability to see the remix tree or even a complete list of remixes and studios.

I'm sure I'm not the first to voice these complaints, but I felt that if I could compile my complaints in one place it might help myself and others to get a general idea for feelings on 3.0. And if enough people complain about a feature, with some luck, the ST might add it back.

Oh, and one more thing: the “revamped” or “improved” or whatever backpack is exactly the same as before, minus whatever we had in it. Next time, I'd have a clearer message, perhaps something that appears in our inbox, that they were going to be wiped. A featured project could be easily missed and I'm lucky to have seen it.

Thanks for reading to here, if you did. I'm only writing all this because I want a working site that can do what we did before.

That's it for me.
-Toad

Once again, please help me save if you can. Any ideas?

I can only say that I agree. They should have made sure that ALL features included in version 2, were ready before releasing version 3. Changing to Scratch 3.0 is not an upgrade at all to me. Nice thet you can use it on a tablet; but I didn't need that. Nice that you can program Micro:Bit and Lego Mindstorms, but I do not need that.

I need my old projects to work, to look the same graphically, and I need to be able to make new projects and use the same features that were available in Scratch 2.0 (for example, the center costume feature, the save offline feature, ….). All the things Toad mentioned in his post.

So please, Scratch Team, remedy the situation and make ALL Scratch 2.0 features available again. I can adjust to the flashy, screamy color scheme, I can adjust to the switching of screens in the editor, but I cannot work when certain basic features are unavailable.

CooleMDH wrote:

I can only say that I agree. They should have made sure that ALL features included in version 2, were ready before releasing version 3. Changing to Scratch 3.0 is not an upgrade at all to me. Nice thet you can use it on a tablet; but I didn't need that. Nice that you can program Micro:Bit and Lego Mindstorms, but I do not need that.

I need my old projects to work, to look the same graphically, and I need to be able to make new projects and use the same features that were available in Scratch 2.0 (for example, the center costume feature, the save offline feature, ….). All the things Toad mentioned in his post.

So please, Scratch Team, remedy the situation and make ALL Scratch 2.0 features available again. I can adjust to the flashy, screamy color scheme, I can adjust to the switching of screens in the editor, but I cannot work when certain basic features are unavailable.

+1 to this. Thanks for support.

I fully agree. It really seems like 3.0 was rushed out the door before Flash was completely removed from most browsers, but that's no excuse for a net loss of features. A few extra months in the metaphorical oven would still give plenty of leeway for the transition from Flash to HTML5.

3.0 just isn't right for me. I hope that Scratch soon improve it. Something more hilarious is the fact that the Scratch 3.0 we have now is literally nothing different to the beta we got in July. They said they were working on it!

I agree as well… Those features need to be brought back! Although I think we should give them time since scratch 3.0 is pretty much new and that they're still actively working on it…

Also here's a list of things that are missing/replaced on the new editor:
1. A missing maximum/minimum value for slider variables (there is a workaround, but they're no better than the option that was given simply due to lack of scalability on the slider var). This is used on some 2.0 projects
2. ‘Can drag in player’ is removed (there is a workaround). This is used on some 2.0 projects
3. CTRL + Pressing Green flag no longer mutes project
4. Shift + Pressing Edit no longer shows options where some of them are shown below
5. You can no longer export transition strings/help screen names
6. You can no longer edit block colors
7. MediaLib is also removed
8. Tool buttons are gone
9. Like I said, tool buttons are gone, but stamp button is removed entirely from the editor. You now have to do copy and paste.

Give them time? They should have implemented it BEFORE taking Scratch 2.0 offline and force everyone to start using 3.0
This version just isn't ready for release. This is not about bugs, it is about important stuff completely missing.

Give them time to correct bugs and glitches: agreed.
Give them time to develop necessary features that were present in the previous version after release: don't agree.

Also the changing the color scheme is a HUGE impact for all educators / Coderdojos around the world that have spent hours on developing free course materials. All the volunteers will loose hours, even days with adapting everything they developed. Books that were bought with the little money that was available now show the wrong colors, so kids can no longer use the colors to find the correct blocks. Young children go by the colors, rather than reading all the text on the screen.

I sorely miss the embedding feature, and all the previous embeddings I did in my blog are now broken.

Has Scratch 3 become a walled garden?

Phanthomphax wrote:

I agree as well… Those features need to be brought back! Although I think we should give them time since scratch 3.0 is pretty much new and that they're still actively working on it…

Also here's a list of things that are missing/replaced on the new editor:
1. A missing maximum/minimum value for slider variables (there is a workaround, but they're no better than the option that was given simply due to lack of scalability on the slider var). This is used on some 2.0 projects
2. ‘Can drag in player’ is removed (there is a workaround). This is used on some 2.0 projects
3. CTRL + Pressing Green flag no longer mutes project
4. Shift + Pressing Edit no longer shows options where some of them are shown below
5. You can no longer export transition strings/help screen names
6. You can no longer edit block colors
7. MediaLib is also removed
8. Tool buttons are gone
9. Like I said, tool buttons are gone, but stamp button is removed entirely from the editor. You now have to do copy and paste.

I will add some (I think these haven't been mentioned by you yet)
10. ‘Save to local file’ is gone
11. Select a certain area of sound is gone therefore making it harder to edit sounds
12. ‘Remove Background’ is removed from bitmap editor
Those are all I can see at the moment.

I 100% Agree. I guess they rushed 3.0 without taking the time to make sure everything works. I thought new versions are supposed to be better.

I'm gonna cut the ST some slack here, because 2.0 already had some bugs just due to flash, like inconsistent timing. Writing a programming language is hard, even if you have the blueprint on how to do so. I think the problem the ST is facing is that they're trying to make a programming language (3.0) that is almost the same as a previous language they wrote (2.0) but is also compatible with it. Not to mention they have to do it in a different base language. (HTML as opposed to Flash)

It's kind of like making a soup. Then making a very similar soup, but with different ingredients, while also making it taste the same as the first one. Not to mention that you have to make the new soup as quickly as possible before the first soup becomes stale.
Sorry if you don't understand the analogy, I tried my best.

So, cut the ST some slack. They worked hard on 3.0 and In my opinion, It's good.

ToadTV wrote:

You read the title. 3.0 is a bit problematic. It feels like using a beta, except it's the full site and there's no way to avoid it.

My main issue is that there are tons of missing features that we had in 2.0: remix trees, tags, sound editor features, save to local file, project restore, centering in costume editor, embedding projects, and numerous other things I'm sure.
Is it too much to ask to have the new version at least include the features of the old one?

Actually, my main issue is that I can't save one (or more) project(s). I edit something, click save, and it loads for 30 seconds or so before crashing the page.
That's really useful.

My other projects save fine, albeit much slower than in 2.0, but this one doesn't work. It was right around 49.5 MB in 2.0, near to the project limit. Has the size limit been lowered? Or has it been corrupted somehow? I've been working on it for months on end and will not be pleased if it's broken.

And there are obvious visual bugs that weren't there in 2.0. Everything is blurry and offset, especially text. Exactly whose idea was it to replace the fonts with new ones with different spacing than the old ones? Centered text is now to the side, some overlaps with button edges, and generally looks bad.
Also, variables now default to being in front of all sprites, which messes up fade effects and such. And why doesn't loving/favoriting projects show up in recent activity anymore?

Aside from actual functional issues that shouldn't exist in a final release, it seems to me that there have been changes for the sake of changes. What I mean can be shown by things like the flag and stop sign. They are now swapped with the full-screen button so that they are on the left, instead of the right, for no logical reason other than to be different than 2.0. This doesn't help with transitioning. The stage being locked to the right inside the editor is different to be different, and the scripts and tab buttons were moved as well.

And then there's the new style of it all. It's massive and impossible to fit everything on the screen at once, with bright annoying colors and huge blocks and tons of buffer space between comments and descriptions and stuff. It's just poorly used space for the sake of it. I have to zoom out to 90% to even fit the whole costume editor on my screen. I have a 15.6“ monitor, which isn't terribly small, and yet I can't see anything at 100%. The ”add sprite" button now covers whatever sprite is to the far right in the scrolling list, which is annoying and makes everything harder to see and click. It's cumbersome to use and look at, and all for few new features.

New features are minimal. Experimenting with the editor, all I've found so far are things I could do in 2.0, but not in 3.0. Please correct me if I'm wrong, but it seems underwhelming.

To end positively, at least projects run much faster. Working on mobile is a nice touch, or it would be, if it worked, but as of a few hours ago it just breaks the page if you try to open a project.

But as I was saying, there is minimal lag now. Yay for that, at least.

Overall, though, it feels unfinished and under-polished, and I haven't enjoyed it thus far.

Mainly, though, can anyone help my save my project?

I hope that 3.0 can be improved, because visually, it does look more modern, if less functional, and HTML5 is much better than Flash. The new project pages are nice, aside from the lack of an ability to see the remix tree or even a complete list of remixes and studios.

I'm sure I'm not the first to voice these complaints, but I felt that if I could compile my complaints in one place it might help myself and others to get a general idea for feelings on 3.0. And if enough people complain about a feature, with some luck, the ST might add it back.

Oh, and one more thing: the “revamped” or “improved” or whatever backpack is exactly the same as before, minus whatever we had in it. Next time, I'd have a clearer message, perhaps something that appears in our inbox, that they were going to be wiped. A featured project could be easily missed and I'm lucky to have seen it.

Thanks for reading to here, if you did. I'm only writing all this because I want a working site that can do what we did before.

That's it for me.
-Toad

Once again, please help me save if you can. Any ideas?

In your post you mentioned embedding projects. If you want to do that you can type <iframe src=“scratch.mit.edu/projects/1234567/fullscreen” width=“WIDTH” height=“HEIGHT”></iframe> into HTML This is basically the same, but more customizable.

venyanwarrior wrote:

I'm gonna cut the ST some slack here, because 2.0 already had some bugs just due to flash, like inconsistent timing. Writing a programming language is hard, even if you have the blueprint on how to do so. I think the problem the ST is facing is that they're trying to make a programming language (3.0) that is almost the same as a previous language they wrote (2.0) but is also compatible with it. Not to mention they have to do it in a different base language. (HTML as opposed to Flash)

It's kind of like making a soup. Then making a very similar soup, but with different ingredients, while also making it taste the same as the first one. Not to mention that you have to make the new soup as quickly as possible before the first soup becomes stale.
Sorry if you don't understand the analogy, I tried my best.

So, cut the ST some slack. They worked hard on 3.0 and In my opinion, It's good.

I do agree, it is hard! I once tried coding HTML and… I used a book to code only the actual page (no buttons or anything), but changed what they did. But I do feel a little disappointed with the features, although I really like the new look!
Well done on the new update ST! -Minty

I fully give support. The new version lacks many features, and I can’t tell if it’s to ‘make the site easier to understand, or if it’s just the scratch team being lazy (no offense).

- Scratch 3.0 does not let you create gradients with the fill tool.
- Scratch 3.0 audio editor is hot garbage.
- No helvetica - ruins the look of most of my projects
- No swatches for color selecting
- You can no longer import a graphic directly inside another graphic
these are a few of my gripes with the new scratch

however there are some good things such as how audio can now be in stereo

Minty_Cat_56 wrote:

Phanthomphax wrote:

I agree as well… Those features need to be brought back! Although I think we should give them time since scratch 3.0 is pretty much new and that they're still actively working on it…

Also here's a list of things that are missing/replaced on the new editor:
1. A missing maximum/minimum value for slider variables (there is a workaround, but they're no better than the option that was given simply due to lack of scalability on the slider var). This is used on some 2.0 projects
2. ‘Can drag in player’ is removed (there is a workaround). This is used on some 2.0 projects
3. CTRL + Pressing Green flag no longer mutes project
4. Shift + Pressing Edit no longer shows options where some of them are shown below
5. You can no longer export transition strings/help screen names
6. You can no longer edit block colors
7. MediaLib is also removed
8. Tool buttons are gone
9. Like I said, tool buttons are gone, but stamp button is removed entirely from the editor. You now have to do copy and paste.

I will add some (I think these haven't been mentioned by you yet)
10. ‘Save to local file’ is gone
11. Select a certain area of sound is gone therefore making it harder to edit sounds
12. ‘Remove Background’ is removed from bitmap editor
Those are all I can see at the moment.

1. Is needed
2. Is not necessary, due to the fact that there is a block to use that sprite mode
3. Is not necessary, just use the volume block or turn your computer's volume down to 0
4. Is not necessary
5. Is not necessary, probably because it would have been complicated for New Scratchers to use
6. Is not necessary, the feature in Scratch 2 was only temporary and wasn't used too much
7. Is not necessary, it wasn't used too much
8. Should be necessary, but the workarounds seem easier to do
9. (Read 8)
10. Not sure, you can already upload projects to your computer and load them
11. Is needed, was used very often with Scratchers that use 2.0
12. Is not necessary, you can already select the transparent color and then clear everything or use the eraser to erase everything

I'm having trouble with 3.0 too. I can't even get into any projects, and some of the changed stuff just seems.. useless.

im sameposting but tbf what i said was actually important (especially regarding gradients & swatches)

RCScratch wrote:

im sameposting but tbf what i said was actually important (especially regarding gradients & swatches)

To use gradients select one of the gradient options at the top of colour select.


Scratch 3.0 is missing lots of things, but they will get added. It's better to let people be able to use Scratch more and have more testing.

There are a lot of different points to keep track of here, but let me at least say, we take your feedback and concerns seriously, and we're working hard to make Scratch 3.0 be awesome for everyone.

@ToadTV, what is the project url that you're having trouble with?

@Phanthomphax, you should still be able to set a sprite to be draggable in the player, using a block in the Motion section.

@Minty_Cat_56, you should still be able to save a project to a file.