Please confirm the following.
What version of the Modrinth App are you using?
v0.8.1
What operating systems are you seeing the problem on?
Windows
Describe the bug
Modrinth asked me to update, so I did. Upon completion I tried to launch my custom modpack that I have been playing flawlessly for months, only to find that Minecraft had launched in Vanilla. Tried to restart both the app and my computer but it still did this. Then I uninstalled Modrinth and reinstalled it, and now the modpack is launching in Forge and whatnot, but closes without a crash log during launchup during the "Loading Bootstraps" phase. Not sure what to do here
Steps to reproduce
To reproduce the problem I would launch a custom modpack with the new Modrinth version. That's all I did
Expected behavior
I expected the modpack to launch as usual, fully functional via forge with the mods installed and functioning, as it had hours before I updated the app.
Additional context
No response
Please confirm the following.
What version of the Modrinth App are you using?
v0.8.1
What operating systems are you seeing the problem on?
Windows
Describe the bug
Modrinth asked me to update, so I did. Upon completion I tried to launch my custom modpack that I have been playing flawlessly for months, only to find that Minecraft had launched in Vanilla. Tried to restart both the app and my computer but it still did this. Then I uninstalled Modrinth and reinstalled it, and now the modpack is launching in Forge and whatnot, but closes without a crash log during launchup during the "Loading Bootstraps" phase. Not sure what to do here
Steps to reproduce
To reproduce the problem I would launch a custom modpack with the new Modrinth version. That's all I did
Expected behavior
I expected the modpack to launch as usual, fully functional via forge with the mods installed and functioning, as it had hours before I updated the app.
Additional context
No response