This is a two-fold issue, and since both are so closely related I figured I'd toss them into a single report.
First off, when changing the path for instances you can't select a subfolder of the current folder path. I have no idea why this is a thing, as I had to redirect my instances a couple of times when first setting it up (in this case, I made a folder called FTB, then decided I wanted the path to be FTB\Instances before the app said "lol you can't do that" so I had to do a workaround just to select a sub-folder).
Secondly, the folder names for instances is just a random string of characters (which I assume to be some kind of back-end ID) rather than the modpack's name (I only use the CF Launcher, but assume most others do the same thing). Makes it annoying to easily modify files in a pack (configs, options.txt, adding mods, etc.)
(Also, I noticed that you can't type in a value for the game RAM - you have to use the sliders otherwise it won't save).
What is your suggestion?
This is a two-fold issue, and since both are so closely related I figured I'd toss them into a single report.
First off, when changing the path for instances you can't select a subfolder of the current folder path. I have no idea why this is a thing, as I had to redirect my instances a couple of times when first setting it up (in this case, I made a folder called
FTB, then decided I wanted the path to beFTB\Instancesbefore the app said "lol you can't do that" so I had to do a workaround just to select a sub-folder).Secondly, the folder names for instances is just a random string of characters (which I assume to be some kind of back-end ID) rather than the modpack's name (I only use the CF Launcher, but assume most others do the same thing). Makes it annoying to easily modify files in a pack (configs, options.txt, adding mods, etc.)
(Also, I noticed that you can't type in a value for the game RAM - you have to use the sliders otherwise it won't save).
Alternatives ideas
No response
Screenshots
No response
Additional information
No response