#5479 closed defect (fixed)
Order queue not followed / Units remain in INDIVIDUAL.WALKING state
Reported by: | elexis | Owned by: | |
---|---|---|---|
Priority: | Release Blocker | Milestone: | Alpha 24 |
Component: | Simulation | Keywords: | regression |
Cc: | Patch: | Phab:rP22422, Phab:rP22426, Phab:rP22430, Phab:D1907, Phab:D2066, Phab:rP22496 |
Description
Reproduce:
- Set initial units to gather some resource
- Order a resource dropoff command to the CC
- Queue an order to move somewhere else
Observed result:
Some of the units keep standing at the resource dropsite in INDIVIDUAL.WALKING
state (without moving) and not performing the queued order to move elsewhere.
Bug observed with r22426 and previous revisions.
Attachments (1)
Change History (7)
comment:1 by , 5 years ago
comment:2 by , 5 years ago
Not sure if this is the same or distinct issue:
Reproduce:
- Use the "gift from the gods" and developer overlay change-perspective to build some units for both players
- Simulate a battle, send a move order for units that are in attack range of enemies
Expected result:
- Once units finish the move order, they will attack nearby enemies
Observed result:
- Units remain in INDIVIDUAL.WALKING state while getting attacked by nearby enemies
Following r22426 replay attached to reproduce the bug, the bug existed at least a couple of days before that revision.
comment:3 by , 5 years ago
Milestone: | Backlog → Alpha 24 |
---|
comment:4 by , 5 years ago
All three cases above cannot be reproduced post D2066.
Case 1 (in the ticket description) was most likely cause by rP22422. Case 2 is fixed by D1907, the cause was that the target is unreachable. Case 3 is fixed by a combination of rP22426, rP22430 and D1907 / D2066
comment:5 by , 5 years ago
Patch: | → Phab:rP22422, Phab:rP22426, Phab:rP22430, Phab:D1907, Phab:D2066, Phab:rP22496 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Also related to #5510.
Fixed by the above diffs and Phab:rP22496.
comment:6 by , 5 years ago
Keywords: | regression added |
---|
Not sure if this is the same or distinct issue:
Reproduce: