Discuss Scratch
- Discussion Forums
- » Suggestions
- » New Sensing block for Scratch
- Alex_PWA16
-
Scratcher
26 posts
New Sensing block for Scratch
Proposed Block:
<( ) is touching ( ) ?>
Why This Block Should Be Added
Right now, Scratch only allows a sprite to check if it itself is touching another sprite using:
<touching ?>
But there is no way to check collisions between two other sprites from a third script.
This makes certain games and systems much harder than they need to be.
What This Would Help With
Enemy–enemy collisions
Projectile hitting an enemy without coding in both sprites
Ammo / bullets checking collisions from a controller sprite
Physics engines
Raycasting and 3D engines (Scratchers use these a lot)
Multiplayer NPC logic
Inventory or UI detection
Benefits
Makes advanced projects simpler
Avoids messy workarounds with broadcasts, loops, or custom blocks
Easier for beginners to understand collision systems
Fits naturally in the existing Sensing category
Why It Would Not Break Compatibility
Sprites that don’t use the new block won’t be affected.
Older projects continue working normally.
Summary
This block would open up a lot of creative possibilities for Scratchers, especially those making advanced games. It’s simple, intuitive, and fits well with how Scratch already works.
<( ) is touching ( ) ?>
Why This Block Should Be Added
Right now, Scratch only allows a sprite to check if it itself is touching another sprite using:
<touching ?>
But there is no way to check collisions between two other sprites from a third script.
This makes certain games and systems much harder than they need to be.
What This Would Help With
Enemy–enemy collisions
Projectile hitting an enemy without coding in both sprites
Ammo / bullets checking collisions from a controller sprite
Physics engines
Raycasting and 3D engines (Scratchers use these a lot)
Multiplayer NPC logic
Inventory or UI detection
Benefits
Makes advanced projects simpler
Avoids messy workarounds with broadcasts, loops, or custom blocks
Easier for beginners to understand collision systems
Fits naturally in the existing Sensing category
Why It Would Not Break Compatibility
Sprites that don’t use the new block won’t be affected.
Older projects continue working normally.
Summary
This block would open up a lot of creative possibilities for Scratchers, especially those making advanced games. It’s simple, intuitive, and fits well with how Scratch already works.
<[Sprite1 v] is touching [Sprite2 v] ?>
Last edited by Alex_PWA16 (Dec. 21, 2025 10:38:39)
- newgoldyslimepupacc
-
Scratcher
3 posts
New Sensing block for Scratch
you forgor to color the block and also it exists on (removed by moderator - please don't name browser extensions).
Last edited by cosmosaura (Dec. 21, 2025 15:14:37)
- FreshTheCat
-
Scratcher
1000+ posts
New Sensing block for Scratch
To colour your block, use this scratchblock instead:
I think that for now, you can use this workaround instead:
<(Sprite1 v) is touching (Sprite2 v)? ::sensing>
<(Sprite1 v) is touching (Sprite2 v)? ::sensing>
I think that for now, you can use this workaround instead:
when green flag clicked //in Sprite1
forever
if <touching [Sprite2 v] ?> then
add [Sprite2] to [Sprites touching Sprite1 v]
else
delete (item # of [Sprite2] in [Sprites touching Sprite1 v]) of [Sprites touching Sprite1 v]
end
end
when green flag clicked //in another sprite
forever
if <[Sprites touching Sprite1 v] contains [Sprite2] ?> then
do whatever... ::grey
end
end
- Discussion Forums
- » Suggestions
-
» New Sensing block for Scratch