Topic on Glossary talk:Game data

Should the template for supporting / not supporting the XDG specifications be be independent for config and save files?

Template:

This game follows the XDG Base Directory Specification on Linux.

This game does not follow the XDG Base Directory Specification on Linux.

Often games store their config files within the save location which is at the XDG save location rather than splitting into save and config. For the wiki should we say that it correctly follows the specification for save files but not config files?

For example here (comments in source): http://pcgamingwiki.com/wiki/FTL:_Faster_Than_Light#Configuration_file.28s.29_location

We do not really worry about that. As far as I'm concerned, at least using the data path is great. Plus SDL2's SDL_GetPrefPath recommends the data directory, and it's enough of an achievement as it is.

As to FTL, I am not aware of it being a botched job like that - both the config file and the save files are in XDG_DATA_HOME, rather than one always using .local/share as the page implies.

If it uses either path, it's meant to be true. And in fact, it can be both - see Bit.Trip Presents... Runner2: Future Legend of Rhythm Alien, which uses XDG_DATA_HOME, but fails to use XDG_CONFIG_HOME correctly.

To elaborate on my chain of unhelpful edits, I changed it to say .local/share since I thought it was incorrect using data_home for config files, I didn't consider that it is still a variable even if it is not in the exact technical location available.

Your example with Bit.Trip Presents... Runner2: Future Legend of Rhythm Alien confuses me somewhat. Is it both because the save data is using the variable for data_home and the config is using the absolute fallback location for config_home?

Yes, that's the point here. Bit.Trip saves save games to XDG_DATA_HOME, but always uses the fallback for config files, never using XDG_CONFIG_HOME.