Modsman v0.32.1

• Improve download error reporting
• Increase timeouts on downloads

Modsman v0.32.0

• Fixed jar matcher not setting the right path when running modsman-cli discover, causing old files to not be deleted when updating mods
• Added release type support. This allows you to direct the jar selection system whether to allow beta and alpha mod versions. Default is release-only; use the -r beta or -r alpha during init or edit the config after init to change it. Beta includes release, and alpha includes all three.
• Fixed exception when trying to initialize a directory that already contains a .modlist.json

Modsman v0.31.0

• Created modsman-packutil, a utility for inflating MultiMC modpacks on first run with modsman
• Fixed a minor typo in the CLI error message

Modsman v0.30.1

Make init version flags (-X and -R) optional

Modsman v0.30.0

This version is not fully compatible with modlists from 0.21.0 and below! The upgrade is pretty easy, see the release notes for version 0.22.0. Or just perform an init and discover.

• Added mod version pinning
• Added game version exclusions
• Added Java 8 support (probably)
• Sacrificed the GUI to the red-diff gods

To create a new modlist that allows any 1.15(.x) mod EXCEPT mods tagged with Forge or Rift, run:

modsman-cli init -R 1.15 -X Forge -X Rift

To update an existing modlist, update your modlist config block to something like this:

{
  "config": {
    "required_game_versions": [
      "1.15"
    ],
    "excluded_game_versions": [
      "Forge",
      "Rift"
    ]
  },
  "mods": []
}

You can "pin" a mod to block it from being upgraded. This is useful if some mods don't play well with auto-upgrading due to mistagging on Curse. Mod pinning example:

modsman-cli discover *.jar
modsman-cli pin 306770
modsman-cli upgrade-all # upgrades all mods except Patchouli
modsman-cli unpin 306770
modsman-cli upgrade-all # upgrades all mods including Patchouli

Modsman v0.22.0

Now supports multiple game version tags, so you can specify both 1.15.2 and Fabric. This should fix the issue where it would auto-upgrade Fabric mods to Forge versions in cases where the CF project was shared.

For a new modlist: modsman-cli init -M 1.15 -M Fabric

To update your old modlist, replace

"config": {
  "game_version": "1.15"
}

with

"config": {
  "required_game_versions": ["1.15", "Fabric"]
}

in the config block of your .modlist.json

As before, game version maching uses substrings, so "1.15" in a modlist matches "1.15.2" on curseforge.

Modsman v0.21.0

no changes