That's not how it works. Either the research topic (f. ex STR_ADEPTAS_ARMORS_DEP1) lists which dependencies it needs, of which all have to be met.
Or one research topic (f. ex STR_FLOATER_SOLDIER) unlocks a different research topic (f. ex STR_ADEPTAS_ARMORS_DEP1). The dependencies of your topic don't matter if you got a different one unlocking yours. Then dependencies aren't being checked on unlock (unlike requires)
research:
- name: STR_ADEPTAS_ARMORS
cost: 180
points: 20
dependencies:
- STR_ADEPTAS_ARMORS_DEP1
- STR_ADEPTAS_ARMOR
- name: STR_ADEPTAS_ARMORS_DEP1
requires: # is checked for unlock
- STR_ADEPTAS
dependencies: # are not checked for unlock
- STR_FLOATER_SOLDIER
- STR_FLOATER_MEDIC
- STR_FLOATER_NAVIGATOR
- STR_FLOATER_ENGINEER
- STR_FLOATER_LEADER
- STR_FLOATER_COMMANDER
- name: STR_FLOATER_MEDIC
cost: 75
points: 50
needItem: true
unlocks:
- STR_ADEPTAS_ARMORS_DEP1 # will unlock topic
- STR_INTERROGATION_COMPLETED
You can try the attached rul file.
That's not how it works. Either the research topic (f. ex STR_ADEPTAS_ARMORS_DEP1) lists which dependencies it needs, of which all have to be met.
Or one research topic (f. ex STR_FLOATER_SOLDIER) unlocks a different research topic (f. ex STR_ADEPTAS_ARMORS_DEP1). The dependencies of your topic don't matter if you got a different one unlocking yours. Then dependencies aren't being checked on unlock (unlike requires)
research:
- name: STR_ADEPTAS_ARMORS
cost: 180
points: 20
dependencies:
- STR_ADEPTAS_ARMORS_DEP1
- STR_ADEPTAS_ARMOR
- name: STR_ADEPTAS_ARMORS_DEP1
requires: # is checked for unlock
- STR_ADEPTAS
dependencies: # are not checked for unlock
- STR_FLOATER_SOLDIER
- STR_FLOATER_MEDIC
- STR_FLOATER_NAVIGATOR
- STR_FLOATER_ENGINEER
- STR_FLOATER_LEADER
- STR_FLOATER_COMMANDER
- name: STR_FLOATER_MEDIC
cost: 75
points: 50
needItem: true
unlocks:
- STR_ADEPTAS_ARMORS_DEP1 # will unlock topic
- STR_INTERROGATION_COMPLETED
You can try the attached rul file.
So run them all through DEP1 like this?
- name: STR_ADEPTAS_ARMORS_DEP1
requires:
- STR_ADEPTAS
dependencies:
- STR_FLOATER_SOLDIER
- STR_FLOATER_MEDIC
- STR_FLOATER_NAVIGATOR
- STR_FLOATER_ENGINEER
- STR_FLOATER_LEADER
- STR_FLOATER_COMMANDER
- STR_WARPTALON_SOLDIER
- STR_WARPTALON_COMMANDER
- STR_ORK_STORMBOY
With each dependency having the unlock, instead of DEP1.
I.e the chain should be:
1. "research ANY ONE of the listed (flying) units",
2. This Unlock "DEP1" (DEP1 has no research cost, so the player gets it right away without researching it as a topic)
3. DEP1 is set as dependency for all of the Flying type armors. If other dependencies are fulfilled,
4. The Flying Type Armor of your faction is now available as a research topic.
(haven´t made DEP1 the dependency for the Assault Marine Armor yet but that´s the idea).
To limit each armor unlock to only one faction or strategy, it might require several DEP1 versions, like for assault armor:
- name: STR_ASS_ARMOR
cost: 180
points: 20
dependencies:
- STR_ASS_ARMOR_DEP1
- STR_PERSONAL_ARMOR
- name: STR_ASS_ARMOR_DEP1
requires:
- STR_ASSAULT
dependencies:
- STR_FLOATER_SOLDIER
- STR_FLOATER_MEDIC
- STR_FLOATER_NAVIGATOR
- STR_FLOATER_ENGINEER
- STR_FLOATER_LEADER
- STR_FLOATER_COMMANDER
- STR_WARPTALON_SOLDIER
- STR_WARPTALON_COMMANDER
- STR_ORK_STORMBOY
Each listed unit have unlock: - STR_ADEPTAS_ARMORS_DEP1 and STR_ASS_ARMOR_DEP1, but because each armor DEP1 research topic is limited by an "requires: X Faction", only the relevant armor should appear as a topic for the player.