that's what I assumed, but I tested that theory and It doesn't go top to bottom. I placed three actors 1 at 100,100 second at 200,200 and the third at 300,300 I had a fourth actor at 400,200 and told him to go 100,100 200,200 and 300,300 in that order and he moved to 200,200 then 300,300 then 100,100?
tatiangMember, Sous Chef, PRO, Senior Sous-ChefPosts: 11,949
So is that just a bugged behavior?
Yes, I see what you mean. I copied your rules and my actor does the same thing. Odd. I had heard Move To had some problems and because of that I've never used it in an app.
I was just curious about the behavior I have already gone a separate route it would just make the process a lot easier if it were working top to bottom. considering the amount of moves my project has.
Comments
https://imageshack.com/i/mrg12cp
Move To 100, 100
Timer -> After .5 seconds
Move To 200, 200
Timer -> After 1 seconds
Move To 300,300
You might have to adjust your time in seconds depending on how far and fast your actor is moving.