Map Making 2.6 Change Summary
Review the documents at: https://github.com/triplea-game/triplea/tree/master/docs/map-making/reference, particularly the feature change log for 2.6
- will no longer need to update 'triplea_maps.yaml', it is no longer used in 2.6
- map repository and map name no longer have to have the same name. The map name is arbitrary and is pulled from the map.yml file.
- game notes are loaded from disk every time 'game notes' are rendered in game.
- game errors / notifications are now sent to log file. The log file will be generated in "<your home folder>/triplea/triplea.log". When working on a map, check this file for additional information.
Please let me know if you have any questions. I hope for 2.6 to be released sometime in March.
- 2.6 will auto-migrate maps that are already downloaded for players to have the above requirements. 2.6 will generate a map.yml file (if it does not exist) and will generate the game notes file.
So when 2.6 comes out existing maps are all good and we can look at the new folder setup for how to do it ? Or maybe a full example that we could update @Frostion 's map upload link :
@beelee In short, yes.
@lafayette How tested is this? Previous prerelease versions of 2.6 have done such things as
- Erasing dozens of zip files in my folder without warning
- Becoming locked on a single game name, giving me an error whenever I tried to use the select game screen
- Creating dozens of folders starting with triplea followed by random numbers
I had to go back to using a stable 2.5 release. I am still cleaning up the mess made.
Schulz last edited by
I hope I will be able to open maps in this version.
@rogercooper Whenever a player downloads a prerelease, they are testing it, that is how prereleases are tested.
@lafayette I forget to mention scenarios not appearing on the selection screen, even though they were in map.yml
Unless major fixes have been made to the prerelease, I am not going to try it. On the last prerelease I tried, I received an error whenever I tried to choose a scenario.
You need to test it robustly. Make sure a single malformed mod does not cause the selection screen to fail. Warn users before ANY file deletion. Resolve all the open issues.
@rogercooper This thread is not asking anyone to try 2.6 just yet, but instead to clarify what changes are coming up. Anyone that does try a prerelease should both be in coordination with development and in the context of QA testing. I am one person, to get robust testing it is a group effort.
Anyone wanting access to edit the Guide “How to make your map downloadable in TripleA” is welcome to send me their Gmail via chat or just press the request to edit button.
The guide is clearly out of date, but I don’t feel qualified to describe what to do anymore. I hope someone else will want to give it a try, someone with the “know how” plus the skills needed to describe how to make maps downloadable (in a simple and stupid manner).
If anyone is up for the challenge, I can say that a good way of testing is to write the guide and then afterwards have it tested by folks with zero map upload experience. I tried to make the guide have as little implicitness as possible and every step explicitly described.
Alternatively someone could make a brand new guide instead? Maybe using elements and ideas from this old one?
@frostion I did update it not too long ago, apart from images the text is mostly up to date. The need for description.html and preview.png are not yet mentioned but those are 2.6 features (not yet released).
It's probably prudent we convert this to be in the official documentation so that anyone can suggest an edit without needing to go through you first.
@lafayette Tried out the latest pre-release it seems to handling the scenarios I have correctly now, generating correct map.yml.
I would suggest sorting the new download list in descending order by category, so the mods of most interest would be first (and not my experimental 1914-COW-Empires).
Good to hear @RogerCooper
Are all of the changes making sense? There are quite a number of changes and number of things that are NO longer needed in XML for 2.6 (but should still be there to work with 2.5, so there is some duplication needed). For example, game notes MUST be put into an external file to be seen in 2.6.
@lafayette I think too much was done at once.
If the notes are missing, I thought 2.6 will look in the XML and generate them.
No map maker should be relying on the engine to generate any of these files for them. That behavior will go away, it's only there so that players do not need to redownload maps.
These are not that many changes necessarily, but the explanation has been too complex.. Game notes, map.yml and description.html are the only new things.