HostedRedmine.com has moved to the Planio platform. All logins and passwords remained the same. All users will be able to login and use Redmine just as before. Read more...
Feature #905824
Abandon "embark" and "disembark" lists
0%
Description
Since (dis)embarking is enabler controlled, this mechanism is overhead now, we can do the same with requirements "UnitState", "OnNativeTile" and "CityTile", "CityCenter". (Of course the ruleset will bloat a bit for replacing one list item on two enablers...)
Related issues
History
#1
Updated by Sveinung Kvilhaugsvik over 1 year ago
Is this an "I'm working on this"-ticket or an "just to remind the developers"-ticket?
#2
Updated by Alexandro Ignatiev over 1 year ago
Sorry, I won't likely work on this topic, just a supposedly gentle reminder.
#3
Updated by Sveinung Kvilhaugsvik over 1 year ago
- Assignee set to Sveinung Kvilhaugsvik
#4
Updated by Sveinung Kvilhaugsvik over 1 year ago
I now remember why I didn't do this at once. How can disembark be replaced for the Transport Disembark actions? (as opposed to the "Transport Alight" action)? (Note its target kind)
I'll do embark unless you have a way to covert disembark too.
#5
Updated by Alexandro Ignatiev over 1 year ago
I think we could do the same thing as one I've suggested in #905820, add a requirement for unit's current transport type. If I understand right the code, in 2.6 if your Paratrooper can unload from Helicopter he will do it even if the heli is on Carrier and he can't jump from carriers (a bug or a feature?).
#6
Updated by Sveinung Kvilhaugsvik over 1 year ago
- Related to Feature #920365: Idea: new requirement range: sub target added
#7
Updated by Sveinung Kvilhaugsvik over 1 year ago
- Blocked by Feature #920366: Abandon "embark" list added
#8
Updated by Sveinung Kvilhaugsvik over 1 year ago
Alexandro Ignatiev wrote:
add a requirement for unit's current transport type.
I meant within the current requirement system. So no promise except for embark. It may still be done in time for 3.1.
.