DSDA-Doom configuration being saved onto ~/.dsda-doom instead of $XDG_DATA_HOME

[RedStoner420]

When using DSDA-Doom v0.28.0 (which added support for the dsda-doom config folder inside $XDG_DATA_HOME) it reads and writes configuration from and to $XDG_DATA_HOME/dsda-doom as expected. However, when launching dsda-doom with dsda-launcher it saves configuration to ~/dsda-doom.

[Pedro-Beirao]

dsda-launcher currently only supports ~/.dsda-doom, and its configuration files are saved there.
For the next version, ill be sure to add support for $XDG_DATA_HOME the same way dsda-doom does.

But are you saying that the dsda-doom v0.28.0 configs (not the launcher's) are also saved to ~/.dsda-doom? That should not happen. Maybe dsda-launcher is launching an older version of dsda-doom?

[Gliczy]

With the added support for $XDG_DATA_HOME in dsda-doom, it first checks for the legacy directory ~/.dsda-doom and if it's not found it will instead use $XDG_DATA_HOME/dsda-doom.

However, since dsda-launcher still uses ~/.dsda-doom for it's configuration, it will create this directory if it’s missing. This, in turn, will cause dsda-doom to use this directory for its configuration as well, since dsda-doom first checks for the legacy directory.

[Pedro-Beirao]

Oh I see. Thats funny!

I will fix this for the next version, but that wont happen until maybe september. Im busy and there is still quite a bit of work to be done for this update.