Za-Chary wrote:

MaximunPokeMaster wrote:

-snip-

This one I'll have to disagree with you on.

There's a lot of people who think the Scratch Team should go back to 2.0, or perhaps they should allow users to switch between the two editors. Such requests happen not only on the forums, but on the Scratch website itself as well.

This suggestion is good to include, as it gives reasons for why it's rejected, and really is commonly suggested. I don't think I'll be removing it, at least not any time soon. The same goes for #2.3.

Za-Chary wrote:

1.5 Cloud Lists
Cloud variables currently have several restrictions. There can be at most 10 cloud variables per project due to server costs. New Scratchers cannot use cloud variables, for it is easy to misuse them. Cloud variables can only support up to 256 numeric digits so it is harder to create chat projects; for more information, see #3.1 on this list.

Cloud lists would require similar restrictions, and the issues currently presented with cloud variables would only grow with the addition of cloud lists. You can still use cloud variables to create a list which contains entries everyone can see, but the Scratch Team will not be adding an official, easy way to make cloud lists.

noogai34 wrote:

“disable remixing”
@scratchitout1 “nullifies my remixes”. 1st there was a no, then there was “STOP INTERLUDING”. Does this come on to the list of rejections?

Za-Chary wrote:

noogai34 wrote:

“disable remixing”
@scratchitout1 “nullifies my remixes”. 1st there was a no, then there was “STOP INTERLUDING”. Does this come on to the list of rejections?

Can you explain what you mean by “nullifying your remixes”?

If that user is trying to prevent you from remixing their project, they cannot do that. If you see a project that says “NO REMIXING”, you can report it.

Celestial_Candy wrote:

Well, sometimes people worked really hard on a thing, so they don't want people to remix them.

Za-Chary wrote:

Celestial_Candy wrote:

Well, sometimes people worked really hard on a thing, so they don't want people to remix them.

When you share a project on Scratch, you agree that anyone can remix it. As long as they change something about the remix and give proper credit, it is a valid remix.

You cannot prevent people from remixing your projects; it goes against the Terms of Use. If you make a project and don't want anyone to remix it, then you should not share the project on Scratch.

StrangeMagic32 wrote:

though I do believe you are allowed to say, “Please don't remix this, thanks.” because it's not a demand, where as saying, “DON'T REMIX THIS!” is a demand, but I'm not 100% sure…

Za-Chary wrote:

StrangeMagic32 wrote:

though I do believe you are allowed to say, “Please don't remix this, thanks.” because it's not a demand, where as saying, “DON'T REMIX THIS!” is a demand, but I'm not 100% sure…

That's not correct, either. It certainly sounds nicer, but there is no way to prevent people from remixing your projects, and I'm still pretty sure you can get reported for trying to prevent remixing.

Za-Chary wrote:

2.3 Set the editor to look like older versions of Scratch
Some users prefer the look and feel of the Scratch 2.0 editor, and have suggested that the editor look like Scratch 2.0, but still run off of HTML5 like Scratch 3.0 does. However, this would be more complicated for educational purposes, and would also require that the Scratch Team maintain twice as much code as they already do. Simply put, the Scratch Team does not have the resources to manage such a customizable interface.

Alzter wrote:

Za-Chary wrote:

2.3 Set the editor to look like older versions of Scratch
Some users prefer the look and feel of the Scratch 2.0 editor, and have suggested that the editor look like Scratch 2.0, but still run off of HTML5 like Scratch 3.0 does. However, this would be more complicated for educational purposes, and would also require that the Scratch Team maintain twice as much code as they already do. Simply put, the Scratch Team does not have the resources to manage such a customizable interface.

I don't understand how this makes sense. There's user-scripts that make Scratch 3.0 look more similar to 2.0 and they don't take “twice as much code as 3.0 does”. We just want a 2.0 THEME for Scratch 3.0 that modifies certain UI elements and block size to make Scratch 3.0 more familiar to 2.0 users.

Paddle2See* wrote:

The way I read it was that they wanted to be able to switch between 2.0 and 3.0, as far as the look and feel of the editor goes. To me that, sounds like a lot of complexity, both for the coders, but also for anybody trying to write documentation or teach Scratch.

thisandagain* wrote:

We are not considering a “skin” that switches between the look of 2.0 and 3.0, but we may consider being able to toggle which side of the screen the stage is on.

congyingzhou wrote:

Your 7.1 link leads to the second page of the topic. Could you change it so it leads to the first?

Yeetkinglord910 wrote:

(7.1 Changing usernames) the scratch team could just add a feature on their side where they can see the username history a scratcher has like in ROBLOX

Za-Chary wrote:

Yeetkinglord910 wrote:

(7.1 Changing usernames) the scratch team could just add a feature on their side where they can see the username history a scratcher has like in ROBLOX

It's not quite that simple. The Scratch Team just doesn't have the resources or systems to make a username changing system.

MaximunPokeMaster wrote:

Za-Chary wrote:

Yeetkinglord910 wrote:

(7.1 Changing usernames) the scratch team could just add a feature on their side where they can see the username history a scratcher has like in ROBLOX

It's not quite that simple. The Scratch Team just doesn't have the resources or systems to make a username changing system.

not to mention that it would still be confusing for non-ST members, because they don't have access to the history.

Rejected Suggestion wrote:

4.1 Disable “See Inside” or restrict sharing
Some users want an option to prevent Scratchers from looking inside their project and using their artwork, scripts, or sounds (perhaps to hide surprises or prevent users from cheating). However, the motto of Scratch is “Imagine – Program – Share”. By sharing a project on the Scratch website, you are allowing others to see the code and potentially remix or reuse the data inside, as long as they give credit. (Please report any projects that do not seem to give credit for assets they did not make.) If you do not want other users to see inside your project, then do not share your project on the Scratch website.

Restricting sharing so that only certain users can view the project is also not going to be implemented. It is important for projects to be publicly shared for everyone to see so that people can report them if they are inappropriate. Only allowing certain users to view projects could increase the chance that inappropriate projects can be shared on the website, and this is an Internet safety issue. It could also be used for private messaging; for more information, see #6.1 on this list.

Terms Of Use wrote:

4.3 All user-generated content you submit to Scratch is licensed to and through Scratch under the Creative Commons Attribution-ShareAlike 2.0 license. This allows others to view and remix your content. This license also allows the Scratch Team to display, distribute, and reproduce your content on the Scratch website, through social media channels, and elsewhere. If you do not want to license your content under this license, then do not share it on Scratch.

hani2018 wrote:

I think you have to change the part were you said your not a member of the scratch team cause you are now