Scratch

archmage · 2007-08-14 18:08:13

I think this would be very useful for people who want their sprite to react differently when touched at different points. Many people have tried making a sprite that follows another sprite to determine where a sprite has been touched but the results are often inaccurate as the sprites can't follow another sprite well enough.

Example of how these blocks could be used:

///On player sprite
when flag pressed
wait until touching "platform" at x("x position") y(y position+20)
say "ow I hit my head"

If you added sprite length and sprite width blocks as well you could make the code work regardless of a sprites hight.

///On player sprite
when flag pressed
wait until touching "platform" at x("x position") y(y position+("sprite's lenght"/2))
say "ow I hit my head"

Last edited by archmage (2007-08-14 18:08:54)

AlveKatt · 2007-08-14 18:17:01

Can't you just use more than one sprite and tie them together?

archmage · 2007-08-14 18:39:12

AlveKatt wrote:
Can't you just use more than one sprite and tie them together?

Many people have tried doing this but even if you set one sprite to forever go to the x and y coordinates of another sprite it won't follow it perfectly. Also these blocks would remove them need for such tedious tasks.

Mayhem · 2007-08-15 04:20:20

instead of making one sprite follow the other, create variables X and Y and use those variables to move both sprites. That way they stick together better.

kevin_karplus · 2007-08-15 12:25:19

Moving sprites independently, even to the same locations, can cause them to get out of sync. The problem is worse on slower machines, as the overhead of interpreting the code is larger and the time between the moves is larger.

Is "touching at x y" a good solution though? If so, should the x,y be in absolute coordinates as suggested, or in sprite relative coordinates? The example given showed doing a translation to get sprite-relative coordinates, but that did not take into account rotation of the sprite.

The other way people seem to handle the problem is to color the sensor area specially, and use color over color. Perhaps what people want is to be able to add sensor areas to a sprite (perhaps invisibly) and detect "sensor area 3 touching sprite" or "sensor area 3 touching color".

AlveKatt · 2007-08-15 12:39:36

Does that mean that my plan of making a sprite capital ship with other sprites as turrets will make it look all wonky no matter what?

MathWizz · 2012-05-09 22:26:00

*bump* Great idea!

Andres-Vander · 2012-05-09 22:35:17

Can't you do this with variables now? This topic is seriously old

TorbyFork234 · 2012-05-10 00:43:15

MathWizz wrote:
*bump* Great idea!

this can also be replicated with variables, like this:

when gf clicked
set [x pos v] to <x pos you want>
set [y pos v] to <y pos you want>
wait until<<<x position> = (x pos)> and <<y position> = (y pos)>>
do stuff

Please, next time you post, look at the time of the post before you.

Last edited by TorbyFork234 (2012-05-10 00:44:16)

Scratch

archived forums

#1 2007-08-14 18:08:13

Touching at x_y_ blocks

#2 2007-08-14 18:17:01

Re: Touching at x_y_ blocks

#3 2007-08-14 18:39:12

Re: Touching at x_y_ blocks

AlveKatt wrote:

#4 2007-08-15 04:20:20

Re: Touching at x_y_ blocks

#5 2007-08-15 12:25:19

Re: Touching at x_y_ blocks

#6 2007-08-15 12:39:36

Re: Touching at x_y_ blocks

#7 2012-05-09 22:26:00

Re: Touching at x_y_ blocks

#8 2012-05-09 22:35:17

Re: Touching at x_y_ blocks

#9 2012-05-10 00:43:15

Re: Touching at x_y_ blocks

MathWizz wrote:

Board footer