Discuss Scratch

mellfang
Scratcher
26 posts

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

i subport it
LBormi
Scratcher
1000+ posts

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

Support. This would be very helpful for sprite organization.
StevenTheSquare
Scratcher
100+ posts

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

Thanks to @Awesome_Gabe for supporting from the project! We now have 32 supporters!
fdreerf
Scratcher
1000+ posts

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

Could you change the topic title? It sure is eye catching, but for all the wrong reasons.
It takes up three lines for me.
StevenTheSquare
Scratcher
100+ posts

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

fdreerf wrote:

Could you change the topic title? It sure is eye catching, but for all the wrong reasons.
It takes up three lines for me.
how do I change it?
LBormi
Scratcher
1000+ posts

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

StevenTheSquare wrote:

fdreerf wrote:

Could you change the topic title? It sure is eye catching, but for all the wrong reasons.
It takes up three lines for me.
how do I change it?
You click edit on the very first post of the topic.
StevenTheSquare
Scratcher
100+ posts

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

LBormi wrote:

StevenTheSquare wrote:

fdreerf wrote:

Could you change the topic title? It sure is eye catching, but for all the wrong reasons.
It takes up three lines for me.
how do I change it?
You click edit on the very first post of the topic.
Thanks. is this better?
minor-edit
Scratcher
500+ posts

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

SUGGESTION and PLEASE IMPLEMENT are redundant b/c this is in the forum for suggestions and Scratch team knows that each topic is made with the desire that it be implemented. Also, caps are a bit like yelling.
StevenTheSquare
Scratcher
100+ posts

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

minor-edit wrote:

SUGGESTION and PLEASE IMPLEMENT are redundant b/c this is in the forum for suggestions and Scratch team knows that each topic is made with the desire that it be implemented. Also, caps are a bit like yelling.
it already had those before and nobody else complained??
LBormi
Scratcher
1000+ posts

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

StevenTheSquare wrote:

minor-edit wrote:

SUGGESTION and PLEASE IMPLEMENT are redundant b/c this is in the forum for suggestions and Scratch team knows that each topic is made with the desire that it be implemented. Also, caps are a bit like yelling.
it already had those before and nobody else complained??
It doesn't really matter how you present your suggestion, so long as it's an actual suggestion and not something dumb.
StevenTheSquare
Scratcher
100+ posts

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

LBormi wrote:

StevenTheSquare wrote:

minor-edit wrote:

SUGGESTION and PLEASE IMPLEMENT are redundant b/c this is in the forum for suggestions and Scratch team knows that each topic is made with the desire that it be implemented. Also, caps are a bit like yelling.
it already had those before and nobody else complained??
It doesn't really matter how you present your suggestion, so long as it's an actual suggestion and not something dumb.
oh okay thank you
fdreerf
Scratcher
1000+ posts

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

StevenTheSquare wrote:

minor-edit wrote:

SUGGESTION and PLEASE IMPLEMENT are redundant b/c this is in the forum for suggestions and Scratch team knows that each topic is made with the desire that it be implemented. Also, caps are a bit like yelling.
it already had those before and nobody else complained??
I did though lol
playbaldiyeet
Scratcher
17 posts

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

StevenTheSquare wrote:

Anybody who's ever tried to make a game or animation with multiple moving sprites can tell you that layers are a pain.
Yes, you have blocks like:
go to front
go back (1) layers
But there's no way to tell in code which sprites are in what layers, or say, I want this sprite to be in front of that sprite but not this sprite. To solve this problem, I propose that we make a block similar to
<touching [ v] ?>
that would look like
<behind [sprite1 v]?  :: sensing>
It would be really useful, for like, if I wanted sprite2 to be behind sprite3 but in front of sprite1. You could do a script like
when I receive [sprite2 in middle]
if <behind [sprite1 v]? :: sensing> then
go forward (1) layers :: looks
end
if <not<behind [sprite3 v]? :: sensing>> then
go back (1) layers
end

You could also make one of those variable blocks that are like,
<<(costume #)or(size)>or<(backdrop name)or(backdrop #)>>
but it's
(layer  :: looks)


This simple sensing block would make layers INFINITELY less painful to order. And, if you put it in the backdrop, it would always be true, no matter what.


If you support this, please reply “support” and why you support it. Maybe also add some other suggestions?

Here is the project version of this post.


SUPPORTERS LIST: (33)
@StevenTheSquare @WindOctahedron @Slushy70 @kanishka_maiti @venyanwarrior @OurPrincess @_nix @ScratchEmm999 @PullThatSpoonAway @scratchinghead @boroy07 @Grayforz24682 @CattyCodes @chrdagos @midnight-echos @TelekineticPotato @Feather_Dynamics @Dolphinrider8910 @EmmettRios19 @norbert00 @Catscratcher07 @DrGaming_92Games @RedGuy7 @-GentooPenguin- @–Explosion– @nicopete119 @X-cloudStudios @RandyX187 @Lil_Asgore_Maker @mellfang @LBormi @Awesome_Gabe @The_Minecode
I think no, Because you can make a layer variable block. or create your own.
StevenTheSquare
Scratcher
100+ posts

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

playbaldiyeet wrote:

I think no, Because you can make a layer variable block. or create your own.
Other people have already proposed this workaround, and I have a rebuttal

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!
StevenTheSquare
Scratcher
100+ posts

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

Thanks to @UnstripedZebra for supporting via the project! We now have 34 supporters!
StevenTheSquare
Scratcher
100+ posts

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

Thanks to @Untitled_2 for supporting via the project! We now have 35 supporters!
guster-animations
Scratcher
4 posts

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

I support
Starstriker3000
Scratcher
1000+ posts

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

guster-animations wrote:

I support
Please be constructive and say why you support.
chrdagos
Scratcher
500+ posts

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

bump
StevenTheSquare
Scratcher
100+ posts

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

chrdagos wrote:

bump
what?

Powered by DjangoBB