Skip to main content
Industry & SpecializedGame Production38 lines

World of Warcraft Addon Packaging

Package a World of Warcraft addon for named Retail and Classic clients. Validate TOC metadata, folder and manifest names, dependency and load ordering, saved variables, and release archive structure before installing or publishing.

Quick Summary10 lines
Build a release artifact from a known source revision and show that each supported client sees the intended addon's manifest and files. Start by documenting the client matrix and the install layout, then verify the archived bytes and run a clean-profile client smoke test when authorized.

## Key Points

- [Blizzard's Add-On Development Policy](https://eu.forums.blizzard.com/en/wow/t/wow-user-interface-add-on-development-policy/1642)
- [Client-exported Mainline Collections manifest](https://raw.githubusercontent.com/Gethe/wow-ui-source/live/Interface/AddOns/Blizzard_Collections/Blizzard_Collections_Mainline.toc)
- [Client-exported Classic Collections manifest](https://raw.githubusercontent.com/Gethe/wow-ui-source/live/Interface/AddOns/Blizzard_Collections/Blizzard_Collections_Classic.toc)
- [Client-exported AddOns events and API](https://raw.githubusercontent.com/Gethe/wow-ui-source/live/Interface/AddOns/Blizzard_APIDocumentationGenerated/AddOnsDocumentation.lua)
skilldb get game-production-skills/world-of-warcraft-addon-packagingFull skill: 38 lines
Paste into your CLAUDE.md or agent config

World of Warcraft Addon Packaging

Build a release artifact from a known source revision and show that each supported client sees the intended addon's manifest and files. Start by documenting the client matrix and the install layout, then verify the archived bytes and run a clean-profile client smoke test when authorized.

Establish a release matrix

For each target, record the product/flavor, game build, interface number, expected TOC file and required dependencies. Read the target client's interface number and verify its actual manifest selection rules using that client's exported source and a controlled load test. The current Retail client is not a proxy for every Classic branch. Blizzard's own flavor-specific manifests demonstrate different file and dependency lists, but internal manifest tags are not an entitlement for third-party addons.

Prefer an explicit manifest and release artifact per flavor when behavior, source files or declarations diverge. A combined archive can work if every intended client selects the right manifest and the packaged directory contains each declared file. Derive the release file list from an owned source revision. Record source revision, artifact version, client support and file inventory in the release receipt.

Build the archive and validate the load graph

Package an archive with a top-level addon directory that matches the expected manifest base name. Avoid an extra repository or ZIP wrapper folder. Verify the exact relative path of every TOC entry after resolving its separator convention and any XML includes. Compare path spelling and case against archive entries rather than relying on a case-insensitive workstation. Reject missing files, absolute paths, traversal, ambiguous case-only duplicates and accidental nested archives.

Make bootstrap and dependency order explicit. Load shared constants and initialization before consumers and UI templates before code that instantiates them. Mark mandatory dependencies as required, and guard optional integration calls when the optional addon is absent. Keep source code readable and honor the current Blizzard addon policy. Exclude local caches, credentials, game data dumps, user configuration and saved-variable files from the distribution.

If the addon uses SavedVariables, separate startup initialization from the migration of old persisted schemas. Match ADDON_LOADED to the addon's identity before migrating or defaulting its saved values. Declare whether data belongs to the account or character. Preserve valid prior settings, handle a version the code cannot safely read, and keep migration idempotent when a user reloads the UI.

Verify the same bytes the player will install

Run a static check over the candidate archive. Verify exact expected top-level folder and manifest, inventory membership, dependency declarations and every referenced file's relative path. Test two broken archives separately, one with an extra wrapper directory and one with an omitted or case-mismatched module. Each should fail before any installation. A local static success proves the packaging contract exercised, not addon load or behavior.

When authorized, extract a verified artifact to the proper AddOns directory of a test client, without touching production settings. Verify that the addon's manager shows the expected flavor and version, then log in and check first load, saved-variable migration, UI reload and missing optional dependencies. Keep an explicit unavailable result for untested clients. Do not use an out-of-date override as proof of supported compatibility. Keep the artifact hash and rollback path, and publish only with user authorization.

References and rights

Original SkillDB instructions under LicenseRef-SkillDB-Content. References were checked 2026-11-13 and used for technical verification.

Install this skill directly: skilldb add game-production-skills

Get CLI access →