Search the Community
Showing results for tags 'xml'.
Found 3 results
-
Can we make it possible to dictate where techs can go in the UI? It would be very helpful (and logical) to be able to place techs beneath the units that they primarily affect. For instance, Rank Promotion techs and "Tradition" techs ("Archery Tradition", "Hoplite Tradition" etc.) can go directly beneath the unit. Example: It could go in the building's template in the productionqueue/technologies component, perhaps productionque/technologies/row. <ProductionQueue> <BatchTimeModifier>0.8</BatchTimeModifier> <Entities datat- 7 replies
-
- 3
-
-
- javascript
- xml
- (and 1 more)
-
I know this may be controversial, but I think the current SpecificName scheme adds a minor amount of confusion, or at least a better scheme may add some more clarity where currently there is little. So, for example: <GenericName>Gallic Champion</GenericName> <SpecificName>Soliduros</SpecificName> This is actually a Swordsman, along with whatever that means to the game, but you don't know that from the name of the unit. What I would suggest is something like this: <GenericName>Champion Swordsman</GenericName> &l
- 2 replies
-
- 1
-
-
- javascript
- xml
- (and 3 more)
-
Currently, unit template files have a translatable field called Tooltip. This field, as far as I’ve seen, may contain the following information: • Unit classes (recently prefixed by ‘Classes:’). • Units that this unit counters (prefixed by ‘Counters:’). • Units that counter this unit (prefixed by ‘Countered by:’). • Unit description. In the XML, these are differenciated by line breaks. What would you think about providing separated fields for each one of these? • DisplayClasses (as opposed to the class names used in the game logic) • Counters • CounteredBy • Description Pros would be: • Easier