| name | packwiz-pack-maintenance |
| description | Maintains an existing packwiz Minecraft 1.12.2 Forge modpack. Use for refresh, list, update, remove, pin, unpin, acceptable-game-versions, and routine metadata verification. |
Packwiz Pack Maintenance
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 run commands from the pack root containing pack.toml.
Common Commands
packwiz refresh
packwiz list -v
packwiz update <metadata-name>
packwiz update --all
packwiz remove <metadata-name>
packwiz pin <metadata-name>
packwiz unpin <metadata-name>
The agent MUST use the metadata name from packwiz list, usually the .pw.toml filename without extension.
Workflow
- The agent SHOULD run
packwiz list -v before changes when the current names or versions are needed.
- After manual file edits, additions, removals, or config/script changes, the agent MUST run
packwiz refresh.
- For 1.12.2 packs, the agent SHOULD update one mod at a time when compatibility risk is high.
- The agent MUST use
packwiz update --all only when the user wants broad updates.
- The agent SHOULD pin files that MUST NOT auto-update:
packwiz pin <metadata-name>.
- If packwiz needs adjacent Minecraft versions for legacy 1.12.2 files, the agent SHOULD set them explicitly:
packwiz settings acceptable-versions "1.12,1.12.1"
packwiz settings acceptable-versions --add "<version>"
packwiz settings acceptable-versions --remove "<version>"
Guardrails
- The agent MUST NOT change
minecraft = "1.12.2" to satisfy a single mod unless the user requests a pack migration.
remove, pin, and unpin MUST receive exactly one metadata name.
- The agent SHOULD use
packwiz refresh --build only for no-internal-hashes distribution workflows.