instead of being two separate blocks, they would be one, and would look like this.

turn () degrees :: motion

The reason why I say this is because you can easily make sprites turn counterclockwise by using negative values in the clockwise block, kind of making the turn counterclockwise block redundant. Plus, it'd be more efficient.

Oh, and just for compatibility, any projects that use the “turn clockwise” and “turn counterclockwise” blocks would be unaltered, using the same blocks as before.

the clockwise/counter-clockwise arrows could be easier to understand for newer users or kids who don't know negative numbers are a thing

Xzillox wrote:

the clockwise/counter-clockwise arrows could be easier to understand for newer users or kids who don't know negative numbers are a thing

True, and maybe they could keep the original blocks, but add this one as well.

IHaveToBlink wrote:

Xzillox wrote:

the clockwise/counter-clockwise arrows could be easier to understand for newer users or kids who don't know negative numbers are a thing

True, and maybe they could keep the original blocks, but add this one as well.

Or they could merge the blocks like this:

turn [counterclockwise v] () degrees ::motion
turn [clockwise v] () degrees ::motion

It could also have an rotate icon for both each dropdown item to prevent confusion (can't be shown in the scratch blocks since that syntax isn't supported).

However, if we replaced these blocks, it will break projects that use the existing rotate blocks unless Scratch migrates every single project that uses them

ajskateboarder wrote:

True, and maybe they could keep the original blocks, but add this one as well.
Or they could merge the blocks like this:

turn [counterclockwise v] () degrees ::motion
turn [clockwise v] () degrees ::motion

Because the blocks are longer, some projects where the code is very close together may become harder to read because the rotate blocks could overlap more, which affects the remixability a bit; having to move the code can be very annoying.

EDawg2011 wrote:

ajskateboarder wrote:

True, and maybe they could keep the original blocks, but add this one as well.
Or they could merge the blocks like this:

turn [counterclockwise v] () degrees ::motion
turn [clockwise v] () degrees ::motion

Because the blocks are longer, some projects where the code is very close together may become harder to read because the rotate blocks could overlap more, which affects the remixability a bit; having to move the code can be very annoying.

Right click -> Clean up blocks

ajskateboarder wrote:

EDawg2011 wrote:

ajskateboarder wrote:

True, and maybe they could keep the original blocks, but add this one as well.
Or they could merge the blocks like this:

turn [counterclockwise v] () degrees ::motion
turn [clockwise v] () degrees ::motion

Because the blocks are longer, some projects where the code is very close together may become harder to read because the rotate blocks could overlap more, which affects the remixability a bit; having to move the code can be very annoying.

Right click -> Clean up blocks

whenever i do that it makes it more confusing for me because it's all in just one vertical column rather than the scripts being next to each other

IHaveToBlink wrote:

Xzillox wrote:

the clockwise/counter-clockwise arrows could be easier to understand for newer users or kids who don't know negative numbers are a thing

True, and maybe they could keep the original blocks, but add this one as well.

If one block is exactly the same as another one, then why add it?

Xzillox wrote:

whenever i do that it makes it more confusing for me because it's all in just one vertical column rather than the scripts being next to each other

The cleanup button used to do sth different in 2.0, not sure why it was reverted to how it worked in 1.x though.

IHaveToBlink wrote:

The reason why I say this is because you can easily make sprites turn counterclockwise by using negative values in the clockwise block, kind of making the turn counterclockwise block redundant. Plus, it'd be more efficient.

What about for newcomers who don't know how to do this?

ajskateboarder wrote:

Right click -> Clean up blocks

What about for newcomers who don't know how to do this?

OP wrote:

turn () degrees::motion

This block is a little ambiguous.
Would a positive number in the input make it rotate clockwise or counter-clockwise?

OP wrote:

Oh, and just for compatibility, any projects that use the “turn clockwise” and “turn counterclockwise” blocks would be unaltered, using the same blocks as before.

So the existing rotate blocks just become one of those “hacked blocks” that still work but are hidden from the block palette?

Za-Chary wrote:

ajskateboarder wrote:

Right click -> Clean up blocks

What about for newcomers who don't know how to do this?

Newcomers can Google how, I guess? Anyways, I doubt you'd need to use the “Clean up blocks” feature since the difference in length between the current blocks and the merged block isn't that much

turn cw () degrees
turn ccw () degrees
turn [counterclockwise v] () degrees ::motion
turn [clockwise v] () degrees ::motion

The length difference could be lowered even more if the merged block just used an icon. (This block is stemming too much from the original suggestion, isn't it)

Bump because dupe

I suggested this, but @Paddle2See said the two blocks are the way they are because of scratchers not familiar with negatives

I’m assuming this would spin clockwise, but note that counter-clockwise is the standard for most measures.

ajskateboarder wrote:

IHaveToBlink wrote:

Xzillox wrote:

the clockwise/counter-clockwise arrows could be easier to understand for newer users or kids who don't know negative numbers are a thing

True, and maybe they could keep the original blocks, but add this one as well.

Or they could merge the blocks like this:

turn [counterclockwise v] () degrees ::motion
turn [clockwise v] () degrees ::motion

It could also have an rotate icon for both each dropdown item to prevent confusion (can't be shown in the scratch blocks since that syntax isn't supported).

However, if we replaced these blocks, it will break projects that use the existing rotate blocks unless Scratch migrates every single project that uses them

some kids dont know which way a clock turns bro