IronBit_Studios wrote:

Basically, what my idea is is that there should be an “Touching any sprite” Boolean, because for some projects that involve just touching a sprite in general (Like a scanner that checks for sprites), it takes a long time to write “if touching Sprite2 or if touching Sprite3, etc.” I think it would look like this:
credit to stickfiregames

<touching [any sprite v] ?>

There should also be a reporter called

(sprites touching :: sensing)

I'm noticing a lot of people are asking the same thing-

Alberknyis wrote:

Explain where an “any sprite touched” block could be used.

Well,

IronBit_Studios wrote:

Projects that involve sprite-scanning, for some projects that involve just touching a sprite in general (Like a scanner that checks for sprites), it takes a long time to write “if touching Sprite2 or if touching Sprite3, etc.”. It would be fairly easy to implement, and otherwise…

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

CURRENT SUPPORTERS (46 And Counting)

IronBit_Studios(obviously)
stickfiregames
CosmicSans
CatsUnited
LionsStair
NolanAwesome
44701
scratchrainbow
Silphaer
peterules54
ev3commander
Alberknyis (90%)
Cyoce
theonlygusti
Starbolt1
TheHockeyist
mundofinkyenglish
Tommy100
m801234
JoeyTheChicken
scrooge200
Penguin9090_new
thelucariokid
scratch_inno
Tymewalk
nether_before
19f8361
pokejofe
HSL2014
Pot-Of-Gold
marilynjosiahbojo
CGRises
Cream_E_Cookie
Samanyolu
Unlicht
Scratcher1002
scratchinghead
wizard192
gamebeater187
BookOwl
Ninchanko
Botchko_Otkho
Leadrien2366
DrEthan
JonathanSchaffer
Inreal49

Non-supporters

ShadowFlareX
Econinja
Blank1234

<touching any sprite ? :: sensing>

<touching any sprite except for [not the sprite you want v] ? :: sensing>

Econinja wrote:

The workaround isn't very tedious. By saying that, we should have a block that records dates when you could do this:

(join (current [date v]  (join [/] (join (current [month v] (join [/] (current [year v] :: operator) :: operator) :: operator)  :: operator)

Excuse my messy scratchblocks syntax thing. You get the idea
No support.

(join (current [date v])  (join [/] (join (current [month v])(join [/] (current [year v] :: operator) :: operator) :: operator)  :: operator)

PkmnQ wrote:

-snip-

<touching any sprite ? :: sensing>

<touching any sprite except for [not the sprite you want v] ? :: sensing>

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

if <<touching [any sprite v]?> and <<not <touching [Sprite18 v]?>> and <not <touching [Sprite19 v]?>>>> then
broadcast [Touching any sprite but Sprite18 and Sprite19! v]
end

when I start as a clone // this is a particle!
forever
  move around using particle physics
  delete (all v) of [Sprite List v]
  add [Normal Ground] to [Sprite List v] // a floor/wall sprite
  add [Enemy Ground] to [Sprite List v] // another floor/wall sprite
  add [Enemy Class] to [Sprite List v] // has clones that might move around
  add [Player Class] to [Sprite List v] // has clones that are controlled by player(s)
  detect touching
  if <(Touching?) = [1]> then
    delete this clone // oh no, we died
  end
end

define detect touching
set [Touching? v] to [0] // 0 by default, if we're not touching any of the sprites this won't be set to 1
set [parse v] to [1]
repeat (length of [Sprite List v]) // for every item, if we're touching that sprite, touching should become true
  if <touching (item (parse) of [Sprite List v]) ?> then // the important part!
    set [Touching? v] to [1]
  end
  change [parse v] by (1)

define move around using particle physics
move (10) steps // just for the example

<touching [backdrop v] ?>

<not <touching [any sprite v] ?>>

_nix wrote:

I'm obviously not going to go through all the pages of this topic to see if anybody's suggested this, but it's possible that the “touching” block will be able to take arbitrary inputs (that is, reporters) in Scratch 3.0. In that case you could do something like this:

when I start as a clone // this is a particle!
forever
  move around using particle physics
  delete (all v) of [Sprite List v]
  add [Normal Ground] to [Sprite List v] // a floor/wall sprite
  add [Enemy Ground] to [Sprite List v] // another floor/wall sprite
  add [Enemy Class] to [Sprite List v] // has clones that might move around
  add [Player Class] to [Sprite List v] // has clones that are controlled by player(s)
  detect touching
  if <(Touching?) = [1]> then
    delete this clone // oh no, we died
  end
end

define detect touching
set [Touching? v] to [0] // 0 by default, if we're not touching any of the sprites this won't be set to 1
set [parse v] to [1]
repeat (length of [Sprite List v]) // for every item, if we're touching that sprite, touching should become true
  if <touching (item (parse) of [Sprite List v]) ?> then // the important part!
    set [Touching? v] to [1]
  end
  change [parse v] by (1)

define move around using particle physics
move (10) steps // just for the example

This project implements a simple particle that will disappear when it touches any sprite or clone from the “Sprite List” list. Plus, it's pretty easy to customize – for example, you could make it so that you might don't add the player to the sprite list if the player has an invisibility power-up.. and you wouldn't be able to do that using “touching (any sprite)”.

(number of sprites i'm touching::sensing)

TopicBumper wrote:

Bump.

BanMeOS wrote:

TopicBumper wrote:

Bump.

<touching [all sprites v] ?>

redgreenandblue wrote:

Honestly I would like a

<touching [backdrop v] ?>

It would do the same thing as a

<not <touching [any sprite v] ?>>

<touching [ any sprite] ?>
broadcast [ I guess I agree?]