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


Ignore:
Timestamp:
Jul 3, 2019, 12:35:14 PM (5 years ago)
Author:
elexis

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #5460, comment 10

    initial v1  
    1 Incorrect: the Jebel crash is because the unit is IDLE.
    2 It finds a new target, so tries to attack, but can't reach it. Since it's a garrisoned unit (ie. turret), it calls "FinishOrder" in Order.Attack.
    3 That makes us go through the Order.Garrison order that we have as a turret, which calls SetNextState("IDLE"), which loops all over again since there is FindNewTargets in IDLE.enter.
     1Incorrect: the Jebel crash is because the unit is IDLE. It finds a new target, so tries to attack, but can't reach it. Since it's a garrisoned unit (ie. turret), it calls "FinishOrder" in Order.Attack. That makes us go through the Order.Garrison order that we have as a turret, which calls SetNextState("IDLE"), which loops all over again since there is FindNewTargets in IDLE.enter.
    42
    5 So the jebel crash is caused by rP22023, the rest aren't, but FindNewTargets is a common thread in all of these.
     3So the jebel crash is caused by r22023, the rest aren't, but FindNewTargets is a common thread in all of these.