the way that “layers” are currently function is simple: each sprite and clone is having a different layer number. this number is controls if the sprite is seen “above” or “below” another sprite. you can be moving sprites up and down by layers, and they do displace other sprite when this is done. however, in a project with a many sprite, or many clone, it is not always not entirely not easy to know where is a layer-sprite. to fix this … ..

I think that it will be a good idea to be have a layer hierarchy, like the one for “costumes”. this will make it easy er to see and re arrange sprites on the layers.

if a layer hierarchy is not, then this block may be. however, both is best, in opinion.

(layer number :: looks)
([layer number v] of [Sprite1 v])

finally, another feature that can be add with this, is the ability to make an empty “dummy” layer, with no sprite in it. this way a layer can be “reserved” for later. however, this is confusing and a way of doing that is not confusing has not been thought. so, maybe no.

if, then this can:

go to layer () if that layer is empty :: looks

(this is also a cool: thank Quantum-Cat for a concept)

<layer () is empty? :: looks>

Yes, this makes more sense, because you might not want a sprite to be on a layer with another sprite. (Unless you are planning to make it part of the background layer.)

Just saying, you can edit the original post to change the title.
This sounds great! It makes way more sense than the blocks, considering the blocks just create new layers willy nilly.

k0d3rrr wrote:

Yes, this makes more sense, because you might not want a sprite to be on a layer with another sprite. (Unless you are planning to make it part of the background layer.)

I'm confuse. In current scratch, two sprite cannot be on a same layer. with my suggestion, still no sprite can be on a same layer with another sprite.

lolecksdeehaha wrote:

Just saying, you can edit the original post to change the title.

uh oh oops and dang.. I wasn't knowing of that. thank's!

Official_GameTeam wrote:

k0d3rrr wrote:

Yes, this makes more sense, because you might not want a sprite to be on a layer with another sprite. (Unless you are planning to make it part of the background layer.)

I'm confuse. In current scratch, two sprite cannot be on a same layer. with my suggestion, still no sprite can be on a same layer with another sprite.

Oh, okay. I just was confused.
But yes, this is a good idea.

bump

bump,

bump.

bump;

bump-

This would be very useful, It was really confusing when I had to solve for the exact layer my sprites and clones are supposed to be on (like, the go back 1 layer block could just bring it to the wrong layer)

anyone remember this thingy






anyways, bump

bump

bump

support since it can be really useful for stuff like layering in rpgs

Support!
So many projects would be so much easier to make if this was added.

bumpity bump

bump

bump