When a user manually moves the installation folder to another folder/disk, bs-manager still uses the default or installation-folder property in config.json.
Solution
If the installation folder (BSManager) does not exist on startup, prompt the user a modal to select either a new or existing installation folder. Default installation folder value should still be used on the prompt.
Workaround
Manually editing the config.json to replace the installation-folder value to the new location.
Change the installation folder within BSManager in the settings
NOTE: Does not work if the original folder location does not exist anymore, since BSManager wants to transfer the original installation folder to the new location.
Problem
When a user manually moves the installation folder to another folder/disk, bs-manager still uses the default or installation-folder property in config.json.
Solution
If the installation folder (BSManager) does not exist on startup, prompt the user a modal to select either a new or existing installation folder. Default installation folder value should still be used on the prompt.
Workaround
Additional Context
Issue reported in https://discordapp.com/channels/1049624409276694588/1273029459544375459
Might be related to #481