move to

If you put more than one "move to" attribute in a rule how does the computer decide which x y coordinate it goes to first?

Comments

  • tatiangtatiang Member, Sous Chef, PRO, Senior Sous-Chef Posts: 11,949
    Rules and behaviors (I assume you meant "move to" behavior) are evaluated from the top down. The one on top (above) will trigger first.
  • LiekusLiekus Member Posts: 5
    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?
  • LiekusLiekus Member Posts: 5
    So is that just a bugged behavior?
  • tatiangtatiang Member, Sous Chef, PRO, Senior Sous-Chef Posts: 11,949
    It depends on the timing of everything. Can you post a screenshot of your rules?
  • LiekusLiekus Member Posts: 5
    it was just a test..

    https://imageshack.com/i/mrg12cp
  • tatiangtatiang Member, Sous Chef, PRO, Senior Sous-Chef Posts: 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.
  • jamie_cjamie_c ImagineLabs.rocks Member, PRO Posts: 5,772
    Try this:

    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.
  • LiekusLiekus Member Posts: 5
    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.
Sign In or Register to comment.