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 #)

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.
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

Check out patapony here.
Or, check out pygame here.
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])

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.
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.










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




or you just used Inspect Element, you hacker

;
daves777
Scratcher
37 posts

Sprite Layer reporter

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.


U^ェ^U::motion//This is Blocky. He lives in my signature. He is a trained attack block. He protects my siggy from kumquats.
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










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




or you just used Inspect Element, you hacker

;
Zekrom01
Scratcher
1000+ posts

Sprite Layer reporter

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

20 something years old
Probably doing college work
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.
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)

club penguin is kil
mlcreater
Scratcher
1000+ posts

Sprite Layer reporter

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

← there are 3 sig figs and 0 kumquats





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)


My browser/operating system: Microsoft BOB 1.0, gateway 2000 edition

Powered by DjangoBB