PrincessIsza wrote:

(#9280)
Where is tolors?

PrincessIsza wrote:

han614698 wrote:

PrincessIsza wrote:

(#9277)

8to16 wrote:

1.9 doesn't have a loop arrow icon, it should be this:

forever if <> {

} @loopArrow :: control cap

Fixed scratchblocks:

forever if <> {

} @loopArrow :: control cap

What is Scratch 1.9?

I don't believe 8to16 is referring to Scratch 1.9, but rather item 1.9 on TOLORS.

Where is tolors?

ToyBird_255 wrote:

mmm glass
~snip~ add glass

Za-chary wrote:

PLEASE DO NOT SUGGEST THINGS HERE!
I am not a member of the Scratch Team; your suggestion will get more attention if you make your own topic about it. Also, please do not spam or create off-topic posts, or else they may be deleted.

The-Sushi-Cat wrote:

Ban Off Topic Commenting Is rejected! (I know it probably won't be added, but you still gotta know-)

Edit: Dustbinned :thumbs_up:

Scratch137 wrote:

PrincessIsza wrote:

(#9280)
Where is tolors?

TOLORS is short for “The Official List of Rejected Suggestions.” That's where we are right now.

randomguy3513 wrote:

The-Sushi-Cat wrote:

Ban Off Topic Commenting Is rejected! (I know it probably won't be added, but you still gotta know-)

Edit: Dustbinned :thumbs_up:

It has to be commonly suggested to be on the list.

za-charry wrote:

Please also update me on any recently-rejected suggestions so we can discuss whether or not to add them to this list. Even if a suggestion is infrequently suggested or it is “obviously rejected,” it's still helpful for me to see that the suggestion exists. I will do my best to regularly update and revise the list as needed. In addition, feel free to tell me if there are any spelling mistakes or formatting errors. Other general feedback is appreciated as well.

8to16 wrote:

1.9 doesn't have a loop arrow icon, it should be this:

forever if <> {

} @loopArrow :: control cap

PrincessIsza wrote:

(#9285)

Scratch137 wrote:

PrincessIsza wrote:

(#9280)
Where is tolors?

TOLORS is short for “The Official List of Rejected Suggestions.” That's where we are right now.

Oh

<(message v) received? :: events>

<pointing towards (sprite v)? :: sensing>

[scratchblocks]
<(message v) received? :: events>
[/scratchblocks]

[scratchblocks]
<pointing towards (sprite v)? :: sensing>
[/scratchblocks]

3.2 Disable remixing or censor minor remixes
One of the most important ideas of Scratch is the share aspect. Scratch is a website not only for displaying your work, but also for sharing it with others, and by posting your project on the Scratch website you agree to allow others to remix your work. You are not allowed to write “Do not remix this project” in the Notes and Credits of your project; you may get alerted for this, because it discourages remixing. This suggestion extends to the ability to require permission to remix a project, as you have already given permission to others to use your creations by sharing a project on Scratch; for more information, see this post.

A remix of a project is allowed on Scratch, even if the remix only contains minor changes (this includes recolors). However, when you remix a project, you should put in the Notes and Credits what you changed. If you see a project that contains no noticeable changes, please use the Report button on it so the Scratch Team can take a look at it. This suggestion extends to “extremely minor remixes,” such as a remix of a game that gives you 2 points per second instead of 1. As long as the user explains what they changed about the project and gives proper credit, this is okay.

However, a feature that prevents unchanged remixes from being shared is NOT rejected. You can discuss it on this topic.

crazyfrogcat wrote:

-snip-

so wait, is a disable sharing remix's of this project rejected?

7.1 Private messaging
Scratch currently has public messaging, meaning anyone can see the comments that you write. As a result, people are more likely to be respectful since anyone can see the comment. However, with private messaging, people know that only the intended recipient can see the message, which could lead to many more disrespectful or inappropriate comments. The Scratch Team also simply does not have the resources to moderate a private messaging system, precisely because there would be a lot of bad comments. In addition, it is a huge Internet safety concern and is not the purpose of Scratch anyway.

This suggestion extends to allowing users to post links to other private messaging websites. Many such messaging websites are not as well-moderated as Scratch is. If such links were allowed, Scratch may be held responsible if anything bad happens to someone. It also extends to voice chat capabilities on Scratch; for more information, see this post.

However, the ability to message others publicly in an area where nobody else can comment is NOT rejected. You can discuss it on this topic.

crazyfrogcat wrote:

-snip-
So is private messaging where people can only send other people a list of words approved by the scratch team rejected?

Catscratcher07 wrote:

randomguy3513 wrote:

The-Sushi-Cat wrote:

Ban Off Topic Commenting Is rejected! (I know it probably won't be added, but you still gotta know-)

Edit: Dustbinned :thumbs_up:

It has to be commonly suggested to be on the list.

za-charry wrote:

Please also update me on any recently-rejected suggestions so we can discuss whether or not to add them to this list. Even if a suggestion is infrequently suggested or it is “obviously rejected,” it's still helpful for me to see that the suggestion exists. I will do my best to regularly update and revise the list as needed. In addition, feel free to tell me if there are any spelling mistakes or formatting errors. Other general feedback is appreciated as well.

Super-Cat-Poderoso21 wrote:

Za-Chary wrote:

-snip of shame-

I made a Portuguese Version but there are some topics missing because I haven't finished doing it yet.

8to16 wrote:

(#9289)
could the “pointing towards sprite” and “broadcast received” block be changed to use insertable dropdown:

<(message v) received? :: events>

<pointing towards (sprite v)? :: sensing>

when I receive [message v]

Scratch137 wrote:

(#9300)

8to16 wrote:

(#9289)
could the “pointing towards sprite” and “broadcast received” block be changed to use insertable dropdown:

<(message v) received? :: events>

<pointing towards (sprite v)? :: sensing>

The “when I receive” block uses a non-insertable dropdown, so the first one can probably stay as it is now.

when I receive [message v]

broadcast (message v)