Move To behavior - move to object on click

The new MoveTo plugin is nothing like Rex's plugin. His was more intuitive. I want to click on screen and have the player move to the red X. what am I missing?

Check this C3 example:

https://www.dropbox.com/s/embo49759liz9z1/move%20to%20test.c3p?dl=0

Looks like a major bug. Move To Position is working correctly but Move To Object seems to set position instead of move to.

Glad it looks like a bug and I'm not losing my mind.

Ashley Do I need to file a bug report or is this enough to get it corrected?

Move to X, Y works good, seems like a bug...but its still in beta, so, just use direct coordiantes :)

Huh, looks like a bug with moving to an object specifically. Please file it on the tracker to make sure it doesn't get lost in the forum.

Bug report filed.

https://github.com/Scirra/Construct-3-bugs/issues/3383

Thanks for fixing this. it works!

I was hoping "Move to object" would follow the object, but it's actually the same as Move to (Object.x, Object.y)

It will follow the object, if the object is moving away and at the same speed or faster than the object following it. But if you want the object to follow it, there are other ways to get that.

Well the feature is still new, maybe suggest a "Follow object" action to Ash.

Why not just use "Move to object" every tick? If you have an action that starts automatically following an object, you'd also need an action to stop it again, and all that seems redundant compared to just using "move to object" with a condition that controls if it's true or not.

To me "Move to object" seems redundant, because it's the same as move to (object.x, object.y). I just think that it would probably be more useful if it could automatically follow the object.

This is not a suggestion, just a thought. I can definitely live with how it works now, and use "move to object" on every tick if needed.

To me "Move to object" seems redundant, because it's the same as move to (object.x, object.y). I just think that it would probably be more useful if it could automatically follow the object.

This is not a suggestion, just a thought. I can definitely live with how it works now, and use "move to object" on every tick if needed.

When you say it's the same as move to(objectx,objecty), what is that?

The method MoveToObject("object") is just a shortcut to MoveTo(object.X, object.Y). They'll behave exactly the same way. That's what dop2000 meant.

Cheers!