Gifted_Mess wrote:

Za-Chary wrote:

Gifted_Mess wrote:

Yeah, doesn't look like you missed anything but maybe change the formatting of the proof

Anything in particular you would suggest?

Maybe do like a quote then the proof, it is just more understandable in my mind for like the first one do this :
wait *looks*.,…..

Yeah you have the quote one just maybe find some for all of them

23: “When stop sign clicked” hat block
Some users want a block that looks like this, allowing users to click the stop sign to run a script:

when
stop
sign
clicked

However, the stop sign is designed to stop all the scripts in the project. With this block in place, more scripts will start when you want the project to stop, thus defeating the purpose of the stop sign. This could also be rather confusing for the “stop all” block. Regardless, there is a workaround that uses the “when (timer) > (number)” hat block.

FireyDeath4 wrote:

#43:

Why don't you just set your own clone limits???

SimpleScratch wrote:

What is this timer > number workaround?

when green flag clicked
forever
reset timer
end

when [timer v] > (0.3)
do stuff

Za-Chary wrote:

TABLE OF CONTENTS
This is a concise list of all the rejected suggestions, sorted into categories.

SCRATCH EDITOR

SCRATCH BLOCKS

• “Broadcast received” boolean block
  
• “When stop sign clicked” hat block
  
• 3D Scratch
  
• Digital currency or money blocks
  

CODING INTERFACE

• Text-based coding in Scratch
  
• Adding users to work on projects
  
• Set the editor to look like older versions of Scratch
  
• Revert back to older versions of Scratch
  

RESTRICTIONS AND LIMITS

• Remove the 50 MB project size limit
  
• Increase the 300 clone limit
  

PROJECTS AND STUDIOS

PROJECT PAGES

• Disable “See Inside” or restrict sharing
  
• Dislike button or a project rating system
  
• Delete or edit your comments on other users' projects
  
• Remove character limits on comments
  
• Notifications for viewing projects
  

STUDIO PAGES

• Remove studio activity messages
  
• Add an “invite all” button for studios
  
• Remove “add everything” or “invite everyone” studios
  

PROFILE PAGE

ACCOUNT STATUS

• Add a rank above Scratcher or remove the New Scratcher status
  
• Show when users are online
  
• Show when users are banned
  
• Delete inactive accounts
  

OTHER INFORMATION

• Changing username
  
• Blocking users
  
• Remove the location feature
  
• Game badges or achievements
  

DISCUSSION FORUMS

CATEGORIES AND ACCESS

• Bring back the “Discuss” tab
  
• Off-topic or miscellaneous section on the forums
  
• Remove the Suggestions forum
  

RESTRICTIONS AND MODERATION

• Remove the 60 Second Rule
  
• Remove restricted image hosts or add your own websites
  
• Show exact post count of other users
  
• Moderate mini-mods
  

MODERATOR ACTIONS

SCRATCH PROJECTS

• Blacklisted chat projects with cloud variables
  
• Ban minor remixes
  
• Ban projects with no coding
  
• Remove restrictions on Five Nights at Freddy's projects
  
• Ban a certain franchise
  
• Ban voice acting
  

SCRATCH COMMUNITY

• Private messaging
  
• Ban “follow for follow” (f4f)
  
• Remove the phone number censor
  
• Scratch Team members should not post political views
  
• A 13+ version of the Scratch website
  

NilsTheBest wrote:

Sorry for not snipping here, but what post I could be snipping is quite vague..
I saw your comment, and yes I do think that this is much more organized! You should put this system instead, but also keep the numbers so that we can easily find the rejected suggestion that corresponds to a given number..

Flipped_ wrote:

I saw a user saying that Paddle2See rejected a suggestion for a 16:9 aspect ratio. I'm not exactly sure how new Rejected Suggestions are added to the list, but maybe you could look into it and add 16:9 aspect ratio to the list? I can't find the topic anywhere.

Flipped_ wrote:

I saw a user saying that Paddle2See rejected a suggestion for a 16:9 aspect ratio. I'm not exactly sure how new Rejected Suggestions are added to the list, but maybe you could look into it and add 16:9 aspect ratio to the list? I can't find the topic anywhere.

Za-Chary wrote:

It would be nice if we could find the post that says it was rejected. That way I can look more into it.

Paddle2See wrote:

So far as I know, this suggestion hasn't been formally rejected.

StrangeMagic32 wrote:

Also here is a little of what Paddle2See has said about it.
https://scratch.mit.edu/discuss/post/3475949/

Paddle2See wrote:

So far as I know, this suggestion hasn't been formally rejected.

Za-Chary wrote:

Yep, you are right. Looks like this is NOT rejected.

Za-Chary wrote:

44: Text-based coding in Scratch
Some users wish to code Scratch not with the blocks, but with typing code instead (similar to how more advanced programming languages work). However, the Scratch Team has discussed this possibility multiple times and has decided every time that it would not be beneficial for beginners or for teachers.

One amazing thing about block-based programming is that syntax errors largely do not exist, but text-based programming would indeed introduce syntax errors which younger users might not understand.

This suggestion extends to coding Scratch in any text, including BBCode, Javascript, some form of pseudocode, or some other programming language. If you wish to code using Javascript, for instance, then you can learn Javascript on your own; but it would have to be done outside of Scratch.

EIephant_Lover wrote:

For this one, you should quote Paddle here: https://scratch.mit.edu/users/MaximunPokeMaster/#comments-55378478

Za-Chary wrote:

However, the Scratch Team has discussed this possibility multiple times and has decided every time that it would not be beneficial for beginners or for teachers.

Flipped_ wrote:

I saw a user saying that Paddle2See rejected a suggestion for a 16:9 aspect ratio. I'm not exactly sure how new Rejected Suggestions are added to the list, but maybe you could look into it and add 16:9 aspect ratio to the list? I can't find the topic anywhere.

Za-Chary wrote:

Gifted_Mess wrote:

Za-Chary wrote:

Gifted_Mess wrote:

Yeah, doesn't look like you missed anything but maybe change the formatting of the proof

Anything in particular you would suggest?

Maybe do like a quote then the proof, it is just more understandable in my mind for like the first one do this :
wait *looks*.,…..

Yeah you have the quote one just maybe find some for all of them

Thanks for the suggestion — if I find anything good, I'll add it in, but we'd also like to avoid having the forum post get too long.

Enderboygamer wrote:

why would you not allow repeat until broadcast?

<[message v] received? :: events>

repeat until [message v] received {} :: events

wait until [message v] received :: events

The restriction is not for all FNaF projects. If you have a Five Nights at Freddy's project without any inappropriate/gory/scary-for-an-AVERAGE-eight-year-old content, then it won't be taken down/NFE'd. It's only that many Five Nights at Freddy's projects have gory content that isn't what Scratch wants.

sti_scratch wrote:

For the FNaF thing, you can put this above everything else:

The restriction is not for all FNaF projects. If you have a Five Nights at Freddy's project without any inappropriate/gory/scary-for-an-AVERAGE-eight-year-old content, then it won't be taken down/NFE'd. It's only that many Five Nights at Freddy's projects have gory content that isn't what Scratch wants.

Za-Chary wrote:

However, you are free to use Five Nights at Freddy's characters in your project as long as the project follows the Community Guidelines (one example is a Five Nights at Freddy's dress-up game). Be sure to report any project that does not follow the Community Guidelines, especially if it contains jumpscares or scary images.

Paddle2See wrote:

Interesting idea! But we don't see it as being useful enough to the few advanced Scratchers that would find it handy to earn a place in the Scratch block vocabulary. One of the main goals of Scratch it to keep it easy to learn - and that means keeping the number of blocks as small possible. Also, it seems like there are work-arounds that aren't all that onerous. Thanks for the suggestion though.