| name | packwiz-curseforge-import |
| description | Imports an existing CurseForge Minecraft modpack into packwiz. Use when converting a CurseForge zip, manifest.json, minecraftinstance.json, or installed CurseForge instance to packwiz metadata for a 1.12.2 Forge pack. |
Packwiz CurseForge Import
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL are to be interpreted as described in RFC 2119.
Prerequisite
If packwiz is not available on PATH, the agent MUST install it manually from the GitHub Actions artifacts in the packwiz repository: https://github.com/packwiz/packwiz. The agent MUST verify availability with packwiz --help before running these commands.
The agent MUST use this for CurseForge packs only. Importing MAY overwrite files in the current pack directory.
Workflow
- The agent SHOULD work in an empty pack directory or MUST ensure the current worktree is safe to modify.
- The agent MUST import the pack:
packwiz curseforge import "<path-to-modpack.zip-or-metadata>"
- The agent MUST verify the imported loader and game version in
pack.toml; for this workflow they SHOULD be Minecraft 1.12.2 and Forge.
- The agent MUST run
packwiz refresh.
- The agent SHOULD run
packwiz list -v and check for missing or unexpected mods.
Inputs
- The input SHOULD be a CurseForge exported
.zip containing manifest.json or minecraftinstance.json.
- The input MAY be a standalone
manifest.json or minecraftinstance.json.
- On Windows, an installed CurseForge instance name MAY resolve if packwiz can find the CurseForge directory.
Boundaries
- The agent MUST NOT use this for Modrinth
.mrpack files.
- For non-CurseForge local JARs after import, the agent SHOULD keep them as internal files or add them with
packwiz url add if they have stable direct downloads.