Nor'easter
Deity
- Joined
- Feb 25, 2007
- Messages
- 2,014
to give a bit more context on the memory side of things,
new xml entries cost barely anything in terms of memory since they're only stored once.
What matters is the dynamic elements of the game (the actual units, cities, players , as opposed to the blueprints from the xml).
those dynamic entries have a slightly larger memory cost, since they need to keep every stat on hand. One particular case is that units keep a full array of "true/false" values of the size of promotions ( that tells the game whether the unit has the promotion). The real memory cost is that those are duplicated for each active unit in the game. So each time you add a new promotion to the xml , the data from every unit becomes slightly larger. it's barely anything on one unit, but could start to amount to something across all units and given enough promotion added.
Thanks for explaining it so clearly.