Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#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:

  1. Set initial units to gather some resource
  2. Order a resource dropoff command to the CC
  3. 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)

commands.txt (58.9 KB ) - added by elexis 5 years ago.
Aggressive pacifists dying in r22426

Download all attachments as: .zip

Change History (7)

comment:1 by elexis, 5 years ago

Not sure if this is the same or distinct issue:

Reproduce:

  1. Select the CC
  2. Set a gather-rallypoint to a fruit or tree
  3. Qeuue a move-rallypoint
  4. Train or garrison/unload a unit a cavalry
  5. The cavalry will walk to the fruit or tree and not perform the queued move order

comment:2 by elexis, 5 years ago

Not sure if this is the same or distinct issue:

Reproduce:

  1. Use the "gift from the gods" and developer overlay change-perspective to build some units for both players
  2. 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.

by elexis, 5 years ago

Attachment: commands.txt added

Aggressive pacifists dying in r22426

comment:3 by elexis, 5 years ago

Milestone: BacklogAlpha 24

comment:4 by wraitii, 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 wraitii, 5 years ago

Patch: Phab:rP22422, Phab:rP22426, Phab:rP22430, Phab:D1907, Phab:D2066, Phab:rP22496
Resolution: fixed
Status: newclosed

Also related to #5510.

Fixed by the above diffs and Phab:rP22496.

comment:6 by elexis, 5 years ago

Keywords: regression added
Note: See TracTickets for help on using tickets.