| name | packwiz-forge-1122-init |
| description | Initializes a packwiz modpack for Minecraft 1.12.2 Forge. Use when creating a new packwiz pack, reinitializing pack.toml, or setting pack metadata for a 1.12.2 Forge modpack. |
Packwiz Forge 1.12.2 Init
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 create packs from a dedicated pack directory, not .minecraft or a launcher instance directory.
Workflow
- The agent MUST confirm the target directory is the pack root.
- The agent SHOULD choose a Forge version explicitly and SHOULD prefer the version REQUIRED by the modpack.
- The agent MUST use
--forge-latest only when the user accepts whatever packwiz currently resolves for Minecraft 1.12.2.
- The agent SHOULD initialize non-interactively when values are known:
packwiz init --name "<pack name>" --author "<author>" --version "<pack version>" --mc-version 1.12.2 --modloader forge --forge-version "<forge version>"
- If recreating existing metadata is intentional, the agent MAY add
--reinit; otherwise the agent MUST NOT overwrite pack.toml.
- The agent MUST run
packwiz refresh, then inspect pack.toml for minecraft = "1.12.2" and forge = "<forge version>".
Notes
- The agent SHOULD NOT use
packwiz init -y unless every important option is supplied because it accepts defaults and can choose unwanted values.
- Generated files SHOULD be kept under version control:
pack.toml, index.toml, .pw.toml files, configs, scripts, and other non-ignored pack files.
