yadayadayadagoodbye wrote:

I would assume clones could increase the amount of layers, so perhaps a “total layers” reporter would be helpful as well.

(total layers ::looks)

forever
go to front
end

yadayadayadagoodbye wrote:

I would assume clones could increase the amount of layers, so perhaps a “total layers” reporter would be helpful as well.

Do note that your example can also be acheived currently by using

forever
go to front
end

GlitchedThrough wrote:

Mrow meow mrow.
(I can see the potential. There are workarounds, but everything has a workaround. It could certainly help with dynamically generating content, that is an RPG tile like system would greatly benefit by this.)
Mrow meow.
(It also wouldn't take much time to implement, as there's already likely an internal count of it. So they could just read from this.)

-stxllxr wrote:

GlitchedThrough wrote:

Mrow meow mrow.
(I can see the potential. There are workarounds, but everything has a workaround. It could certainly help with dynamically generating content, that is an RPG tile like system would greatly benefit by this.)
Mrow meow.
(It also wouldn't take much time to implement, as there's already likely an internal count of it. So they could just read from this.)

Jester, there is no simple workaround.
(There isn't really a viable and accurate workaround, without using far too many blocks for something that, as you stated, should have an internal state regardless. Since sprites and clone's code are run in layer-order, i am left to believe that this must be true, and shouldn't bet too difficult to add. The workaround required for this would be quite complex, and i could make a project showing the code for it, but it would be required in every clone sprite and etc, to accurately store the layers.)

-stxllxr wrote:

Sire, there appears to be a duplicate! We must traverse there at once!
(You know the drill, someone suggested this before, please go there to discuss this addition to prevent clutter and keep the conversation in one place.)