# Building MPQ Patches for WoW 1.12.1 Reference for packaging files (addons, FrameXML overrides, art) into an MPQ patch archive that vanilla 1.12 picks up at boot. Captured because the MPQEditor docs are sparse, the script syntax is non-obvious from the GUI, and there's a 1.12 patch-MPQ naming constraint that's easy to miss. ## When this matters Useful when you want files to: - **Auto-load before user addons** — engine reads MPQs in `\Data\` early in boot, alongside FrameXML. Anything in `Interface\AddOns\\` inside an MPQ enumerates just like a filesystem-resident addon, but loads earlier than addons living in `Interface\AddOns\` on disk. - **Be tamper-resistant** — users can't accidentally disable an MPQ-resident addon from the in-game addon list (it's not in the filesystem `Interface\AddOns\` they can browse to). - **Override engine UI** — drop `Interface\FrameXML\.lua` / `Interface\FrameXML\.xml` files to add or modify FrameXML. This is how the 3.3.5 reference for `/dump`, `/framestack`, `/etrace` lives in `ChatFrame.lua` — it could be replicated here via a small `Interface\FrameXML\AddedSlashCommands.xml` MPQ insert that calls `UIParentLoadAddOn` for backported tools. Confirmed empirically (1.12.1): | Test | Result | |-----------------------------------------|--------| | Plain (non-Blizzard_-prefixed) addon in MPQ, auto-discovered | ✅ engine sees it via enum | | Plain addon in MPQ, auto-loads on login | ✅ | | `Blizzard_*` addon in MPQ, no `.toc.sig` | ❌ engine refuses (signature check is name-based, not location-based) | | `Blizzard_*` addon on filesystem, no `.toc.sig` | ❌ same — refusal applies regardless of MPQ vs filesystem | So MPQ residency is no help for `Blizzard_*` names — those need a separate signature-bypass approach (see `mpq-test/HANDOFF.md` for the hook target). ## Tooling We use Ladik's **MPQ Editor** (`MPQEditor.exe`), which ships with a MoPaQ 2000 script interpreter. Run with `/console