Changes between Initial Version and Version 1 of Ticket #5460, comment 3


Ignore:
Timestamp:
Jun 24, 2019, 1:03:03 PM (5 years ago)
Author:
wraitii

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #5460, comment 3

    initial v1  
    22> [12:55] <wraitii> the cause is that Combat.Approaching says we can't move to attack an enemy, which causes it to refuse the Attack order, which means we go back to IDLE, which then right away finds a new target, rinse, repeat
    33> [12:56] <wraitii> so either MoveToTargetRange is wrong, and should return true and the order accepted, or it is right, and then I don't think we have a much better choice than to make "Find New Target" part of the stuff we do in Idle-Timer instead of Idle-enter
     4
     5After some digging, this happens for formation members, since MoveToTargetAttackRange returns false. That formations members go through INDIVIDUAL.IDLE seems buggy.