MineColonies

MineColonies

57M Downloads

[BUG] The latest release's version not matching previous version's structure

zyxkad opened this issue ยท 4 comments

commented

Is there an existing issue for this?

  • I have searched the existing issues

Are you using the latest MineColonies Version?

  • I am running the latest beta version of MineColonies for my Minecraft version.

Did you check on the Wiki? or ask on Discord?

  • I checked the MineColonies Wiki and made sure my issue is not covered there. Or I was sent from discord to open an issue here.

What were you playing at the time? Were you able to reproduce it in both settings?

  • Single Player
  • Multi Player

Minecraft Version

1.20.1

MineColonies Version

1.1.636

Structurize Version

1.1.636-1.20.1-BETA

Related Mods and their Versions

No response

Current Behavior

Previously the version structure is <minecraft_version>-<minecolonies_version>,
but now the versions swapped, it become <minecolonies_version>-<minecraft_version>

Is this on purpose? Since it breaks our mod dependencies.

[[dependencies.${mod_id}]]
modId = "minecolonies"
mandatory = false
versionRange = "[1.20.1-1.1.472-BETA,)"
ordering = "NONE"
side = "BOTH"

image

Expected Behavior

Mod (both older version and the latest version) should load correctly without error.

Reproduction Steps

  1. Define dependencies with older version
  2. Try load with the latest version
  3. Load failed

Logs

N/A

Anything else?

  • Add a thumbs-up to the bug report if you are also affected. This helps the bug report become more visible to the team and doesn't clutter the comments.
  • Add a comment if you have any insights or background information that isn't already part of the conversation.
commented

We're aware, this is being fixed with ldtteam/OperaPublicaCreator#13

commented

The file minecolonies-1.1.638-1.20.1-beta.jar at CurseForge still has this issue. I edited the mods.toml in the jar and that seemed to work.

commented

Maybe minecolonies can temperatory remove the release until fixed.

commented

We're currently checking what we want to do to resolve this, we recommend not upgrading past 1.1.629 for now