-
Notifications
You must be signed in to change notification settings - Fork 347
Open
Labels
appRelates to Modrinth AppRelates to Modrinth App
Description
Please confirm the following.
- I checked the existing issues for duplicate problems
- I have tried resolving the issue using the support portal
- I have ensured my Modrinth App installation is up to date
What version of the Modrinth App are you using?
0.10.9
What operating systems are you seeing the problem on?
Windows
Describe the bug
My installation of Prism is located at E:/Documents/Minecraft/Prism, but my instances are located at E:/Documents/Minecraft/Instances. I configured this in Prism, and this path is stored as the InstanceDir value in prismlauncher.cfg.
When I attempt to import an instance from Prism Launcher, the app attempts to access the instance from E:/Documents/Minecraft/Prism/instances (the default location), ignoring my configuration, and resulting in an import error.
Steps to reproduce
- Set up the Prism Launcher to use a non-default Instances folder (Settings -> Launcher -> Features -> Folders -> Instances, change the path)
- Use Modrinth app to attempt to import the custom instance.
Expected behavior
The Modrinth app should check the user's configuration properly, and successfully store the value.
Additional context
I can confirm that reconfiguring Prism to use the default instances folder, then copying my instance there, successfully prevents the reported error.

Metadata
Metadata
Assignees
Labels
appRelates to Modrinth AppRelates to Modrinth App