Obey XDG conventions regarding file storage path

[ghost]

Currently, everything is stored in the same folder, by default in ~/.local/share/unvanquished/. Everything means:

• the games' pkg files themselves
• the user configuration and public auth key
• mods and maps the user could have downloaded by moving to a different server
• game logs, which can grow quite big after few games, especially if playing solo or in LAN (since then you also get server's logs "for free")

I believe that those 3 elements should be separated, at least config and auth key should go in XDG_CONFIG, to prevent a mass "erase & reinstall" to also delete auth key and configuration. Or, to the contrary, to allow starting with fresh config without needing to download anew all the content

[slipher]

For me it would be really annoying if you had to hunt among multiple noncontiguous directory structures to find all the Unvanquished user data.

On non-Linux platforms there does exist a separation between the stuff installed by the installer, and everything else generated at runtime.

There's a -resetconfig command line option to reset key bindings and cvars.

[ghost]

For me it would be really annoying if you had to hunt among multiple noncontiguous directory structures to find all the Unvanquished user data.

There would be no hunting, since XDG's specs are pretty clear. When I want to give my $HOME a good cleanup, I basically start the cleanup in the XDG_CACHE_HOME (.cache) directory, which as the name makes pretty clear, only contains cached data. Then I usually go in XDG_DATA_HOME and certainly would not expect removing configuration files in there by accident.

But even if keeping things in a single directly, the current situation does include a lot of hunting:

• ./base/ -> downloaded stuff from internet, some will be overwritten by next release, but there will be many artifacts as several files include the version in their name
• ./base/pkg -> where most (but not all) of the non-overwritten stuff lands, worth hundred of megabytes
• ./config -> there is both auto-generated and static things in there
• ./pubkey -> do not delete this.
• ./conhistory, ./.log, ./.nexe -> junk files that are "useless" (logs are logs, obviously, and the .nexe will be extracted at each run anyway)
• ./crashdump -> "useless"
• ./glsl -> "useless"
• ./game -> lot of hunting will happen here, as many things are auto-generated by one might want to keep things such as navcon files, custom layouts, etc. There is also this ./game/stats/gameplay folder which can grow rather quickly (not a problem on a regular desktop, but certainly is a problem for people with a cheap VPS like me)
• ./pkg -> downloaded from internet, as mods and maps change, without any possibility to easily clean it up, this can quickly grow to hundreds if not thousands of megabytes

Note that I put quotes around useless, because I know why those files are for: I'm not saying they should not exist.

On non-Linux platforms there does exist a separation between the stuff installed by the installer, and everything else generated at runtime.

This would be a start, and XDG actually addresses this kind of concerns. Except for one thing: unvanquished have the habit to rewrite config files so they should probably be outside of the "generated" data.

There's a -resetconfig command line option to reset key bindings and cvars.

Nice to learn about it. Sadly I'll probably have forgot it when me or another player will need it.