Currently, if you migrate your settings.db from SS14Main to any other launcher, it's data overwrites the transferred .db file, potentially locking out data between launchers.
I really don't wanna spend several years learning SQL just to move a data table from one db file to another, having to manually retype all the data, only for it to be one letter off, so I should offer a solution:
Checks for .db type, and a way to export and import settings files for each launcher, easily and quickly, that in the case of upstream imploding and player data being rendered useless, like saved favorites for example, could be freely exported to other launchers without launchers failing to open.
Thanks!
Currently, if you migrate your settings.db from SS14Main to any other launcher, it's data overwrites the transferred .db file, potentially locking out data between launchers.
I really don't wanna spend several years learning SQL just to move a data table from one db file to another, having to manually retype all the data, only for it to be one letter off, so I should offer a solution:
Checks for .db type, and a way to export and import settings files for each launcher, easily and quickly, that in the case of upstream imploding and player data being rendered useless, like saved favorites for example, could be freely exported to other launchers without launchers failing to open.
Thanks!