The Collision Block

1. Function
The Collision Block Would Be A Sensing Block.
It Would Function Similar To How The

Block Disables Collision Detection Blocks.

2. What Would It Be Used For
The Collision Block Would Allow Hidden Sprites To Detect Collisions.
It Could Be Used For Hitboxes.

3. Workarounds
A Workaround For This Block Would Be

However As Scratch Is For All Ages, Some Scratchers May Not Understand How The Workaround Functions.

4. Mockup
Here Is A Mockup Of The Collision Block :


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

No support, its very confusing to new users and the workaround isn't that hard.

Eason_9 wrote:

No support, its very confusing to new users and the workaround isn't that hard.

this ^

Bro the workaround is very clear ppl on the suggestion forums really underestimate new scratchers, and it’s no harder to understand than this. Would using the “collision mode to: inactive” disable non-hidden collisions too? You didn’t make it very clear for people. And “on/off” would be easier to understand than “active/inactive” tbh

hydrofungus wrote:

the workaround is very clear ppl on the suggestion forums really underestimate new scratchers, and it’s no harder to understand than this. Would using the “collision mode to: inactive” disable non-hidden collisions too? You didn’t make it very clear for people. And “on/off” would be easier to understand than “active/inactive” tbh

The Block Replaces The Collision Changes Caused By Hide/Show EG : Set To Active Will Enable Collisions Even If The Sprite Is Hidden And If The Block Is Set To Inactive It Will Disable Collisions Even If The Sprite Is Shown

This is super hard to understand, how would this be used? Why would we need this?

This is why I think we need more concisive rules on foruming, because… This Happens intentionally.

There are easy workarounds for this block.

No support.

We don't actually need this block… no support :(

Even for a 5 year old, a one block workaround can’t be that hard. No support.

use move blocks and sum code

or, y'know, you could just make sprites detect hidden sprites from the get-go without having all of these shenanigans set in place

unmet wrote:

(#11)
or, y'know, you could just make sprites detect hidden sprites from the get-go without having all of these shenanigans set in place

that would break a lot of projects.

Bump

wait. Did you just give the easiest one block workaround that everybody can understand with some context? That's just sabotaging yourself.

Eason_9 wrote:

No support, its very confusing to new users and the workaround isn't that hard.

Its not confusing its littery a block to change if hidden sprites can be collided

starlightsparker wrote:

Even for a 5 year old, a one block workaround can’t be that hard. No support.

Is this the one block?

hide

that just hides the sprite and disables collision.

DangerPuppy10 wrote:

wait. Did you just give the easiest one block workaround that everybody can understand with some context? That's just sabotaging yourself.

collision needs multiple blocks to work
edit: I was referring to actual collision
but the OP is suggesting others so maybe I misunderstood it

Roblox888i wrote:

Is this the one block?

hide

yes, and this for on:

set [ ghost v] effect to (100)

gdfsgdfsgdfg wrote:

DangerPuppy10 wrote:

wait. Did you just give the easiest one block workaround that everybody can understand with some context? That's just sabotaging yourself.

collision needs multiple blocks to work

you misunderstood it (which does indeed prove how confusing the suggestion is). Chippy is talking about how normally, when a sprite is hidden, the

<touching [sprite v] ?>

block would report as false even when a sprite overlaps with the hidden sprite. So chippy is suggesting that there be a block to make it report true even if the other sprite is hidden, achieving the same effect as

set [ghost v] effect to (100)

fine i’m not going to argue