save game setups

[titi]

It would be nice to have a way to save game setups like we already do for the "restore last game settings"-Button, but we should be able to store several setups and cycle through them in the custom menu.

To avoid to just blindly store the last 100 setups or something like this, I suggest to save setups map based! So the file names for the saved game setups should be something like:
<mapname>-last.mgs  ( .mgs= MegaGlestSetup )

This allows us to use the map selector to use this feature too like this:
- select map you want and restore last setup for this map.

Questions:
Would this be good enough or do we want a way to cycle through the last settings ? Or can this be combined somehow? ( keep in mind that the custom menu is already VERY crowded!)

[Ishmaru]

How about we save last played settings on a per map basis, and load those settings automatically when map is selected?
This way we don't need to add more buttons to the menu. Also this will help so much with all the maps both varying team set ups (2v2, 3v3, 5v3, 2v2v2, etc)

[kagu]

I also suggested something similar https://forum.megaglest.org/index.php?topic=9498.msg90542

[titi]

yes, thats very similar, but we need a good way to combine all those ideas.

What we want is:
0. auto saved setups
1. several saved setups of games
2. saved setup(s?) per map
3. ideally no monsterchange in the GUI ( or at least something which will fit in the GUI )

[jammyjamjamman]

It would be nice to be able to save your own game presets and recall them for later games. I propose that this would be done by adding a save game settings button which behaves like the automatic reload last settings save, Then, you can recall the preset you want later.

[andy_5995]

Good idea

[titi]

this was made in git version now. Currently I am a bit undecided if I should have saved setups seperated for each techtree or not. What do you think?

[andy_5995]

this was made in git version now. Currently I am a bit undecided if I should have saved setups seperated for each techtree or not. What do you think?

Maybe better to use as-is for now, and then think about it more after the next release. Saves you a little time and you get more user feedback in the meantime.