stickfiregames wrote:

paws48 wrote:

I just wanted to know, is blocking other Scratchers a rejected suggestion? I don't mean blocking and then they aren't allowed to be on Scratch. I mean blocking in the way that they can't talk to you but can talk to other people. Pretty much the exact same thing as the blocking in Animal Jam.

Yes:

Ignore List (Blocking Users)
It just buries the problem. If you have a problem, report the user.

This topic has the full list of what's rejected.

paws48 wrote:

stickfiregames wrote:

paws48 wrote:

I just wanted to know, is blocking other Scratchers a rejected suggestion? I don't mean blocking and then they aren't allowed to be on Scratch. I mean blocking in the way that they can't talk to you but can talk to other people. Pretty much the exact same thing as the blocking in Animal Jam.

Yes:

Ignore List (Blocking Users)
It just buries the problem. If you have a problem, report the user.

This topic has the full list of what's rejected.

But what if the user is being annoying to you but you still want others to be able to comment and share their opinions on projects?

stickfiregames wrote:

paws48 wrote:

stickfiregames wrote:

paws48 wrote:

I just wanted to know, is blocking other Scratchers a rejected suggestion? I don't mean blocking and then they aren't allowed to be on Scratch. I mean blocking in the way that they can't talk to you but can talk to other people. Pretty much the exact same thing as the blocking in Animal Jam.

Yes:

Ignore List (Blocking Users)
It just buries the problem. If you have a problem, report the user.

This topic has the full list of what's rejected.

But what if the user is being annoying to you but you still want others to be able to comment and share their opinions on projects?

If they're breaking the rules, report them. If they're not, just ignore them by yourself.

Harakou wrote:

Unfortunately this doesn't make it all that much easier on us, becuase it still requires piecing together context from potentially huge comment chains. It makes the job of actually implementing it all the harder, too.

Comments simply aren't designed as longer thoughts that might need to be edited over time, like forum posts, so the actual need for editing seems to be limited to fixing mistakes and abusing the system. You're limited in space as it is, so adding thoughts via another comment is common as it is - and this reflects what comments are intended to be. If you really are concerned about typos, try reviewing your comment before posting.

DownsGameClub wrote:

Should we add “Editing Comments”? This was rejected by Harakou-
https://scratch.mit.edu/discuss/post/1939992/

Harakou wrote:

Unfortunately this doesn't make it all that much easier on us, becuase it still requires piecing together context from potentially huge comment chains. It makes the job of actually implementing it all the harder, too.

Comments simply aren't designed as longer thoughts that might need to be edited over time, like forum posts, so the actual need for editing seems to be limited to fixing mistakes and abusing the system. You're limited in space as it is, so adding thoughts via another comment is common as it is - and this reflects what comments are intended to be. If you really are concerned about typos, try reviewing your comment before posting.

jvvg wrote:

3. Disabling “See inside”, restricting sharing, etc.
Several people want to be able to lock their projects so that they are read-only, and other people can't see the code to copy their scripts, sounds, or artwork. However, the motto of Scratch is "Imagine - Program - Share". By putting a project on the site, you give anyone who sees it the right to see your code, all data in it, and potentially copy it. Part of the whole goal of Scratch is remixing. If you do not wish to allow this, then you are welcome to publish the project on your own site (once the downloadable Scratch 2.0 comes out).

gamer2343676 wrote:

jvvg wrote:

3. Disabling “See inside”, restricting sharing, etc.
Several people want to be able to lock their projects so that they are read-only, and other people can't see the code to copy their scripts, sounds, or artwork. However, the motto of Scratch is "Imagine - Program - Share". By putting a project on the site, you give anyone who sees it the right to see your code, all data in it, and potentially copy it. Part of the whole goal of Scratch is remixing. If you do not wish to allow this, then you are welcome to publish the project on your own site (once the downloadable Scratch 2.0 comes out).

The downloadable Scratch 2.0 come out a long time ago!

gamer2343676 wrote:

jvvg wrote:

3. Disabling “See inside”, restricting sharing, etc.
Several people want to be able to lock their projects so that they are read-only, and other people can't see the code to copy their scripts, sounds, or artwork. However, the motto of Scratch is "Imagine - Program - Share". By putting a project on the site, you give anyone who sees it the right to see your code, all data in it, and potentially copy it. Part of the whole goal of Scratch is remixing. If you do not wish to allow this, then you are welcome to publish the project on your own site (once the downloadable Scratch 2.0 comes out).

The downloadable Scratch 2.0 come out a long time ago!

LionHeart70 wrote:

If I had a dollar for every time someone didn't read this topic and suggested a rejected suggestion..

PaultheCat wrote:

#bring it back

Ignore List:
Despite this feature being a go way to be prevented from bullying, we have removed the ignore list, since it has caused lots of problems with no solution.

If someone is bullying you, report the user, and state what the user is doing bad.

Stop Sign Clicked:
Clicking the Stop Sign was meant to stop all scripts, not to trigger a script. If you want this function, make sure you aren't using the timer for other purposes in the project you want to implement this to. First make a forever block with the reset timer block in it. Then put a “when timer > (0.1)” block and put the scripts underneath the blocks, which you will call the scripts that trigger when the Stop Sign is clicked, since all scripts stop but the timer keeps going, allowing you to trigger a script.

Charles12310 wrote:

Add this:

Ignore List:
Despite this feature being a go way to be prevented from bullying, we have removed the ignore list, since it has caused lots of problems with no solution.

If someone is bullying you, report the user, and state what the user is doing bad.

And this:

Stop Sign Clicked:
Clicking the Stop Sign was meant to stop all scripts, not to trigger a script. If you want this function, make sure you aren't using the timer for other purposes in the project you want to implement this to. First make a forever block with the reset timer block in it. Then put a “when timer > (0.1)” block and put the scripts underneath the blocks, which you will call the scripts that trigger when the Stop Sign is clicked, since all scripts stop but the timer keeps going, allowing you to trigger a script.

duckboycool wrote:

Charles12310 wrote:

Add this:

Ignore List:
Despite this feature being a go way to be prevented from bullying, we have removed the ignore list, since it has caused lots of problems with no solution.

If someone is bullying you, report the user, and state what the user is doing bad.

And this:

Stop Sign Clicked:
Clicking the Stop Sign was meant to stop all scripts, not to trigger a script. If you want this function, make sure you aren't using the timer for other purposes in the project you want to implement this to. First make a forever block with the reset timer block in it. Then put a “when timer > (0.1)” block and put the scripts underneath the blocks, which you will call the scripts that trigger when the Stop Sign is clicked, since all scripts stop but the timer keeps going, allowing you to trigger a script.

These used to be on here, but they were moved over to the complete list when that topic was made, as they weren't requested very often.

-_UnderfellSans_- wrote:

Why is it rejected when the Scratch Team NEVER TAKES SUGGESTIONS?

jvvg wrote:

Removing restrictions on FNAF-based projects
These restrictions were put because many of these projects were considered too scary for younger users. Scratch was blocked on many networks because of this, such as school districts. Some parents have also reported that their children had nightmares, and some users were wary of browsing Scratch. Removing these restrictions could damage Scratch's reputation. The game itself wasn't banned from Scratch entirely, so you may still make things about the game as long as they don't break the guidelines. (Based on LionHeart70's post, with some rewording/shortening.)

Carriage wrote:

jvvg wrote:

Removing restrictions on FNAF-based projects
These restrictions were put because many of these projects were considered too scary for younger users. Scratch was blocked on many networks because of this, such as school districts. Some parents have also reported that their children had nightmares, and some users were wary of browsing Scratch. Removing these restrictions could damage Scratch's reputation. The game itself wasn't banned from Scratch entirely, so you may still make things about the game as long as they don't break the guidelines. (Based on LionHeart70's post, with some rewording/shortening.)

FNAF should be banned completely!

add (username) to [ban v]