Sprite Layer reporter

Sonickyle

There should be a new integer in the Looks sction that when the tickbox is ticked, it'll display what layer the sprite is on (with 0 being the topmost). The tickbox would behave like what happens when you tick the tickbox next to:

(costume #)

It could be called:

(layer #)

No I don't make projects anymore. I left some time ago.
I only check the forums every now and then, but other than that consider me retired.

I have made 2950+ posts / contributed to 2238+ topics

AonymousGuy

Workaround:

set [layer # v] to [0]
go to front
go back (x) layers
change [layer # v] by (x)

Travellingcritic

AonymousGuy wrote:

Workaround:

set [layer # v] to [0]
go to front
go back (x) layers
change [layer # v] by (x)

Yeah, but the block ould be more effective, you could create a 3d (2.5d) game where size could represent the layer number. I am aware that you could do the same thing with variables, but this would save a lot of bock space. Also to note is size, and the

[spriteI]'s [size] //catigory=sensing

Check out patapony here.
Or, check out pygame here.

Sonickyle

Travellingcritic wrote:
AonymousGuy wrote:
Workaround:
set [layer # v] to [0]
go to front
go back (x) layers
change [layer # v] by (x)
Yeah, but the block ould be more effective, you could create a 3d (2.5d) game where size could represent the layer number. I am aware that you could do the same thing with variables, but this would save a lot of bock space. Also to note is size, and the
[spriteI]'s [size] //catigory=sensing

This would have to be added too:

([layer v] of [Sprite1 v])

No I don't make projects anymore. I left some time ago.
I only check the forums every now and then, but other than that consider me retired.

I have made 2950+ posts / contributed to 2238+ topics

cobraguy

Hmm… Do you have any examples for when the block could be used?

YoghurtMaster

They should add this:

(Layer #)
go infront of [ sprite]
go behind of [ sprite]

stickfiregames

AonymousGuy wrote:

Workaround:

set [layer # v] to [0]
go to front
go back (x) layers
change [layer # v] by (x)

That wouldn't work.

Support.

If you can read this, my signature cubeupload has been eaten by an evil kumquat!

or you just used Inspect Element, you hacker

;

daves777

Support

https://scratch.mit.edu/studios/1358788/

DaSpudLord

stickfiregames wrote:
AonymousGuy wrote:
Workaround:
set [layer # v] to [0]
go to front
go back (x) layers
change [layer # v] by (x)
That wouldn't work.

Support.

How?

Semi-support as per the workaround.

| Primary Target | Fireworks Show! Wheel of Fortune || Block Buster ||||| Shut the Box ||||||||| Surf's Up! |||||

U^ｪ^U::motion//This is Blocky. He lives in my signature. He is a trained attack block. He protects my siggy from kumquats.

stickfiregames

DaSpudLord wrote:
stickfiregames wrote:
AonymousGuy wrote:
Workaround:
set [layer # v] to [0]
go to front
go back (x) layers
change [layer # v] by (x)
That wouldn't work.

Support.
How?

Semi-support as per the workaround.

Layers are effectively a list. When a sprite moves back, all the sprites it passesd move forward a layer, so their layer # variables would no longer be accurate

If you can read this, my signature cubeupload has been eaten by an evil kumquat!

or you just used Inspect Element, you hacker

;

Zekrom01

75% support due to workaround.
dang it 60second rule

ɴᴏᴡ ᴘʟᴀʏɪɴɢ: Despacito 2 (Feat: Lil Pump) ───────────⚪────── ◄◄⠀▐▐ ⠀►►⠀⠀ ⠀

theonlygusti

AonymousGuy wrote:

Workaround:

set [layer # v] to [0]
go to front
go back (x) layers
change [layer # v] by (x)

Not a valid work-around.

Say another Sprite were to now [go to front], this Sprite's (layer #) variable wouldn't be updated.

I support this.

(layer # :: looks)

Last edited by theonlygusti (Oct. 7, 2015 20:22:46)

theonlygusti

Zekrom01 wrote:
75% support due to workaround.
dang it 60second rule

There is no work-around.

stickfiregames wrote:
Layers are effectively a list. When a sprite moves back, all the sprites it passesd move forward a layer, so their layer # variables would no longer be accurate

Cream_E_Cookie

Support!

AlveKatt

Why isn't better layer support a thing?

Please give us more control over this.

Scratcher1002

Cream_E_Cookie wrote:
Support!

・Scratcher1002は「ここにランダムな日本語の言葉はたくさんですか？はい」と言いました・

||||Search:
Topics | Users
||Studios | Projects
||

Leadrien2366

Support.

JonathanSchaffer

Travellingcritic wrote:
AonymousGuy wrote:
Workaround:
set [layer # v] to [0]
go to front
go back (x) layers
change [layer # v] by (x)
Yeah, but the block ould be more effective, you could create a 3d (2.5d) game where size could represent the layer number. I am aware that you could do the same thing with variables, but this would save a lot of bock space. Also to note is size, and the
[spriteI]'s [size] //catigory=sensing

([sprite1 v]'s [size v]::sensing)

do you like siri, alexa, cortana, or google assistant, but can't buy an iphone, echo, or google home?

then try alice!
alice is a wonderful virtual assistant that works on linux and is tested on raspberry pi*
she can play music, search online, answer questions, tell jokes, give you the date and time, and plenty of other things

*you may need to install additional software like python 2, libttspico-utils, and timidity

mlcreater

Four suggestions that duplicate this one (I came here because one of them is from 4 hours ago):

if<there is (nothing(to say::looks)except[bump]::operators)::sensing>then{
(the(topic::grey)::sensing)[doesn't v]deserve(a(bump::grey)::variables)::grey
}::control

panda-wat

maybe while the

 (layer::looks)

block is being made the ST can also add to the other sprite report reporter block like this?

 ([layer v] of (sprite v)

also I support!

Last edited by panda-wat (July 11, 2020 22:53:08)

I'm just an animations and games maker who mostly hangs out in the questions, suggestions, bugs, and HwS forums.

Discuss Scratch