Transformations Extension Suggestion

123NJBG4

I surrport @scratchteam ADD THIS PLEASE[

My browser / operating system: MacOS Macintosh X 10.15.7, Unknown Browser, No Flash version detected
[/quote]
when green flag clicked
say [] for (2) secs
say [] for (2) secs
wait () secs
repeat (pick random ((() * (0)) - (0)) to (10))

end
[/list][/s]

mtaka4

123NJBG4 wrote:
I surrport @scratchteam ADD THIS PLEASE
-blocksnip-

Please explain why you support.
I've said this so many times auto correct predicted my whole sentence lol

Last edited by mtaka4 (Nov. 2, 2025 19:51:03)

123NJBG4

because it would bo awsome

Cade_MM

This obviously could be great for 3D, but this could be amazing for other things like animations, Also depending on how this is implemented it could be as simple as something like Pen!

d016

100% Support.

It's simple, powerful, and intuitive! But there's a problem that happens with these kinds of extentions:

set size to (100) %
set [vertical v] scale to (50) % :: extension
set [horizontal v] scale to (50) % :: extension
say (size) // is 100

// looks the same as

set size to (50) %
say (size) // is 50

jmdzti_0-0

d016 wrote:

That is not a problem, it’s simply how it’s meant to work.

I guess this could finally mean we could actually have infinitely small sprites, unless it is capped. It could be made so at a certain size the sprite is not rendered but still works (so it doesn’t crash webgl) in order to remove stage limits.

Last edited by jmdzti_0-0 (Nov. 7, 2025 22:39:22)

d016

jmdzti_0-0 wrote:

First of all, why do you leave quotes blank like this?

Secondly, my example showed that a new scratcher could get confused, as their sprite that looks 50% size is actually 100%.

I would probably add limits to be consistent with other Scratch limits.

nembence

~~~
[edited]

You can already make infinitely big sizes if you switch to a 0x0 vector costume before setting the size

d016 wrote:
100% Support.

It's simple, powerful, and intuitive! But there's a problem that happens with these kinds of extentions:
set size to (100) %
set [vertical v] scale to (50) % :: extension
set [horizontal v] scale to (50) % :: extension
say (size) // is 100

// looks the same as

set size to (50) %
say (size) // is 50

Another problem:
What if the sprite is rotated?

shift [right v] side [vertically v] by (sprite height)::extension
shift [bottom v] side [horizontally v] by (sprite width)::extension
shift [top v] side [vertically v] by ((-1)*(sprite height))::extension
shift [right v] side [horizontally v] by ((-1)*(sprite width))::extension

                  +            +
                 /|           v \
               T/ |R        Tv   \R
   T           /  |         v     \           R            R
 +---+   =>   +   +   =>   +       +  =>    +<<<+   =>   +---+
 |   ^        |  >          \     /        /   /         |   |
L|   ^R      L| >B          L\   /B      T/   /B        T|   |B
 |   ^        |>              \ /        /   /           |   |
 0---+        0            0   +        0---+            0---+
   B                                      L                L

Last edited by nembence (Nov. 8, 2025 12:17:33)

d016

nembence wrote:

Another problem:
What if the sprite is rotated?

shift [right v] side [vertically v] by (sprite height)::extension
shift [bottom v] side [horizontally v] by (sprite width)::extension
shift [top v] side [vertically v] by ((-1)*(sprite height))::extension
shift [right v] side [horizontally v] by ((-1)*(sprite width))::extension

                  +            +
                 /|           v \
               T/ |R        Tv   \R
   T           /  |         v     \           R            R
 +---+   =>   +   +   =>   +       +  =>    +<<<+   =>   +---+
 |   ^        |  >          \     /        /   /         |   |
L|   ^R      L| >B          L\   /B      T/   /B        T|   |B
 |   ^        |>              \ /        /   /           |   |
 0---+        0            0   +        0---+            0---+
   B                                      L                L

Didn't even realize that. You might be able to tell as the sprite is being skewed, not rotated, but it might get confusing for newer people.

Cade_MM

This is why its a extension

d016

Cade_MM wrote:
This is why its a extension

I see. But new Scratchers who use the extension could still get confused.

Other than the small bit of confusing, Support.

MrSpace-fish

Another problem:
What if the sprite is rotated?

shift [right v] side [vertically v] by (sprite height)::extension
shift [bottom v] side [horizontally v] by (sprite width)::extension
shift [top v] side [vertically v] by ((-1)*(sprite height))::extension
shift [right v] side [horizontally v] by ((-1)*(sprite width))::extension

                  +            +
                 /|           v \
               T/ |R        Tv   \R
   T           /  |         v     \           R            R
 +---+   =>   +   +   =>   +       +  =>    +<<<+   =>   +---+
 |   ^        |  >          \     /        /   /         |   |
L|   ^R      L| >B          L\   /B      T/   /B        T|   |B
 |   ^        |>              \ /        /   /           |   |
 0---+        0            0   +        0---+            0---+
   B                                      L                L

Not an issue.

Just make a tutorial.

Also: this would be just as confusing as rotating a symmetrical sprite: we aren't getting rid of sprites now are we?

Last edited by MrSpace-fish (Nov. 7, 2025 21:52:10)

Nameorus

I think There could also be a kind of vector system with corners.

nembence

MrSpace-fish wrote:
nembence wrote:
Another problem:
What if the sprite is rotated?
(…)

Not an issue.

Just make a tutorial.

Also: this would be just as confusing as rotating a symmetrical sprite: we aren't getting rid of sprites now are we?

I've just realized that the top of the costume moves with the “top” edge
so this isn't a problem
(I was thinking something like that the blocks would move the wrong side of the sprite after rotating the sprite like this)

Although it would detach the rotation from the (direction) reporter

Last edited by nembence (Nov. 7, 2025 22:10:15)

MrSpace-fish

nembence wrote:
MrSpace-fish wrote:
nembence wrote:
Another problem:
What if the sprite is rotated?
(…)

Not an issue.

Just make a tutorial.

Also: this would be just as confusing as rotating a symmetrical sprite: we aren't getting rid of sprites now are we?
I've just realized that the top of the costume moves with the “top” edge
so this isn't a problem
(I was thinking something like that the blocks would move the wrong side of the sprite after rotating the sprite like this)

Although it would detach the rotation from the (direction) reporter

Once again, not a problem: the people who

a) would use this
b) would like to use this

would have no issue figuring this out, if they even introduce this kind of bug in the first place

jmdzti_0-0

d016 wrote:

First of all, why do you leave quotes blank like this?

That’s how I snip an entire post.

d016 wrote:

I see. But new Scratchers who use the extension could still get confused.

That’s the exact same reason it’s a good idea. Exploring confusing areas in a good way, i.e., not leaving you in the lurch, is an excellent method to apply those same skills later in life. Of course, there’s a line (although sometimes blurry) between what’s beneficial to add and what’s just cluttering up space, for example, adding an FPS block would be nice, but adding a reporter that returns the laws of thermodynamics in order is just not it.

Last edited by jmdzti_0-0 (Nov. 7, 2025 22:53:29)

_Paymer

100% support this is amazing

NewRAF

Makes 3D extremely easy, support

MrSpace-fish

Support!

This would super simplify Painter's Algorithm for 3D projects and make them run at 30 FPS instead of 3!

Not to mention this would be extremely useful to many other scratchers in combination with the existing graphics effects: this could add a whole new world of cool visual effects.

THEOFFICIALWCAY

Very good idea. We hope @Scratchteam adds this

Discuss Scratch