World of Warcraft Addon Game Events and Data
Build a World of Warcraft Lua addon that reads supported quest, bag, item, inventory, and map APIs and plays optional user-configured sounds. Use for a version-specific, read-only player panel or tooltip with reliable refresh and missing-data behavior.
Implement a panel that reacts to player state through documented client APIs. Start with one narrow feature, such as a local watch list that shows quest state and whether a selected item is available in visible bags. Keep data retrieval and state updates separate from the frames that render the result. ## Key Points - [Blizzard's Add-On Development Policy](https://eu.forums.blizzard.com/en/wow/t/wow-user-interface-add-on-development-policy/1642) - [Blizzard on addon restrictions and secret values](https://worldofwarcraft.blizzard.com/en-us/news/24246290/combat-philosophy-and-addon-disarmament-in-midnight) - [Client-exported quest log API documentation](https://raw.githubusercontent.com/Gethe/wow-ui-source/live/Interface/AddOns/Blizzard_APIDocumentationGenerated/QuestLogDocumentation.lua) - [Client-exported container API documentation](https://raw.githubusercontent.com/Gethe/wow-ui-source/live/Interface/AddOns/Blizzard_APIDocumentationGenerated/ContainerDocumentation.lua) - [Client-exported map API documentation](https://raw.githubusercontent.com/Gethe/wow-ui-source/live/Interface/AddOns/Blizzard_APIDocumentationGenerated/MapDocumentation.lua) - [Client-exported sound API documentation](https://raw.githubusercontent.com/Gethe/wow-ui-source/live/Interface/AddOns/Blizzard_APIDocumentationGenerated/SoundDocumentation.lua)
skilldb get game-design-skills/world-of-warcraft-addon-game-eventsFull skill: 40 linesWorld of Warcraft Addon Game Events and Data
Implement a panel that reacts to player state through documented client APIs. Start with one narrow feature, such as a local watch list that shows quest state and whether a selected item is available in visible bags. Keep data retrieval and state updates separate from the frames that render the result.
Map capabilities and define state
Record the actual Retail or Classic product, client build, feature and exact event arguments. Consult matching client-exported generated API documentation and the client code that consumes it. The Retail namespaces C_QuestLog and C_Container are useful starting points. Read the declared return structure, nilability and restrictions instead of assuming older global-function tuples or Classic names transfer unchanged.
Write down when the selected source is valid. Record a quest by quest ID, not the quest-log index, because sorting or filtering can move entries. A bag location is a current address, so re-read the slot before rendering it after a change. If an item detail may load asynchronously, retain the exact pending record identity and only apply a completion to the same request or current selection. Do not infer successful completion from a vanished quest or an empty item response alone.
Give the view explicit ready, pending, unavailable and unsupported states. A missing or restricted map position is not the origin. Check the current map context and use the coordinate space returned for that map. Hide a pin with unavailable coordinates or provide a plain-text fallback. Explain when the player's current bags are in scope but bank or other account containers are unavailable.
Refresh without duplicate effects
Register only events that change the feature. Route supported events to invalidate the relevant quest, bags or map slice. Coalesce event bursts into one bounded refresh on the client's supported scheduling mechanism. On refresh, read the available source, compare the prior and current state by stable ID and update only changed rows. On login or a UI reload, seed a baseline before detecting transitions. A repeated notification event or a refresh after login should not replay a completion cue.
For a user-requested audio cue, use a sound identifier or asset and channel the target client and policy permit. Provide a local preference to turn it off. Play at most one cue per observed qualifying transition within its intended scope. Rendering, tab changes and mouse hover must not independently replay it. Keep sound behavior separate from protected player actions and automatic quest, inventory or combat manipulation.
Observe restrictions and test the transitions
Treat secret or restricted values as unavailable for addon-side reasoning. Do not copy them into cache keys, persist them, print them, derive state by comparing them or attempt to recover them through an alternate event. Use only documented supported display behavior for such a value, or omit the feature in that context. Limit stored data to what's needed for the player's preference and avoid logging unrelated personal data.
Simulate a burst of quest and bag updates, moving the selected item across slots and completing a delayed detail request after changing selection. Require one refresh per scheduled invalidation group and no display of stale data for the new selection. Verify that one confirmed transition plays at most one cue and replaying the same event after reload is silent. Exercise missing map data and an absent namespace on a supported variant with the documented fallback. Local event or state tests verify adapter behavior; only the matching WoW clients can verify actual event delivery, restrictions, visual output and audio.
References and rights
- Blizzard's Add-On Development Policy
- Blizzard on addon restrictions and secret values
- Client-exported quest log API documentation
- Client-exported container API documentation
- Client-exported map API documentation
- Client-exported sound API documentation
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-design-skills
Related Skills
World of Warcraft Addon Model Scenes
Build a World of Warcraft addon model preview using supported ModelScene actors and cameras. Use to preview a player or supported display, inspect equipment and character appearance, or troubleshoot blank, clipped, or stale 3D previews on a declared client.
World of Warcraft Addon UI
Build and test a World of Warcraft Lua or FrameXML addon interface with widget input, scrollbars, tooltips, recycled rows, and animation. Use for cosmetic panels, settings, and player-driven controls on a specified Retail or Classic client.
Dialogue Systems
Trigger when building game dialogue systems, branching conversation trees, bark systems, or cinematic dialogue tooling. Use for dialogue data formats, conditional branching, localization pipelines, lip sync integration, or building author-friendly dialogue editors and runtime presentation layers.
Game Accessibility
Trigger when designing games for accessibility, implementing accommodations for visual, auditory, motor, or cognitive disabilities, or evaluating a game's inclusivity. Use for colorblind modes, remappable controls, subtitle systems, difficulty assists, screen reader support, or making a game playable by the widest possible audience without compromising core design.
Game Analytics Liveops
Trigger when designing game analytics systems, live operations strategies, A/B testing frameworks, or player behavior telemetry. Use for retention metrics, funnel analysis, cohort tracking, event schemas, feature flagging, seasonal content cadence, or using data to improve a live game without losing design vision.
Game Audio Design
Trigger when designing or implementing game audio, including sound effects, adaptive music, spatial audio, voice implementation, or audio middleware integration. Use for FMOD, Wwise, audio occlusion, dynamic mixing, sound design for gameplay feedback, or making a game sound as good as it plays.