It would be useful if their were better layering blocks.

go () spaces [behind v][sprite1 v]

go () spaces [in front of v][sprite5 v]

This would help with games, animations, etc. if they had many layers.

This could help deal with how hard it is ti set up layering.
I support this idea.

ilikelegos wrote:

It would be useful if their were better layering blocks…

I think we just had a suggestion quite similar to this (and I went on to suggest almost as you said above).

As I mentioned there, though, it's worth noting that you can't access the layer for a clone of a sprite using such a block…
(The only way I can think to allow layering relative to a given clone would be to follow on from one of the suggestions of the original poster in the above topic: a “layer” reporter so you can recover exactly which layer a sprite/clone currently occupies, then put into a global var/list so something else can read it - the main problem I see there is that you still may need to beware how it might change its layer value whenever something else has its layer changed.)

You should also note that the layers in Scratch include more than just sprites (and clones) - all variables & reporters, hidden or not, also take up a layer each. That's why layering can be so tricky - and also why I suspect having "go (N) layers behind/above [SomeSprite]“ can potentially be as confusing as the existing ”go back (N) layers"…

I see what you mean. I guess that would be pretty confusing.