Discuss Scratch

Sonickyle
Scratcher
1000+ posts

Sprite Layer reporter

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 #)
AonymousGuy
Scratcher
1000+ posts

Sprite Layer reporter

Workaround:
set [layer # v] to [0]
go to front
go back (x) layers
change [layer # v] by (x)
Travellingcritic
Scratcher
84 posts

Sprite Layer reporter

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
Sonickyle
Scratcher
1000+ posts

Sprite Layer reporter

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])
cobraguy
Scratcher
1000+ posts

Sprite Layer reporter

Hmm… Do you have any examples for when the block could be used?
YoghurtMaster
Scratcher
2 posts

Sprite Layer reporter

They should add this:
(Layer #)
go infront of [ sprite]
go behind of [ sprite]
stickfiregames
Scratcher
1000+ posts

Sprite Layer reporter

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.
daves777
Scratcher
37 posts

Sprite Layer reporter

Support
DaSpudLord
Scratcher
1000+ posts

Sprite Layer reporter

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.
stickfiregames
Scratcher
1000+ posts

Sprite Layer reporter

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
Zekrom01
Scratcher
1000+ posts

Sprite Layer reporter

75% support due to workaround.
dang it 60second rule
theonlygusti
Scratcher
1000+ posts

Sprite Layer reporter

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
Scratcher
1000+ posts

Sprite Layer reporter

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
Scratcher
1000+ posts

Sprite Layer reporter

Support!
AlveKatt
Scratcher
94 posts

Sprite Layer reporter

Why isn't better layer support a thing?

Please give us more control over this.
Scratcher1002
Scratcher
1000+ posts

Sprite Layer reporter

Cream_E_Cookie wrote:

Support!
Leadrien2366
Scratcher
100+ posts

Sprite Layer reporter

Support.
JonathanSchaffer
Scratcher
1000+ posts

Sprite Layer reporter

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)
mlcreater
Scratcher
1000+ posts

Sprite Layer reporter

panda-wat
Scratcher
100+ posts

Sprite Layer reporter

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)

Powered by DjangoBB