Discuss Scratch

coolkidguything
Scratcher
55 posts

new layer sensing blocks, <behind [sprite]?> and (layer)

support
minor-edit
Scratcher
500+ posts

new layer sensing blocks, <behind [sprite]?> and (layer)

coolkidguything wrote:

support
Say why.
Feather_Dynamics
Scratcher
2 posts

new layer sensing blocks, <behind [sprite]?> and (layer)

I support this idea. A block for controling layers would help a lot with animations and certain games. I have had trouble with sprites going and staying behind on another for a while and can never get the formula perfectly right with the layers
WindOctahedron
Scratcher
1000+ posts

new layer sensing blocks, <behind [sprite]?> and (layer)

chrdagos wrote:

WindOctahedron wrote:

chrdagos wrote:

... :: #222222
say [i'm on the same layer as sprite1]
... :: #222222
Actually, it's not possible to make two sprites be on the same level, because it wouldn't be possible for them to be at the same location.
It said layer, not level.
Doesn't matter. In this context, the meaning is the same.
DrGaming_92Games
Scratcher
100+ posts

new layer sensing blocks, <behind [sprite]?> and (layer)

Support, though I personally don't do a lot of animations, this block would be incredibly useful. This would also make it much easier to animate especially for those new to Scratch seeing as some of the workarounds may seem complicated for them.
RedGuy7
Scratcher
1000+ posts

new layer sensing blocks, <behind [sprite]?> and (layer)

Support! I was just about to create a topic for this when i saw this!!!
StevenTheSquare
Scratcher
100+ posts

new layer sensing blocks, <behind [sprite]?> and (layer)

hello1964 wrote:

You could create a variable that adds up or down how many layers you are from the front or back, which would allow you to keep track of what layer your sprite is on.

StevenTheSquare wrote:

Seth_Zaw, that workaround assumes that sprites don't eclipse one another, but you can't have two sprites in the same layer. Also, that wouldn't work for projects using clones. Additionally, for projects involving more than 6 or 7 moving sprites (and/or clones of sprites) it would get increasingly more complicated having to say what's behind or in front of what else. That said, thanks for trying to help. Also, if each of those variables is personal to the sprite, you can't drag them into other sprites to see if one is bigger than the other. Plus, the workaround in some cases is more complex than the entire rest of the project!
I already addressed why this workaround is flawed.
RedGuy7
Scratcher
1000+ posts

new layer sensing blocks, <behind [sprite]?> and (layer)

StevenTheSquare wrote:

hello1964 wrote:

You could create a variable that adds up or down how many layers you are from the front or back, which would allow you to keep track of what layer your sprite is on.

StevenTheSquare wrote:

Seth_Zaw, that workaround assumes that sprites don't eclipse one another, but you can't have two sprites in the same layer. Also, that wouldn't work for projects using clones. Additionally, for projects involving more than 6 or 7 moving sprites (and/or clones of sprites) it would get increasingly more complicated having to say what's behind or in front of what else. That said, thanks for trying to help. Also, if each of those variables is personal to the sprite, you can't drag them into other sprites to see if one is bigger than the other. Plus, the workaround in some cases is more complex than the entire rest of the project!
I already addressed why this workaround is flawed.
clones have their own layers but not their own variables
and it gets more and more complicated
RedGuy7
Scratcher
1000+ posts

new layer sensing blocks, <behind [sprite]?> and (layer)

StevenTheSquare wrote:

Seth_Zaw, that workaround assumes that sprites don't eclipse one another, but you can't have two sprites in the same layer. Also, that wouldn't work for projects using clones. Additionally, for projects involving more than 6 or 7 moving sprites (and/or clones of sprites) it would get increasingly more complicated having to say what's behind or in front of what else. That said, thanks for trying to help. Also, if each of those variables is personal to the sprite, you can't drag them into other sprites to see if one is bigger than the other. Plus, the workaround in some cases is more complex than the entire rest of the project!
you can call one-sprite variables from other sprites
([layer v] of [Sprite1 v])
where layer is the variable name and sprite1 is the sprite
-GentooPenguin-
Scratcher
100+ posts

new layer sensing blocks, <behind [sprite]?> and (layer)

Support. I don’t think there are any workarounds and these blocks seem very useful!
--Explosion--
Scratcher
1000+ posts

new layer sensing blocks, <behind [sprite]?> and (layer)

Great idea, support!
StevenTheSquare
Scratcher
100+ posts

new layer sensing blocks, <behind [sprite]?> and (layer)

--Explosion-- wrote:

Great idea, support!
*gasp* I JUST REALIZED EXPLOSION IS SUPER FAMOUS AAAAAAA
StevenTheSquare
Scratcher
100+ posts

new layer sensing blocks, <behind [sprite]?> and (layer)

I have now made this suggestion also in the form of a project! You can find the project at this link. I also added the link to the main post.
StevenTheSquare
Scratcher
100+ posts

new layer sensing blocks, <behind [sprite]?> and (layer)

Thanks to @nicopete119 for supporting via the project! We now have 28 supporters!
OurPrincess
Scratcher
1000+ posts

new layer sensing blocks, <behind [sprite]?> and (layer)

I supported the suggestion. You didn't add me to the list of supporters.

Last edited by OurPrincess (March 9, 2020 19:04:42)

StevenTheSquare
Scratcher
100+ posts

new layer sensing blocks, <behind [sprite]?> and (layer)

OurPrincess wrote:

I supported the suggestion. You didn't add me to the list of supporters.
I think you already supported this actually. Your name is already in the supporters list

OurPrincess wrote:

I support this because it would be very useful, and the problem we have right now with the ones we have are…

go back () layers
That's perfectly fine to me, I'm talking about the one below.

go to front
You can't go forward by a certain number of layers. I couldn't find a block like this.
This is your earlier support

Last edited by StevenTheSquare (March 9, 2020 19:07:03)

OurPrincess
Scratcher
1000+ posts

new layer sensing blocks, <behind [sprite]?> and (layer)

StevenTheSquare wrote:

OurPrincess wrote:

I supported the suggestion. You didn't add me to the list of supporters.
I think you already supported this actually. Your name is already in the supporters list

OurPrincess wrote:

I support this because it would be very useful, and the problem we have right now with the ones we have are…

go back () layers
That's perfectly fine to me, I'm talking about the one below.

go to front
You can't go forward by a certain number of layers. I couldn't find a block like this.
This is your earlier support
Huh. I didn't see my name there. I should look carefully.
X-cloudStudios
Scratcher
9 posts

new layer sensing blocks, <behind [sprite]?> and (layer)

I like the idea because if you wanna make a stealth game where you hide behind things you could make like:
if <behind sprite 1> then
Blah blah blah
end
StevenTheSquare
Scratcher
100+ posts

new layer sensing blocks, <behind [sprite]?> and (layer)

X-cloudStudios wrote:

I like the idea because if you wanna make a stealth game where you hide behind things you could make like:
if <behind sprite 1> then
Blah blah blah
end
it would have to be
if <<behind [sprite1 v]? :: sensing>and<touching [sprite1 v]?>> then
Blah blah blah
end

Last edited by StevenTheSquare (March 9, 2020 19:55:02)

RandyX187
Scratcher
3 posts

new layer sensing blocks, <behind [sprite]?> and (layer)

I support this! It can make games and animations so much easier!

P.S. How do you do the signature thing on the bottom of all your comments, NKL?

Powered by DjangoBB