I think there should be a block for: “Make Solid” because it would be useful to just do:

make [ v] solid

than:

when green flag clicked
forever
if <touching [ v] ?> then
broadcast [ v]
end
end

and then to both sprites in contact:

when I receive [ v]
move ((0) - (foo)) steps

foo being the speed

Please tell me if this is a duplicate or not a problem at all.

What would this do?

dude341 wrote:

What would this do?

I think this is supposed to be some sort of activate collision detection block.

No support, way too specific.

How exactly does this work?

poliwag second rule

-Osiris- wrote:

dude341 wrote:

What would this do?

I think this is supposed to be some sort of activate collision detection block.

No support, way too specific.

I agree.
—————–
If the sprite is a polygon,there is a simple workaround. Let's say you have a maze,you have the player sprite and the wall sprites. You can do this for every key (for example WASD or ARROW UP,ARROW DOWN,ARROW LEFT and ARROW RIGHT):

when green flag clicked
forever
if <key [w v] pressed?> then
change x by (5)
if <touching [wall v] ?> then
change x by (-5)
end
end
...
end

In reply to all the “How would this work?” questions, if sprite A and sprite B were touching, they couldn't move in the exact direction the other sprite was in or to show the complicated (current) way to do this:

if <touching [b v] ?> then
turn cw (180) degrees
move (foo) steps
turn cw (180) degrees
end

again, where foo is speed.

Botcho_Otkho wrote:

-Osiris- wrote:

dude341 wrote:

What would this do?

I think this is supposed to be some sort of activate collision detection block.

No support, way too specific.

I agree.
—————–
If the sprite is a polygon,there is a simple workaround. Let's say you have a maze,you have the player sprite and the wall sprites. You can do this for every key (for example WASD or ARROW UP,ARROW DOWN,ARROW LEFT and ARROW RIGHT):

when green flag clicked
forever
if <key [w v] pressed?> then
change x by (5)
if <touching [wall v] ?> then
change x by (-5)
end
end
...
end

That isn't what I meant I meant, I meant it wouldn't go through other sprites.

GiggyMantis wrote:

Botcho_Otkho wrote:

-Osiris- wrote:

dude341 wrote:

What would this do?

I think this is supposed to be some sort of activate collision detection block.

No support, way too specific.

I agree.
—————–
If the sprite is a polygon,there is a simple workaround. Let's say you have a maze,you have the player sprite and the wall sprites. You can do this for every key (for example WASD or ARROW UP,ARROW DOWN,ARROW LEFT and ARROW RIGHT):

when green flag clicked
forever
if <key [w v] pressed?> then
change x by (5)
if <touching [wall v] ?> then
change x by (-5)
end
end
...
end

That isn't what I meant I meant, I meant it wouldn't go through other sprites.

Yes, we know. This is too specific, no support.

No support because it's too specific (Duh)

when green flag clicked
say [I hate my username why did I name myself like this]

No support. Scratch isn't a physics engine, and if it was it would need a lot more than jut this one block.

At one point, the scratch 3.0 test build had a physics engine extension.

Does no one else see how useful this would be in creating games?

GiggyMantis wrote:

Does no one else see how useful this would be in creating games?

We do, but we don't believe it fits with the current set of default Scratch blocks. It might be something that could belong in an extension (not necessarily a bad thing!)

I think the block should be rephrased to

set solid mode [solid v]::extension // solid, not solid

(like the set drag mode _ block currently in Scratch 3.0)

What if one solid sprite tries to glide over another solid sprite?
Do solid sprites only interact with other solid sprites?
Is the edge considered solid or not?
When a solid sprite creates a clone, the clone likely inherits the solidity. However, it'd be right in the middle of its parent sprite. Would the clone remain there or automatically move to a free spot?
Which motion blocks would be considered “teleportation” (ie it doesn't check if the sprite would collide with another sprite while it moves to the new position) or actual “movement” (ie it checks each position as it moves to the new position, and if it collides with another sprite, it stops there)

Sheep_maker wrote:

GiggyMantis wrote:

Does no one else see how useful this would be in creating games?

We do, but we don't believe it fits with the current set of default Scratch blocks. It might be something that could belong in an extension (not necessarily a bad thing!)

I think the block should be rephrased to

set solid mode [solid v]::extension // solid, not solid

(like the set drag mode _ block currently in Scratch 3.0)

What if one solid sprite tries to glide over another solid sprite?
Do solid sprites only interact with other solid sprites?
Is the edge considered solid or not?
When a solid sprite creates a clone, the clone likely inherits the solidity. However, it'd be right in the middle of its parent sprite. Would the clone remain there or automatically move to a free spot?
Which motion blocks would be considered “teleportation” (ie it doesn't check if the sprite would collide with another sprite while it moves to the new position) or actual “movement” (ie it checks each position as it moves to the new position, and if it collides with another sprite, it stops there)

The idea of it being an extension is probably a better idea (like the sun effect idea).
Obviously I'm not the OP but I think some plausible answers would be:
1: The non-gliding one would probably be knocked out of the way
2: Maybe three modes, non-solid, semi-solid and solid, where non-solids don't interact and don't cause interactions, semi-solid where they interact with solids but don't cause interactions, and solid where they interact and cause interactions (does that make sense? probably not)
3: Probably?
4: Probably move to a free spot, or maybe they always start non-solid
5: Presumably the “go to” blocks, but not move, change or glide

I'd support this being an extension, but not being added into the main palette. It's useful but also pretty specific, so I think it'd fit an extension well.

Yeah people.
How can you make a sprite solid?

Therobloxn00b123 wrote:

Yeah people.
How can you make a sprite solid?

You can by learning Scratch.


______
There is no need for this block.

GiggyMantis wrote:

-snip-

Agreed

Pretty sure it's a dupe, anyways like everyone else said, too specific, and there are many ways of implementing this and just one way would be limiting for newer scratchers.

The unity game engine has rigid body mechanics, but scratch is a learning launguage so gravity and collisions are good for learning on your own. Also you don’t have to have a forever loop with an “if touching” block, you can have it check every time you move, saves processing power.

No support

No Support. This is too advanced for Scratch, and hard to understand.