mmc-export 2.4.2

Export MMC modpack to other modpack formats

MultiMC advanced exporter

Since MultiMC export features are very limited, I created a script that solves this problem, with this script you can export MultiMC pack to any popular format (e.g. curseforge, modrinth, packwiz). MultiMC forks which didn't changed export format much also supported, PolyMC support approved.

Features

• Support conversion to:
  • CurseForge
  • Modrinth
  • packwiz
• Detects downloadable resourcepacks and shaders
• Supports github parsing¹
• Loose modrinth search
• User friendly toml config
• Multiple output formats at once

---

GitHub rate limits

GitHub has limited requests per hour (up to 60), this means that if you have more than 60 mods, the rest will be excluded from github search. If you authenticate with GitHub using mmc-export gh-login, the limit will be removed and requests will be faster. You can always log out with mmc-export gh-logout.

If you don't want to use github search by some reason, you can specify --exclude-providers GitHub as argument.

How to Use

mmc-export -i modpack.zip -c config.toml -f Modrinth packwiz -o converted_modpacks

It's recommended to fill config at least with basic info like name and version, some launchers can fail import if these values are empty.

Sub-commands

gh-login - to authrize GitHub
gh-logout - to get info how to deauthorize GitHub

purge-cache - to purge cache. Available arguments:

--web: to delete requests cache and downloaded mods
--files: to delete hashes cache
--all: equivalent to --web --files, deletes all cache (default)

Syntax

mmc-export [sub-command] [-h] [-c CONFIG] -i INPUT -f FORMAT [-o OUTPUT] [-v VERSION] [--modrinth-search SEARCH_TYPE] [--exclude-providers PROVIDERS]

Explanation

-h --help: prints help
-i --input: path to modpack, must be zip file exported from MultiMC.
-c --config: path to config, used to fill the gaps like description or losted mods.
-f --format: output formats, must be separated by spaces.
-o --output: directory where converted zip files will be stored.
-v --version: specify modpack version, will be overriden by config's value if exists
--modrinth-search: modrinth search accuracy
--exclude-providers: providers you wish to exclude from search

All paths can be relative to current working directory or absolute.

--format options (case-sensitive):

• CurseForge
• Modrinth
• packwiz
• Intermediate (only for debugging, may contain sensitive data like username)

--exclude-providers options (case-sensitive):

• CurseForge
• Modrinth
• GitHub

--modrinth-search options:

• exact - by hash (default)
• accurate - by hash or slug
• loose - by hash, slug or long name

The example for the optional --config file can be found here.

For example, if the script says

No config entry found for resource: ModName

Then you should add one of the following entries to the end of the config:

Specify source URL

[[Resource]]
name = "ModName"
filename = "the_name_of_the.jar" 
url = "https://cdn.modrinth.com/data/abcdefg/versions/1.0.0/the_name_of_the.jar"

Hide the warning

[[Resource]]
name = "ModName"
filename = "the_name_of_the.jar" 
action = "ignore"

Explicitly move to overrides

[[Resource]]
name = "ModName"
filename = "the_name_of_the.jar" 
action = "override"

Delete the file altogether

[[Resource]]
name = "ModName"
filename = "the_name_of_the.jar" 
action = "remove"

To make mod optional you can append

optional = true - to any of above

How to Install / Update

pip install -U mmc-export