I think this should be a good improvement (and the UI stuff can still be done later if someone is interested to pursue it). So it's actually a pretty reasonable experience - if you select something incorrect, you will get a message box with the details when trying to end the purchase phase, which will tell you what's wrong, and then the purchase screen will be shown again with your previous selections which you can correct. Production capacity is displayed on the panel at the bottom left 5/8 = 5 units currently purchased out of the 8 maximum production/placed allowed (if applicable)Īlthough I didn't re-implement the above, I just landed, which makes it so that if you get an error about your purchase, it won't clear your selections. Infantry was maxed out using the max button. It has been suggested this info can be useful to plan production count 2 The aaGun doesn't have a maxBuilt rule and hence no limit is displayed in the labelĬurrent unit count has been appended to the end of the Production tooltip (which makes the info easy to scan). Maxbuiltperplayer has ≤ on the purchase panel for each unit It would make the purchasing of these units less frustrating as getting it wrong cancels all your purchases. If we want to entice players to migrate from 2.5 to 2.6 there is a one feature request that affects about 1/4 of the maps in the map downloads so about 50 of the 200+ maps. tripleabuilderbot created this issue in triplea-game/tripleaĥ: GameParser#parseMapProperties - SAXParseException: game: Test1, line: 190, column: 26, error: Element type said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6: Adding in that support resolves the above problems and gives us a proving ground for being able to support more XML variations going forward.Īs a bonus, now that the map export is fixed, because players can launch 1.8 maps, if they want to upgrade them, they only need to now launch the map and can then re-export the XML.

The mechanisms to support this had some big problems and we dropped it in 1.9 as it was not scaling and really just was not cutting it.Īs mentioned, 2.3 has a new map parsing architecture that makes supporting 1.8 maps much easier.

It's been a long running design principle that maps should never be broken. We should never have assumed that we can upgrade all maps in bulk, we do not 'own' all maps. We are getting about one error report a week for players launching 1.8 maps. There were a few reasons to bring in 1.8 compatibility:

Triplea map creator program