The title says it all, I think that 3.0 is fine and I can live with it even though I prefer 2.0 much much much more.

While it is not necessary to me, I know what you are understanding about the cursor coordinate. But the sprite coordinate is okay to use without a cursor coordinator when you drag to the prediction, then drag closer to your target until you get the needed. No support needed.

Not directly.

What you can do is make two variables called “x point” and “y point” (or something similar) and create the following script:

when green flag clicked
show variable [x point v]
show variable [y point v]
forever
set [x point v] to (mouse x)
set [y point v] to (mouse y)
end

This way you have a way to see the x and y positions of the mouse at any time.

Alternatively, you could create a sprite and use this script:

when green flag clicked
show
forever
say (join (join [x: ] (mouse x)) (join [y: ] (mouse y)))
end

Hopefully one of these methods helps for the time being.

I totally agree that 3.0 is OK but 2.0 is much better. PS, https://scratch.mit.edu/discuss/topic/331170/.

Za-Chary wrote:

Not directly.

What you can do is make two variables called “x point” and “y point” (or something similar) and create the following script:

when green flag clicked
show variable [x point v]
show variable [y point v]
forever
set [x point v] to (mouse x)
set [y point v] to (mouse y)
end

This way you have a way to see the x and y positions of the mouse at any time.

Alternatively, you could create a sprite and use this script:

when green flag clicked
show
forever
say (join (join [x: ] (mouse x)) (join [y: ] (mouse y)))
end

Hopefully one of these methods helps for the time being.

It's kinda annoying that the fact you need to make variables so find the mouse X and Y. Can you make the Mouse X and Y reporters be displayable?