| Spaces are allowed | wrote:

[quote=Your text with spaces here]

powercon5 wrote:

Ziggy741 wrote:

powercon5 wrote:

Ziggy741 wrote:

For Sigton:
1. I never said that you should not give a reason.
2. You're not supposed to support/semi-support/no support without a reason.
3. The Scratch Team could think that an idea is good, and then they add it, and then it leads to bad stuff happening.
4. There is no use for the first block example I gave because it would do nothing, and the other one would be useful because it would report the pen color value.

For MegaByteCorporations:
1. I never said that you should not give a reason.
2. What do you mean?
3. But the Scratch Team could accidentally add a bad idea. Just say it nicely.

For jokebookservice1:
1. What's wrong with telling the consequences?
4. How would that ignore code block be helpful?
(I skipped 2 and 3 because I didn't have anything to say.)

I think the scratch team tests all these things first to make sure they work and how would it be different if they added something from their own ideas there could be a bug then?

What do you mean?

Well when the scratch team gets a suggestion I think they would think about problems it would cause and if they did it they would make sure it is tested first and even if it had bugs they would fix them.

And the scratch team would add their own ideas and they would not have people tell the problems they would test it for themselves.

Ziggy741 wrote:

powercon5 wrote:

Ziggy741 wrote:

powercon5 wrote:

Ziggy741 wrote:

For Sigton:
1. I never said that you should not give a reason.
2. You're not supposed to support/semi-support/no support without a reason.
3. The Scratch Team could think that an idea is good, and then they add it, and then it leads to bad stuff happening.
4. There is no use for the first block example I gave because it would do nothing, and the other one would be useful because it would report the pen color value.

For MegaByteCorporations:
1. I never said that you should not give a reason.
2. What do you mean?
3. But the Scratch Team could accidentally add a bad idea. Just say it nicely.

For jokebookservice1:
1. What's wrong with telling the consequences?
4. How would that ignore code block be helpful?
(I skipped 2 and 3 because I didn't have anything to say.)

I think the scratch team tests all these things first to make sure they work and how would it be different if they added something from their own ideas there could be a bug then?

What do you mean?

Well when the scratch team gets a suggestion I think they would think about problems it would cause and if they did it they would make sure it is tested first and even if it had bugs they would fix them.

And the scratch team would add their own ideas and they would not have people tell the problems they would test it for themselves.

?

jokebookservice1 wrote:

| Spaces are allowed | wrote:

[quote=Your text with spaces here]

While it might not be correct BBCode(?) it still works, so you can do “Xth Suggestion” instead of “XthSuggestion”

Harakou wrote:

I really like this thread! The suggestions forum definitely has a lot of problems, and it's something we'd like to address. That said, this is pretty similar to the existing guide to constructive replies - I'm a little hesitant to sticky another thread of the same nature, especially if the existing one isn't having the intended effect.

Ziggy741 wrote:

4. Semi-support. I kind of agree. What if someone suggested a

this block does nothing :: control

block? It makes no sense.

goldfish678 wrote:

Ziggy741 wrote:

4. Semi-support. I kind of agree. What if someone suggested a

this block does nothing :: control

block? It makes no sense.

I agree - that's a different scenario

jokebookservice1 wrote:

| Spaces are allowed | wrote:

[quote=Your text with spaces here]

While it might not be correct BBCode(?) it still works, so you can do “Xth Suggestion” instead of “XthSuggestion”

Sigton wrote:

dude341 wrote:

1st suggestion: No support, what if people want say that they like/don't like the suggestion? I also like it when people say Support or No support because then I know if my suggestion is good or bad.

Then they say “I like this suggestion”! This whole support convention ahs done nothing to help the suggestions forum, in fact it has done exactly the opposite. It ahs turned this forum into a competition rather than an improvement scheme.

Sigton

Lythium wrote:

Support.

I'd rather put these all in one post rather than having 2000 other topics.

NanoRook wrote:

Could I have a version of that image in a post so that I can put it in my signature?

A thing I think is worth adding to the main post is dissing a small blocklist simply because it's a blocklist. Remember ProdigyZeta's blocklist? Remember what the thing in the very beginning of the post was?

I'd rather put these all in one post rather than having 2000 other topics.

His blocks were neatly organized into categories, I may add. But suddenly, years later, it's closed, just because it's a blocklist. There were some great block ideas in it, too.

I also once saw a blocklist that was no more than 5 blocks, yet no blocks were addressed and all that was posted was “big blocklist, blam plz.”

My suggestion is to allow small blocklists, instead of clogging this dirty drain of a forum with 5 topics, and receiving a lot of messages from each one.

[center][url=https://scratch.mit.edu/discuss/topic/215499/][img]http://i.cubeupload.com/dH71nV.png[/img][/url][/center]

Sigton wrote:

Bump

Sigton

MegaByteCorporations wrote:

Sigton wrote:

Bump

Sigton

Hi.

Sigton wrote:

Hello. Thank you also for supporting this thread by changing your signature

Sigton

MegaByteCorporations wrote:

Sigton wrote:

Hello. Thank you also for supporting this thread by changing your signature

Sigton

I was bored. XD

So….anything I should reply to?

Sigton wrote:

MegaByteCorporations wrote:

Sigton wrote:

Hello. Thank you also for supporting this thread by changing your signature

Sigton

I was bored. XD

So….anything I should reply to?

We can spread the influence of this thread hopefully

Sigton