We all know how there is a

go to [random position v]

block, but the mysterious thing is, you can put a reporter block in there, no matter what you put, let it be

go to (join[random position][])

or

go to (mouse x)

or

go to (join(45)(23))

So what does it do? Why does it allow a reporter to be inserted?

I never thought about this before. Seems like most of the reporter blocks don't do anything when you put them into the block, but I did find out something cool you can do with a variable

go to (sprite)

If you set the variable to the name of another sprite in the project, the “go to” block will actually work. There might be a few uses for that but idk

Wei-ern_520 wrote:

We all know how there is a

go to [random position v]

block, but the mysterious thing is, you can put a reporter block in there, no matter what you put, let it be

go to (join[random position][])

or

go to (mouse x)

or

go to (join(45)(23))

So what does it do? Why does it allow a reporter to be inserted?

because of variables, I can make objects go to different things using:

go to [(Sprite to go to at the moment) v]

Using

go to (join[Code Part 1 ][Code part 2])

we can join save codes

They do nothing - you must have something from one of the existing dropdowns in that block.

Doing this:

go to (Sprite)

Is literally the same thing as doing this (by default):

go to [Sprite v]

So I wouldn't see any purpose of adding a variable there.

A ‘Go to’ block helps us to make a sprite go to a sprite or random possition. I hope you get your answer ^_^

NMario84 wrote:

Doing this:

go to (Sprite)

Is literally the same thing as doing this (by default):

go to [Sprite v]

So I wouldn't see any purpose of adding a variable there.

It works if the variable value is the same as a sprite name. (After that I tried it).

Yea, the variable value has to be named as the sprite its going to align to. So what is the point? It can't align to itself, so may as well use the 2nd option I put below in my previous post.

You can do something like this instead:

set x to (mouse x)

Or like this:

go to x: (mouse x) y: (0)

Maybe if you wanted to save some if-then statements and had numbered sprites, then using reporters would be useful?

go to (join [Sprite] (my variable))