Prerequisites fullfilment by capturing certain houses' buildings
This logic was most likely used for Tiberian Sun's Construction Yard. As you know - there was one GACNST for both sides, however when GDI player captured GACNST which belonged to Nod player, he would receive new technology even when it was basically the same building.
With all prerequisite systems we have I wasn't really able to think of a workaround for this - I'm planning 3 subsides for every side and each of those subsides would have their own equipment. However, I don't want to give seperate factories for each subside, or even worse - seperate CYs because that would clutter the sidebar.
I don't want to provide each subside with a specific building because that method has it's own drawbacks ex. (that building is destroyed, subside can't even build it's basic but unique tank!).
So, for example if there are two following units - one is Confederation's unique basic tank and the other one is Russia's:
[HTNK]
Owner=Russians
Prerequisite=NAWEAP
[BTNK]
Owner=Confederation
Prerequisite=NAWEAP
The Russians would have to capture a NAWEAP owned by Confederation to aquire BTNK. Such logic would require a global enabler though, because it shouldn't be considered as basic logic in original YR - I'm pretty sure it would cause some issues.
Of course, I'm posting this request as something for eventual far future development because it was not a part of DFD and may be vetted by others. However, I think it would become useful for mods with unique subsides.
Blueprint information
- Status:
- Complete
- Approver:
- Graion Dilach
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Graion Dilach
- Definition:
- Approved
- Series goal:
- Accepted for 0.6
- Implementation:
- Implemented
- Milestone target:
- 0.6
- Started by
- Graion Dilach
- Completed by
- AlexB
Related branches
Related bugs
Bug #895920: Prerequisites fullfilment by capturing certain houses' buildings | Fix Released |
Sprints
Whiteboard
Accepted system is in the full specification. Changes might occur.
System will be delivered after 0.2 gets done.
2012-06-21: Implemented in gd03 branch.