Seems to me the French AI got stuck on wagon trains...see attached screenshot (savegame too large). There\'s another city with a large number of wagons as well.
Great... this looks like several bugs at the price of one. ;)
1. AI error - if there's really nothing better to build than wagon trains, the AI should, sooner or later, decide to build nothing at all and instead give other jobs to Lumberjack and Carpenter.
2. Model/Specification error - Col1 has a limit for the number of wagon trains specified (not more than the number of colonies). I doubt the French player had 51 colonies or more, so this limit seems to not be properly obeyed. This part seems to be FIXED IN TRUNK already - at least there's a limit coded in the specification.
3. Last but not least - even with the limit in place, what should happen if a player conquers a colony containing (several) wagon trains? Should he get them even if that means that he will exceed the allowed limit - or should surplus (or all?) wagon trains be destroyed in that process?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think the limit should only apply to the building of new wagon trains. And it is possible that the limit, although encoded in the specification, is not actually enforced. Although it should be.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the wagon construction limit did not cause wagons to be destroyed if you lose or abandon a settlement, so can be considered a limit on construction only.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If there's a limit on wagon trains...between what I've built, and what I've conquered, I'm well over. I've currently got 95 wagon trains, with less than 50 settlements. I have no problem building more. Though I doubt I've personally built more wagon trains than settlements; perhaps the limits aren't tied together? Probably should be (if it's an intended 'feature' of the game, of course). Should you do as I, and conquer a lot of wagons, you can always destroy them if you need to build more elsewhere.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the info.
Great... this looks like several bugs at the price of one. ;)
1. AI error - if there's really nothing better to build than wagon trains, the AI should, sooner or later, decide to build nothing at all and instead give other jobs to Lumberjack and Carpenter.
2. Model/Specification error - Col1 has a limit for the number of wagon trains specified (not more than the number of colonies). I doubt the French player had 51 colonies or more, so this limit seems to not be properly obeyed. This part seems to be FIXED IN TRUNK already - at least there's a limit coded in the specification.
3. Last but not least - even with the limit in place, what should happen if a player conquers a colony containing (several) wagon trains? Should he get them even if that means that he will exceed the allowed limit - or should surplus (or all?) wagon trains be destroyed in that process?
I think the limit should only apply to the building of new wagon trains. And it is possible that the limit, although encoded in the specification, is not actually enforced. Although it should be.
the wagon construction limit did not cause wagons to be destroyed if you lose or abandon a settlement, so can be considered a limit on construction only.
If there's a limit on wagon trains...between what I've built, and what I've conquered, I'm well over. I've currently got 95 wagon trains, with less than 50 settlements. I have no problem building more. Though I doubt I've personally built more wagon trains than settlements; perhaps the limits aren't tied together? Probably should be (if it's an intended 'feature' of the game, of course). Should you do as I, and conquer a lot of wagons, you can always destroy them if you need to build more elsewhere.
Wagon trains have been temporarily disabled.
Fixed in 0.10.5.