Changes between Initial Version and Version 1 of Ticket #4015, comment 33
- Timestamp:
- Jan 19, 2017, 8:11:52 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #4015, comment 33
initial v1 2 2 3 3 wrt patch: the only real bug there still is (AFAIK), is what I tried to explain in last comment about the "unpack" order. (Ordering a unit to pack when unpacking (or other way around)). For proper functionality of ShouldPack {{{ || type == "Unpack"}}} should be appended. Only this doesn't solve the root cause. 4 The problem lays deeper into the the unitAI.Pack (or unitAI.Unpack, this whole thing should be done for that too) function, this only checks for CanPack, returning false when unpacking (as it should). But when getting a pack ordering while unpacking, the unpacking should simply be cancelled (agreed with wraitii and scythetwirler_). This can be done by pushing an cancelUnpack order when unpacking in the unitAI.Pack function.4 The problem lays deeper into the the unitAI.Pack (or unitAI.Unpack, this whole thing should be done for that too) function, this only checks for CanPack, returning false when unpacking (as it should). But when getting a pack ordering while unpacking, the unpacking should simply be cancelled (agreed with wraitii and scythetwirler_). This can be done by adding an cancelUnpack order when unpacking in the unitAI.Pack function. 5 5 6 6 (You can order a pack order while unpacking by selecting 2 sieges, 1 unpacking and 1 unpacked)