Skip to content

XMCL displays Modrinth "[Let's Do] WilderNature" file under "[Let's Do] Beachparty" as extra version #1318

@LauriLepik

Description

@LauriLepik

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.

Image Image

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

  1. Create/open an instance on Minecraft 1.21.1 with NeoForge.
  2. Open "Install" Mods browser, search for "[Let’s Do] Beachparty" and click install.
  3. Search for "[Let’s Do] WilderNature" and click Install.
  4. Return to the Beachparty details page and open the “Selected Version” dropdown.
  5. 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions