Opened 12 years ago

Closed 11 years ago

Last modified 11 years ago

#1671 closed defect (fixed)

Units handle failed garrison order differently

Reported by: zoot Owned by:
Priority: Should Have Milestone: Alpha 12
Component: Core engine Keywords:
Cc: Patch:

Description

If a female citizen is queued to garrison a building that is already fully garrisoned and then walk somewhere else, she will walk to the fully garrisoned building, not enter (because it is full) and then proceed to walk somewhere else as ordered.

If a Gaulic Spearman (and probably other units) is queued to do the same thing, he will immediately disregard the garrison command and instead walk somewhere else without walking to the garrisoned building first.

If a female citizen is queued to walk somewhere, then garrison a full building, then walk somewhere else, she will walk to each of those three waypoints.

If a Gaulic Spearman is queued to do the same, he will walk to the first waypoint, the to the second (the full building) and then stop, without ever completing the order to reach the third waypoint.

Change History (4)

comment:1 by Deiz, 12 years ago

I assume you're referring to groups of units? Garrison orders cause formations to break up, and formation-capable units will always immediately create formations, if possible.

When a formation is created, it replaces the orders of its members, which is the behaviour you're seeing. It occurs whenever you queue a formation order when the selected units aren't currently in a formation. You can reproduce the issue by giving a group of formation-capable units a garrison, gather or attack order, and then queuing a walk order for them. They'll immediately discard their current orders and begin walking in formation.

in reply to:  1 comment:2 by zoot, 12 years ago

Yeah, I assumed it was the individual units but I can indeed only reproduce it with groups of units.

comment:3 by zoot, 11 years ago

Milestone: Backlog
Resolution: fixed
Status: newclosed

I can no longer reproduce this. I assume it was fixed as part of r12911.

comment:4 by historic_bruno, 11 years ago

Milestone: Alpha 12
Note: See TracTickets for help on using tickets.