At this point, fixing the editor and 2.0 pages would be better (in my opinion) than getting anything shiny and cool and new (unless it’s something that assists with creating games like onion skinning or accessibility like website colors)
Because to name every known glitch happening so far…
Cloud variables are down, the Front page is half dead, 2.0 pages constantly log people out, everytime you duplicate a sprite it magically vanishes the SECOND you touch it (which sucks if you’re making a layered UI), The ST somehow managed to break every extension under the sun that has cat blocks, the “Create” button (don’t know if this is still going) will sometimes redirect to the “Oops! Our server is scratching its head”, Set thumbnail the past few months has been going on and off not working, the Message box will sometimes display a error message, the Studio’s project button is constantly highlighted, Profile comments do not work (either comments keep hiding or coming back after being deleted), Sprites get heavily pixelated if they are under 50.1 in size, SVG files are not properly read, Sprite3 files (the file type used for scratch sprites) despite being used to import to scratch are instead greyed out, go to x () y () displaying wrong or otherwise outdated values, sometimes the x and y values in the sprite settings do not change and instead reset to the previous location upon trying to be changed, and yet if the ST wants to make the site accessible, it needs to not be frustrating and reliable to use at times. I understand the ST cannot be perfect, but if they are trying to add AI, work on a new version, and adding paywalled features whilst the website is not working too well, thats just strange to me. And even if Scratch 4.0 may be better, who may know what may happen in the 2 years it’s taking to release it?

Support.

This.

I do think that adding features like face sensing over something that's more convenient is uh.. Something. Not that face sensing is bad or anything, I just think that onion skinning could not only help with games (like you said), but for animators, people who primarily use Scratch to make art, and probably for other things that I can't think of. Accessibility colors and being able to adjust those depending on what fits better depending on the user is definitely better than just changing the website to purple. There was a post on this forum by a colorblind person on how the purple made it harder to see, so I agree with you on the accessibility colors if it's the adjustment that you meant.

There's a lot of other features that would be more convenient. With some that would make the website better and would positively contribute to Scratch's cause. Full support. I understand that the ST are in limited supply and they are humans with actual lives, but I definitely think things like dark mode, fixing the weird ghost message thing, and a lot other really useful things should be taken into consideration and implemented. Even if it takes a while to do so, I and probably many other Scratchers would be happy to wait if it meant something better than an AI assistant was coming around. Just even taking the time to fix bugs even if it meant no new features for a bit would be nice. When I reply to things, there's this huge chance the comments don't load if it's on a profile or the comment just flat out disappears when it DOES load (on both pages). Again, the ghost messages are very annoying. I also just don't like whenever something in bitmap is converted into vector and all these transparent pixels appear. This was not an issue before. This also happens in vice versa as well, which has also not happened before. Bugs being fixed would be amazing.

Now the editor is basically unusable because upon clicking one of my sprites 2 more are hidden and the back layer is moved and sent to the front. I hope the ST sees this.

Scratch_Cat_Coder8 wrote:

At this point, fixing the editor and 2.0 pages would be better (in my opinion) than getting anything shiny and cool and new (unless it’s something that assists with creating games like onion skinning or accessibility like website colors)
Because to name every known glitch happening so far…
Cloud variables are down, the Front page is half dead, 2.0 pages constantly log people out, everytime you duplicate a sprite it magically vanishes the SECOND you touch it (which sucks if you’re making a layered UI), The ST somehow managed to break every extension under the sun that has cat blocks, the “Create” button (don’t know if this is still going) will sometimes redirect to the “Oops! Our server is scratching its head”, Set thumbnail the past few months has been going on and off not working, the Message box will sometimes display a error message, the Studio’s project button is constantly highlighted, Profile comments do not work (either comments keep hiding or coming back after being deleted), Sprites get heavily pixelated if they are under 50.1 in size, SVG files are not properly read, Sprite3 files (the file type used for scratch sprites) despite being used to import to scratch are instead greyed out, go to x () y () displaying wrong or otherwise outdated values, sometimes the x and y values in the sprite settings do not change and instead reset to the previous location upon trying to be changed, and yet if the ST wants to make the site accessible, it needs to not be frustrating and reliable to use at times. I understand the ST cannot be perfect, but if they are trying to add AI, work on a new version, and adding paywalled features whilst the website is not working too well, thats just strange to me. And even if Scratch 4.0 may be better, who may know what may happen in the 2 years it’s taking to release it?

Scratch_Cat_Coder8 wrote:

At this point, fixing the editor and 2.0 pages would be better (in my opinion) than getting anything shiny and cool and new (unless it’s something that assists with creating games like onion skinning or accessibility like website colors)
Because to name every known glitch happening so far…
Cloud variables are down, the Front page is half dead, 2.0 pages constantly log people out, everytime you duplicate a sprite it magically vanishes the SECOND you touch it (which sucks if you’re making a layered UI), The ST somehow managed to break every extension under the sun that has cat blocks, the “Create” button (don’t know if this is still going) will sometimes redirect to the “Oops! Our server is scratching its head”, Set thumbnail the past few months has been going on and off not working, the Message box will sometimes display a error message, the Studio’s project button is constantly highlighted, Profile comments do not work (either comments keep hiding or coming back after being deleted), Sprites get heavily pixelated if they are under 50.1 in size, SVG files are not properly read, Sprite3 files (the file type used for scratch sprites) despite being used to import to scratch are instead greyed out, go to x () y () displaying wrong or otherwise outdated values, sometimes the x and y values in the sprite settings do not change and instead reset to the previous location upon trying to be changed, and yet if the ST wants to make the site accessible, it needs to not be frustrating and reliable to use at times. I understand the ST cannot be perfect, but if they are trying to add AI, work on a new version, and adding paywalled features whilst the website is not working too well, thats just strange to me. And even if Scratch 4.0 may be better, who may know what may happen in the 2 years it’s taking to release it?

Kinda support, but uh, isn't this gonna like slow Scratch 4.0/New extensions from coming out faster? I'm kind of sick of using the same old blocks over and over again, but still… I guess I support this???

doyouknowjasher441 wrote:

Scratch_Cat_Coder8 wrote:

-snip

Scratch_Cat_Coder8 wrote:

-snip-

Kinda support, but uh, isn't this gonna like slow Scratch 4.0/New extensions from coming out faster? I'm kind of sick of using the same old blocks over and over again, but still… I guess I support this???

4.0 and new extensions should be the least of your worries. If so many bugs have been popping up more frequently in a short while, who knows what will happen if they are ignored/slowed down for another 2 years?
Also don't quote the first post as it just clutters up your post more.

Let's not forget the indexer hasn't worked since what, July? So no new projects are showing up in search.

I would really like them to focus on fixing bugs instead of all the other stuff. I actually came here to make this very suggestion until I saw it here. The bugs make scratch look like an unpolished mess by other people so they wouldn't be likely to start using it.

Plus, who would want a membership on a buggy website anyway? It would be hard for me to be fully confident in scratch being able to give new membership features consistently if they had to deal with all these other problems on top of it.

If only it was possible to insert the scratch 3.0 header on scratch 2.0 pages

Support. I have noticed things have changed recently since I lasted used the website and already I can see that some things are not right or working properly or not functioning the way they’re supposed to, not to mention how out of place the membership is the way they’re advertising it currently.

Not only have they been adding things in and promoting the Scratch membership and the new features and early access sprites, the site has never been so buggy and broken when I was last on it.

And the 3.0 nav bar just looks bloated with the membership button being added there as well. I don’t like the direction they are taking this thing in.

I definitely agree that it would be nice if scratch could try to fix the plethora of bugs instead of adding more not particularly interesting features like face sensing.

All these new features that are supposed to increase the “quality”, “creativity” and “safety” of this site are just replacing all chances we'll get of a site that doesn't have a massive bug in every other corner of it.

Total support.

_--_-_-_-_-_-_--_ wrote:

Scratch_Cat_Coder8 wrote:

-oof-

I 100% support. They could include this in the 4.0 update next year.

Support

Pls don't quote the original post.

This doesn't apply to every issue listed in this thread, but one thing worth noting is that it *is* worth upgrading to something more “flashy” if in the process it fixes the issue or otherwise paves the way to make fixing the issue easier.

I don't know the details, but I seem to recall hearing that Scratch 3.0 pages are much easier to work with maintenance-wise than Scratch 2.0 pages. So, as an incredibly gross oversimplification, consider the following two hypothetical options:

• Option 1: Suppose it takes 1 week each to fix any bugs with the 2.0 website.
  
  
• Option 2: Suppose it takes 1 month to upgrade all 2.0 pages to 3.0, then it takes 2 days each to fix any bugs with the 3.0 website.
  

When it comes to website maintenance in the long run, I imagine that Option 2 is much better.

This is why I am interested in seeing what Scratch 4.0 is going to look like. While I don't know for sure, I bet the editor is going to look different and have many changes/fixes … more than just the AI assistant. If all these issues are going to be fixed in the new version, why fix them separately in the old version? Again, (for example, hypothetically) it would be better to take 2 years to release Scratch 4.0 with some fixed issues, than it would be to take 1 year to fix some of the Scratch 2.0/3.0 issues and then start 4.0…

Most problems are in Scratch-WWW pages.

I've got the log out bug on 3.0 pages too :/

Scratch_Cat_Coder8 wrote:

The ST somehow managed to break every extension under the sun that has cat blocks

That happened because they made it member locked (the famous one fixed the issue though)

Scratch_Cat_Coder8 wrote:

Now the editor is basically unusable because upon clicking one of my sprites 2 more are hidden and the back layer is moved and sent to the front. I hope the ST sees this.

Yeah for some reason I'm able to drag sprites behind other sprites at times LOL
My browser / operating system: MacOS 11.3, Chrome 138.0.0.0, No Flash versions detected
My browser / operating system: Windows Vista, Firefox 146.0, No Flash versions detected

Za-Chary wrote:

This doesn't apply to every issue listed in this thread, but one thing worth noting is that it *is* worth upgrading to something more “flashy” if in the process it fixes the issue or otherwise paves the way to make fixing the issue easier.

I don't know the details, but I seem to recall hearing that Scratch 3.0 pages are much easier to work with maintenance-wise than Scratch 2.0 pages. So, as an incredibly gross oversimplification, consider the following two hypothetical options:

• Option 1: Suppose it takes 1 week each to fix any bugs with the 2.0 website.
  
  
• Option 2: Suppose it takes 1 month to upgrade all 2.0 pages to 3.0, then it takes 2 days each to fix any bugs with the 3.0 website.
  

When it comes to website maintenance in the long run, I imagine that Option 2 is much better.

This is why I am interested in seeing what Scratch 4.0 is going to look like. While I don't know for sure, I bet the editor is going to look different and have many changes/fixes … more than just the AI assistant. If all these issues are going to be fixed in the new version, why fix them separately in the old version? Again, (for example, hypothetically) it would be better to take 2 years to release Scratch 4.0 with some fixed issues, than it would be to take 1 year to fix some of the Scratch 2.0/3.0 issues and then start 4.0…

I mean flashy as in like extremely cool stuff that wouldnt fix anything. Updating the pages to 3.0 would more solely be fixing rather than random flashy stuff

Za-Chary wrote:

This doesn't apply to every issue listed in this thread, but one thing worth noting is that it *is* worth upgrading to something more “flashy” if in the process it fixes the issue or otherwise paves the way to make fixing the issue easier.

I don't know the details, but I seem to recall hearing that Scratch 3.0 pages are much easier to work with maintenance-wise than Scratch 2.0 pages. So, as an incredibly gross oversimplification, consider the following two hypothetical options:

• Option 1: Suppose it takes 1 week each to fix any bugs with the 2.0 website.
  
  
• Option 2: Suppose it takes 1 month to upgrade all 2.0 pages to 3.0, then it takes 2 days each to fix any bugs with the 3.0 website.
  

When it comes to website maintenance in the long run, I imagine that Option 2 is much better.

This is why I am interested in seeing what Scratch 4.0 is going to look like. While I don't know for sure, I bet the editor is going to look different and have many changes/fixes … more than just the AI assistant. If all these issues are going to be fixed in the new version, why fix them separately in the old version? Again, (for example, hypothetically) it would be better to take 2 years to release Scratch 4.0 with some fixed issues, than it would be to take 1 year to fix some of the Scratch 2.0/3.0 issues and then start 4.0…

So what I'm getting here… Sorry if I made mistakes this post was kinda hard to read…

Is that, all the current and older scratch versions are gonna be buggy forever and we're all gonna have to wait months if not years for the newer version where the only real difference is that it's turbowarp but with a bunch of bad features no one asked for.

That's the message I'm getting here and from all the other things that have been happening recently.

1.) KOTP, No edit
2.) This is why Scratch Membership is not worth it. The website becomes more and more broken with every passing day and Scratch hasn't done anything innovative in the past 5 years aside from removing features and breaking others. I'm in full support and this full support of holding Scratch accountable and make them actually listen to their userbase.

coder2310 wrote:

So what I'm getting here… Sorry if I made mistakes this post was kinda hard to read…

Is that, all the current and older scratch versions are gonna be buggy forever and we're all gonna have to wait months if not years for the newer version where the only real difference is that it's turbowarp but with a bunch of bad features no one asked for.

That's the message I'm getting here and from all the other things that have been happening recently.

That's a bit of an exaggeration/extrapolation. My point is just that sometimes it is worth “killing two birds with one stone,” so to speak, even if by doing so it will take a little longer than “killing one bird.”