-
-
Notifications
You must be signed in to change notification settings - Fork 164
Open
Labels
Description
Is there an existing issue for this?
- I have searched the existing issues
Launcher Version
v0.54.3
Operating System
Windows
Architecture
x64
Current Behavior
When installing [Let’s Do] WilderNature via the Modrinth integration, it does not appear as a separate installed entry; instead, the WilderNature jar (letsdo-wildernature-neoforge-1.1.4.jar) shows up inside the [Let’s Do] Beachparty mod page/version dropdown as an additional file/version.
Expected Behavior
Installing [Let’s Do] WilderNature should add it as its own mod entry (or at minimum keep its version list attached to the WilderNature project), not as a “version” of Beachparty.
Steps To Reproduce
- Create/open an instance on Minecraft 1.21.1 with NeoForge.
- Open "Install" Mods browser, search for "[Let’s Do] Beachparty" and click install.
- Search for "[Let’s Do] WilderNature" and click Install.
- Return to the Beachparty details page and open the “Selected Version” dropdown.
- Observe that letsdo-wildernature-neoforge-1.1.4.jar appears listed there alongside Beachparty versions.
Anything else?
The WilderNature jar is present in the instance mods/ folder, so this appears to be a UI/association bug rather than a failed download. Im wondering what is causing this and if it could be also affecting other mods as well.
Reactions are currently unavailable