Touching Any Sprite Boolean

Meep5010

support
the workaround may not be too big if you have a few sprites, but if you need to use it alot or have a lot of sprites the suggested block would be a lot better for, less powerful computers

julianandwill

Absolute support!

Alpha_Hedge

Full support. I was thinking about making a “Don't Touch Anything” sort of game, so this would really help. Otherwise, I'd have to…well, you know x3
http://prntscr.com/agk184

pvz_pro

support

Sheep_maker

Questions:
Would the boolean report itself?
How would the reporter report multiple sprites?

IronBit_Studios

Sheep_maker wrote:
Questions:
Would the boolean report itself?
How would the reporter report multiple sprites?

What do you mean?
It would give a list of sprites.

Sheep_maker

IronBit_Studios wrote:
Sheep_maker wrote:
Questions:
Would the boolean report itself?
How would the reporter report multiple sprites?
What do you mean?
It would give a list of sprites.

I meant if the boolean would detect the sprite executing the code because as of now, the touching block thinks that a sprite would be always touching itself.

How would someone use this list, like if I set a variable to it:

set [var v] to (sprites touching::sensing)

AwesomePerson238243

support, but not a whole new block. just make it another dropdown in the

<touching [ spritename v] ?>

block

Last edited by AwesomePerson238243 (April 9, 2016 07:22:31)

Techno-CAT

support this

IronBit_Studios

Bump, let's see where this goes

Gobblesmack

stickfiregames wrote:
<touching [any sprite v] ?>
I support

alexphan

Support, this would be very useful for games where many sprites count as obstacles.

Also, how about

<touching [any clone v] ?>

?

LemonComputer

I EXTREME support. I accidently came with the same idea!

pack34

support!

MasterJPixel

I support. Extremely long booleans are my worst enemy.

I'm not kidding, I named my Pokemon HeartGold rival “Boolean”.

PkmnQ

IronBit_Studios wrote:

<<touching [ v] ?> or <<touching [ v] ?> or <<touching [ v] ?> or <<touching [ v] ?> or <<touching [ v] ?> or <<touching [ v] ?> or <<touching [ v] ?> or <<touching [ v] ?> or < > > > >> > >  > >

Here's a solution:
Make sure all the outlines are the same color and then,

<touching color [Whatever the color is] ?>

Still, I support this because the outlines might not be the same color.

Last edited by PkmnQ (Dec. 2, 2016 15:27:02)

PkmnQ

alexphan wrote:
<touching [any clone v] ?>
?

Maybe the reverse can work.

when I start as a clone
if <touching [wanted sprite v] ?> then
. . .
end

Last edited by PkmnQ (Feb. 17, 2017 08:26:35)

awesome5185

Great idea, although i never had to use it, support.

A_Geeky_Jawa

Support!

ETS12345

when green flag clicked
forever
say [I support!!!]
end

Discuss Scratch