@0az https://github.com/triplea-game/triplea/tree/master/game-headless/scripts, the two scripts are bundled with the headless bot zip: https://github.com/triplea-game/triplea/releases/download/2.0.20234/triplea-game-headless-2.0.20234.zip
There were a few reasons to bring in 1.8 compatibility:
we are getting about one error report a week for players launching 1.8 maps. The 1.8 maps keep coming up:
we should never have assumed that we can upgrade all maps in bulk, we do not 'own' all maps. Not all maps are in the repositories
it's been a long running design principle that maps should never be broken. 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.
As mentioned, 2.3 has a new map parsing architecture that makes supporting 1.8 maps much easier. Adding in that support resolves the above problems and gives us a proving ground for being able to support more XML variations going forward.
As 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.
tripleabuilderbot created this issue in triplea-game/triplea
2.1.20365: GameParser#parseMapProperties - SAXParseException: game: Test1, line: 190, column: 26, error: Element type "attatchmentLis...
Turns out a patch was feasible, 2.2 is patched as: https://github.com/triplea-game/triplea/releases/tag/2.2.20868
If you've already downloaded 2.2, you should be prompted to download again the latest 2.2 to pick up the patch that fixes WaW.
Thanks Roi I understand and agree. I think it should be documented on here somewhere as Dan said. Maybe @Frostion map helper link would be a good spot ?
v2.0.20234 is now available with a few fixes.
I would expect another fix release again in the coming days.
I'm locking this thread. Discussion forums are bad at tracking bugs:
your bug reports are going to be lost if posted here
we're going to confuse ourselves by discussing all bugs all at once in one thread
Here is where to report problems: