Hey, when ever you want to make a topic, think about the topic. What makes it good? Well, think: Is there anything that makes something good? Something that Scratch doesn't have? After you have thought about it, make sure that there are no duplicates, and you have checked everything from The Official List of Rejected Suggestions. Also make sure you don't make a list. (People keep on using lists, topics keep on getting turned down!) So imagine that you are not the creator of a topic. Imagine seeing the topic ansd it's description. Also, no making nonsense stuff. I have seen someone do…(not this forum) something silly in the questions forum.

How descriptive does it need to be?

Well, you need some eye-catching. Make the topic look intresting. Make it so people understand it.

Example

Topic: (anything)
Message: Hi! I think this blocks should be nice (and write what it does).

How do I make people understand it?

Here is two examples.

Example 1

<variable [variable v] changed to [] ?::sensing>

Hello there! What this block would do is it detectes if a certain variable has changed to something…

Look at this. Can everybody understand this? If so, the topic's creator has done well. There, he or she describes what something would do. (This is just only an example.)

Example 2

Hello i think this blck wolld be niice.
If wee hadd aah blouk thaz containues.

What do you think about this? Well, this has several problems.

• This has terrible spelling. (What does this mean?)

• This block does not make sense. He or she has made it in poor quality. (Why do we need a block that continues? Can't we just leave it blank?)

• PROBLEM! NO BLOCKS SHOW WHAT IT LOOKS LIKE!

Someone could have also written this:

Example

Excuse me! Listen to me and stop playing with germs! There is something must be important, noobs!…

This has mean words, and breaks the rule “be friendly” of the community guidelines. So please do not write something with foul words or else someone may click report.
Terrible and filthy words: stop playing with germs and noobs
Now you have an idea of what is good in a topic and what is not.
I hope this helps when creating a topic

There are many examples. But let's start on this suggestion.

unexplained_user_and_this_user_is_unknown wrote:

Subject: Some blocks
Message: These blocks would help scratch.

ask [hi] and wait until <(answer) = [hi]>
skip to [the end v]

What is wrong with this:

• A wait until <> is not necessary. A workaround is:
  

  ask [hi] and wait
  if <(answer) = [hi]> then
  else
  say [answer hi]
  wait (1) secs
  ask [hi] and wait
  end

• skip to the end makes no sense

• Create a topic each for each of your suggestions, the scratch team wrote.

BONUS! You can “bump” a topic to make it go back to the top of the list. Just say “bump” in your suggestion!

(edited)Now, don't try to make topics that don't relate to the forums. Also, please make sure your topic is in the right forum.(/edited)

Helpful! Thanks for posting this ✔

_ReykjaviK_ wrote:

Helpful! Thanks for posting this ✔

Thanks

You may say “agree” or “disagree” to this guide.

hi! Bump

Nice guide! This is really, really good.

I don't like how unrealistic this is.

ioton wrote:

I don't like how unrealistic this is.

I don't like how unspecific this is.

I know this topic means well, and I don't see much mistakes with the writing as well, but I think you could just improve the BBCode… Maybe not highlight all of the keywords? And maybe just clean up the quote text a bit? I also don't see a lot of color - most of the stickies I read have eye-catching and interesting colors.

I also think many of the instructions given here can be found in this sticky, so maybe add some unusual and not so well-known information?

I didn't try to offend you with any of this criticism - just giving some honest feedback to let you improve

Thanks for your feedback. But I don't know how to change the font.

Cool! This will help lots of people!

By the way, I found two intentional spelling/grammatical errors:

BosenChang wrote:

How do I make people understand it?

Here is two examples.

Example 1

<variable [variable v] changed to [] ?::sensing>

Hello there! What this block would do is it detectes if a certain variable has changed to something…

You're kind of going against:

What do you think about this? Well, this has several problems.

• This has terrible spelling. (What does this mean?)

So, you should probably fix that up.

(Not meant to say in a critical way, but I'm letting you know before someone else DOES say it in a critical way.)

2nd Bump in this topic

Nice guide!
I think you can make the poor grammar one less obvious because people would have to be really trying to upset people to do this:

123user wrote:

hi i wannt diss bloke 2 be adid intwe scwach it shtoups evarithin inn a sprhitts skrhipptss plezz ad it nou scwach teeme pleazze itz u gudd ihdeea awso sepourt r els bad luk 4 a yeer

-accidental quote-

3rd bump because this topic is in second page

So, are you basically doing this to get stickied/iTopic'd?
First of all, you shouldn't do that, because that's just… not good.
There's this.

bump x4

Bump, also I edited post with some information stickies don't have.

ioton wrote:

So, are you basically doing this to get stickied/iTopic'd?
First of all, you shouldn't do that, because that's just… not good.
There's this.

Yes. Once, I got rejected from being invited to The Forum Helpers studio partially because I made plenty of guides which a user thought was just an attempt to get stickies or iTopics. That's where a Scratch Team member said that a guide does not need to be made unless it has a clear need in the first place.

Actually, I made most of mine to help the community and stop rumors / inform them about lists. Regardless, I tried to ask a Scratch Team member to sticky my topics, where he said he likes it, but it could fit in a pre-existing sticky, and suggested that I collaborate with the owner of another sticky instead. I feel as though that same principle could be applied here.