As reported by Angen and Gurken Khan on the forums, there is a crash following rP22023 caused by an infinite loop in UnitAI.
The loop as described by Angen in rP22023:
... -> enter IDLE -> Find Targets -> Order.Attack -> Order.Attack fails (movement fails but it could be anything else) -> finishorder -> setNextState(IDLE) -> leave and enter IDLE -> ...
I believe we switch to IDLE so that our default "no order" state is IDLE.
I don't think we can fix the Order.Attack behaviour by itself - D13 would make the moment _likely_ return true but not always.
Finding new targets right away in IDLE.enter also seems reasonable, not waiting a turn is better.
So >> It does seem like we don't want to leave-re-enter IDLE from finishOrder. So my fix is to explicitly check for that.