Sometimes, many users suggest many blocks and sometimes Scratch Team adds them. What could be the real problem is that every block category would be flooded with many blocks, making it difficult to find the correct type in that section you want. This includes when makings lots of variables and lists, which can sometimes flood the data section. Even the more blocks section could be flooded if you decide to add so many blocks.

However, I might have a solution. Split all the blocks in each category into individual sections. For example, put the “point towards sprite”, “turn left/right whatever degrees”, and “point in direction” block into a “Direction” section. Put the “glide secs to x and y”, “go to x y”, “set x to”, “set y to”, “change x by”, and “change y by” in a section called “Positions”.

Of course, this may confuse you, and you might think sometimes it won't be necessary, because some sections have little blocks, but just think about every update. There are more blocks added, more things improved to the website, and much more. Since we will have custom reporters in Scratch 3.0, it's best we have a “Stack Blocks” and “Reporter Blocks” section in the More Blocks category, and you might need to make a lot of stack blocks and custom reporters.

If you still don't understand how this will be like, I will show you and image later on, since Inspect Element doesn't work in the Scratch editor since it has their own right click menu now on. Maybe you'll have an idea.

(This might also be a solution to those customizable list blocks I suggested, since they could easily flood the data section too.)

Bump and support.
Motion
Position
Direction
Looks
Appearance(switch costume to, next costume, etc.)
Size, Effect & Layering
Text(say _, think _, etc.)
Sound
Sprite Sounds(play sound _, stop all sounds, etc.)
Instruments
Effects(3.0 effects, volume and tempo)
Pen
General(clear, stamp, pen down, etc.)
Pen Effects(pen color, pen shade, pen size, etc.)
Data
Variables
Lists
Events
General Events(when flag clicked, when this sprite clicked, etc.)
Broadcasting
Control
Script Control(wait _secs, repeat _, stop _, etc.)
Boolean Input(if _ then, wait until _, etc.)
Clones
Sensing
Interaction(touching _, distance to _, etc.)
Mouse
Video, Timer and Other(username, ask, current _, etc.)
Operators
Math(_+_, _ of _, pick random _ to _, _ mod _, etc.)
Booleans(_=_, _ and _, etc.)
Strings(length of _, etc.)
More Blocks
Custom Blocks
Extensions

Sounds cool! I think this could be helpful despite the fact that x and y positions are movement.

I found this while searching for a topic suggestion to add another section for lists (they're differently colored from variables so makes sense). I semi-support for lists (separating and adding on the category menu), but nothing else on here. The ST would not add so many blocks that the menu gets flooded in the first place. [not necroing]

edit: … buuut I am supporting a lot of blocks, so I'm changing to support for lists and neutral for the rest, at least until some of those blocks start to get implemented..

gosoccerboy5 wrote:

charles12310 wrote:

Since we will have custom reporters in Scratch 3.0

*cries in not having custom reporters, predicates, and c-blocks in scratch 3.0*

If you look closely you will see that blocks are already divided into “paragraphs”

I think that the current categories are good enough. I'm sure we can all agree that having too many categories would be just as inconvenient as having too few, and this suggestion falls under the former category in my opinion. It's not like any of the sections are particularly overflowing with blocks as it is or anything.

gosoccerboy5 wrote:

charles12310 wrote:

Since we will have custom reporters in Scratch 3.0

MDCCCLXVII wrote:

the2000 wrote:

gosoccerboy5 wrote:

charles12310 wrote:

Since we will have custom reporters in Scratch 3.0

Stop sapmming 's

FancyFoxy wrote:

Bump and support.
-snip-

I agree, these would be great!

Bringing this topic up.
Also, maybe sprite only vars/lists too?