Closed jhymni closed 2 months ago
This isn't something we can fix. If the drive is no longer there, there isn't anything to migrate. You would need to manually modify the instanceLocation
field inside the settings.json
file.
This is definitely an edge case...
Regardless, I did note that it was not clear that the instance location setting was a migration system and not a static input field. To resolve this, I've improved the wording.
What Operating System
Windows 10
Debug Code
FTB-DBGAVEQIQECEB
Describe the bug
The debug code is pointless seeing as I already fixed this issue myself, though I did have to delete the .ftba folder to reset the location. The instance location was on the D: disk, which no longer exists.
Steps to reproduce
Expected behaviour
It should recognize that the disk/location is no longer reachable and establish a new location from scratch
Screenshots
No response
Additional information
Niche problem I guess