Date variables?

In the CIV5GameSpeeds.xml file, there are several tables. The second set of tables has 7-8 entries for each speed that give a number of turns, and a number of months each turn corresponds to. These are read sequentially, so the game might spend 95 turns at 40 years per turn, then 65 turns at 20 years per turn, and so on down the line. The starting point is set to -4000 (4000 BC) within GlobalDefines, which can be easily altered. And note, the values are in MONTHS (so 480 means 40 years per turn); if you set the numbers below 12 it'll still work, but the game won't appear to increment the year counter. (Using actual month names only happens in scenarios, I think.)

The maximum number of turns in a game will simply be the sum of the 7-8 entries for whichever game speed you've selected. 350 for Quick, 500 for Standard, and 750 and 1500 for the slower speeds; this determines when a Time victory can happen. My mods have altered this table for a long time now, because I'd slowed down the pace of the game and needed the year numbers to still correlate well (especially once I added future eras). The one other thing you need to keep in mind is that in the Eras table, each era has a variable <StartPercent>, a percentage of the maximum number of the turns for late-era starts. That is, if Industrial has StartPercent=50, then choosing to start in the Industrial Era would start you on turn#250 on Standard, 175 on Quick, and so on; if you're adding new content at one end of the tree, to where the maximum number of turns would need to increase, then you'd need to adjust all of these as well to keep the year numbers relatively consistent.

Now, you could just delete that entire table and re-fill it by hand, or use SQL to multiply/divide all entries as necessary, but I've found it safer to just use very explicit Update commands.
 
Thanks! I was thinking the same as you once I found it -- I run long tables through some regular expressions in notepad++ to convert into update statements, with original values stored in comments.
 
Back
Top Bottom