I'm just working on the tech loading code. And i was just wondering if it would be a favorable idea to put the description of the associated effect/effectgroup also into the tech-describing xml file as inline python...
The document structure looks like this so far.
1.) What do you think about the structure? (did i forget something?)
2.) inline python script?
Code: Select all
<FreeOrion::TechTree>
<Category name="Social Science">
<tech>
<id>10</id>
<name>Mark I</name>
<description>Powerful solver for social problems (in- and outside the empire)</description>
<rpperturn>10</rpperturn><!-- RP's needed to advance this project for one turn -->
<research_duration>20</research_duration><!-- the minimum turns it takes to research it -->
<vispretech>2, 4</vispretech><!-- list of techs needed to make this one visible in the ResearchScreen -->
<unlpretech>2, 4, 9, 2</unlpretech><!-- list of techs needed to make this one researchable -->
<effect> <!-- inline python-script ??? would be cool -->
<?pyscript
dothis(withthis);
dotthat(withthat);
etc();
?>
</effect>
<subtechs> <!-- applied technologies -->
<tech>
...
</tech>
<tech>
....
</tech>
</subtechs>
</tech>
<tech>
<id>11</id>
....
</tech>
</Category>
<Category name="Category 2">
.....
</Category>
</FreeOrion::TechTree>
4.) should it be possible to define sub-categories?
if yes how deep? (infinite/restricted depth)
5.) should it be possible to define sub-techs of subtechs?
if yes how deep? (infinite/restricted depth)
6.) should instead of a list of prerequisite techs a list of condition-classes be used to determine visibility and researchability? (would make it much more flexible...)