Per-config save directory

Hi,

It would be awesome if individual configurations stored save files in different places. Right now there's no difference between the save location of a config which loads, e.g., just doom2.wad, versus a configuration which loads a common resource and a pwad on top of it. This means that saved games are shared between configurations, which causes load errors if your configuration isn't exactly the same as the one in which the save was created.

I have a Python script I use for ad hoc configurations at the command line at https://gist.github.com/horse-mans/9230251268a7838e9839. What I do there is create a save directory based on the exact command line configuration, so that running the script with the arguments

gzdoom_launcher.py C:\Games\Doom\engines\gzdoom\gzdoom.exe -iwad C:\Games\Doom\iwads\doom2.wad

will invoke the first argument (the engine) and add some more arguments, like so:

C:\Games\Doom\engines\gzdoom\gzdoom.exe -iwad C:\Games\Doom\iwads\doom2.wad -savedir C:\Games\Doom\DoomSaves\doom2.wad\

And then, if I add additional wads, e.g.:

gzdoom_launcher.py C:\Games\Doom\engines\gzdoom\gzdoom.exe -iwad C:\Games\Doom\iwads\doom2.wad -file C:\Games\Doom\custom\cchest3\cchest3.wad

The engine will be invoked like so:

C:\Games\Doom\engines\gzdoom\gzdoom.exe -iwad C:\Games\Doom\iwads\doom2.wad -file C:\Games\Doom\custom\cchest3\cchest3.wad -savedir C:\Games\Doom\DoomSaves\doom2.wad+cchest3.wad\

(note the new saved game directory whose name is a combination of the passed in -file and -iwad arguments)

A system like this in RocketLauncher would be fantastic.

It occurs to me you could also just specify per-.rocket file save directories based on their names, keeping the whole config nicely encapsulated.