An independent logic requested to realize the 'Infantry Linking' without causing any potential IEs
Bug #895847 reported by
LH_Mouse
This bug report is a duplicate of:
Bug #894989: Multiple types considered as one class to selection and BuildLimit.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ares |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
My idea is to add a tag, such as Selection.
To those units who has no Selection.LinkedTo= set:
If A can deploy into B, then use [A]\Selection.
If B can undeply into A, then use [A]\Selection.
If A cannot deply into anything, then use [A]\Selection.
If the tag is set, then:
If A can deploy into B, but [A]\Selection.
If A can deploy into B, but [A]\Selection.
That's all. And if possible, I'd rather like a multi-unit linking logic.
To post a comment you must log in.