Under the <ElementType name = "TraitInfos" line or something like that, you get the list of tags that are nested into traits themselves (and thus the order those tags should appear) each listed out as <element type= rather than <ElementType name=, which is a declaration. Basically you declare a tag with ElementType name, and then you apply it with element type under the appropriate declaration of the class object (like traits in general).
See if you can figure out what I'm saying there as you look further at the schema.
Yes TechResearchModifier can make a trait adjust the rate of research the civ gets when researching specified technologies. Thus, just as an example, you can make the Agricultural trait research the TECH_AGRICULTURE faster and the TECH_MINING slower if you wish. It's just a percentage modifier to the research volume when researching the denoted tech. <TechTypes> enables you to select the tech type that modifier applies to.
Thus, the proper XML syntax would be:
Code:
<TechResearchModifiers>
<TechResearchModifier>
<TechType>TECH_AGRICULTURE</TechType>
<iModifier>50</iModifier>
</TechResearchModifier>
<TechResearchModifier>
<TechType>TECH_MINING</TechType>
<iModifier>-50</iModifier>
</TechResearchModifier>
</TechResearchModifiers>
You may notice that under the declaration for TechResearchModifier
s is the application of the tag TechResearchModifier. See how in the above example, this makes sense? Then you look at the declaration for TechResearchModifier, and you can see that TechType and iModifier are applied as nested within TechResearchModifier. They are Declared elsewhere (and only ONCE anywhere in the schema!) but applied within TechResearchModifier. This leads to the xml info file syntax as expressed above.
ElementType name="bCivicOptionNoUpkeep" content="textOnly" dt:type="boolean"/>
Did you realize we had this all along and its never been used? Probably not since it hadn't been applied anywhere and I actually migrated it here from the civic option categories infos.
ElementType name="iUnitProductionModifier" content="textOnly" dt:type="int"/>
This is another migration from what was previously the unit infos tag ProductionTraits. I've also got an experience and production modifier coming in for Combat Class once I can get past my hangup here.
Oh, and as I usually try to go about it this way, every tag you currently see should be 'ready to go' though those that have gone unused so far are still in a watch for bug status.
Just to make sure they are all behaving entirely as desired.)
3 interesting, is that like a politician that changes his mind, depending which direction the wind is blowing?
