-
Notifications
You must be signed in to change notification settings - Fork 406
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.12.2
What operating systems are you seeing the problem on?
Windows
Describe the bug
Modrinth App 0.12.0 overhauled the Content tab.
Each time a new Minecraft snapshot comes out it'll be added to the versions list immediately. But most of the time it isn't added to Modrinth itself, which will cause Modrinth to get stuck on the installing screen and doesn't allow you to edit it back. Basically softlocking the entire instance. On versions before 0.12.0 you were able to fix this issue by pressing the repair button. But by the looks of it, that button got removed. Now once you get stuck, you won't be able to get unstuck until the version is uploaded onto Modrinth's servers. And even then you cannot press the play button, you'd have to go over to the Worlds tab and select a world from there.
I believe that this might cause issues with people who are newer to the app and don't know how to get themselves out of it.
I would love it if the repair button gets added back in some way or another or that it'll only show the new version once it gets added to Modrinth itself. Just so some users won't freak out whenever their instance gets stuck :P
Steps to reproduce
- Wait until a new snapshot drops (most of the time they drop around 4PM CET)
- Reopen the launcher
- Go to any instance and click settings
- Go to installation and click edit
- Select the Show all versions setting in the list of game versions and select the version that just released
- Click save
Now you will be met with an error and your instance will be stuck until the version gets uploaded onto Modrinths servers, and the only way to get it unstuck after that is to go to the worlds tab and click play on any world there.
Expected behavior
What I think should happen is that the instance should switch the Minecraft version back to what it was prior to the change. This way it would be very user friendly and won't leave you locked out of your instance.
Another easy way to fix this is have the version only show up in the list once the version is ready to use in the app.
Additional context
No response