Change AppData Path#5
Conversation
|
Hm, it should probably migrate your settings/favorites then at least. Would be annoying for users to lose that. |
We could. One of the issues with allowing that is we'd have to handle if the user can even write to that directory in the first place, since currently the data sits in a directory that's always accessible and write-able to the current user (it being in |
|
It's also a bit of a chicken and the egg problem, since this is only launcher data, not game/client data. So, if we're setting the launcher config path, we'd need to store it somewhere static, so when the application boots up, it knows that the user overrode the launcher data path and where to find that path. So, it couldn't live with the other settings. |
|
I believe that it'd save a lot of headache later on to be authoritative with where we put stuff so that we can be absolutely sure that people don't make silly mistakes or have really odd decisions about where they put folder structures. Is on them for making silly mistakes, I'm just wary of adding "Space Station 14" branding to the footgun they've just shot themselves with. |
|
Just FYI, as long as you use the same sqlite database, you won't be in full control of the schema, which means that certain parties could break your launcher by doing migrations that screw up the tables. Which is why I PR'd this in the first place. |
This launcher should not use the same sqlite databases (e.g. settings.db) as the launcher this was forked from.