| name | packwiz-curseforge-export |
| description | Exports a packwiz Minecraft 1.12.2 Forge modpack to a CurseForge-compatible zip. Use when preparing a CurseForge upload or launcher import package. |
Packwiz CurseForge Export
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 .zip exports. The CurseForge format does not fully support side-specific packs or OPTIONAL mods.
Workflow
- The agent MUST work from the pack root containing
pack.toml.
- The agent SHOULD ensure
.packwizignore excludes files that SHOULD NOT be included, such as local tools, build artifacts, and previous export zips.
- The agent MUST run a verification pass:
packwiz refresh
packwiz list -v
- The agent MUST export for the intended side:
packwiz curseforge export --side client --output "<pack-name>.zip"
packwiz curseforge export --side server --output "<pack-name>-server.zip"
- The agent MUST inspect command output for non-CurseForge files. CurseForge MAY require manual approval for bundled non-CurseForge JARs.
Guardrails
- The default export side is
client.
- Valid sides MUST be one of
client, server, and both.
- The agent SHOULD prefer CurseForge metadata for CurseForge-hosted mods before exporting and SHOULD use
detect-mods or packwiz curseforge add to replace local JARs with metadata where possible.
