[BUG/GAMEPLAY] Pressing down arrow causes sovereign to move down, then left, then up

from Elemental Forums

Movement was working fine using the arrow keys then after my sovereign delivered a noble woman to her estate, it started acting strangely. Pressing down arrow caused sovereign to move down, then left, then up. My sovereign then died and was revived and he worked okay for a bit then started doing this again.

If I could also ask a question: Is there any other way to move in this game? Can't I click? There is no tutorial and nothing in preferences to help with this.

Thanks,
Gary

1,104 views 7 replies
Reply #1 from Elemental Forums Top

I am finding the same thing is happening even using right-click to set a destination. The sovereign will always go to the destination but will sometimes circle around, moving places where I've not asked him to go.

Reply #2 from Elemental Forums Top

This appears to only happen to the sovereign (haven't seen it with recruits as of yet) and only if there is movement left in the turn. Makes it impossible to get him to stop on a particular square.

Ashes of the Singularity II
Reply #3 from Elemental Forums Top

Is there any other way to move in this game? Can't I click?
End of quote

Yes, just select unit(s) and right click a destination.

Reply #4 from Elemental Forums Top

Even if I right-click, if the NPC I am moving has movement left in their turn, they will act erratically, IOW, then will move even though I told them to stop on a particular sqaure.

Reply #5 from Elemental Forums Top

Did you have them set to autoexplore?

Reply #6 from Elemental Forums Top

Quoting kryo, reply 5
Did you have them set to autoexplore?
End of kryo's quote

 

No, the sovereign was not set to auto-explore. And actually, I did set another NPC to auto-explore and they never moved a muscle...

I'll double check just to make sure I don't have them backwards or something, but if auto-explore means to always move in the same circular pattern, it's pretty broken.

Reply #7 from Elemental Forums Top

I am not currently seeing this problem in Beta 2-A.