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.
Build one addon-owned panel that works in a declared WoW client and has a testable input and display contract. Start with a harmless settings or collection panel, so its behavior can be checked without triggering combat or changing the player's items. ## 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 frame API documentation](https://raw.githubusercontent.com/Gethe/wow-ui-source/live/Interface/AddOns/Blizzard_APIDocumentationGenerated/SimpleFrameAPIDocumentation.lua) - [Client-exported ScrollBox list view implementation](https://raw.githubusercontent.com/Gethe/wow-ui-source/live/Interface/AddOns/Blizzard_SharedXML/Shared/Scroll/ScrollBoxListView.lua)
skilldb get game-design-skills/world-of-warcraft-addon-uiFull skill: 38 linesWorld of Warcraft Addon UI
Build one addon-owned panel that works in a declared WoW client and has a testable input and display contract. Start with a harmless settings or collection panel, so its behavior can be checked without triggering combat or changing the player's items.
Verify the client contract
Record the client product, version, build and interface number, and confirm which Retail or Classic variants the user supports. Use the matching client-exported Blizzard UI source as primary evidence. Inspect the generated API documentation for the frame methods and their restrictions, and inspect the actual template and call sites for the chosen client. A symbol's presence in Retail or another Classic variant does not establish compatibility.
Choose a small set of controls for the first working panel. Create or declare an owned parent frame with explicit anchors. Keep view state, selection and scroll position separate from frame objects. Use named IDs for options and items, and keep one clear owner for update scheduling and UI teardown. Prefer Lua for straightforward composition. Use XML where named reusable templates or existing client conventions make it easier to verify inheritance and file ordering.
Implement input, scrolling and feedback
Route clicks to the action for the currently bound record. If a row is pooled, install its handler once and have the handler read its current row binding, or replace and remove the handler as part of binding. On release, clear or reset tooltip state, selections, references, highlight and transient animation. After filtering or resorting, retain selection by record ID if it is still present. Clamp scroll position and test content that exactly fills the viewport as well as content that overflows.
Use the supported scroll mechanism for the client. For a ScrollBox-backed list, inspect the view's element initializer and the factory and data provider lifecycle before choosing templates and scroll behavior. A fallback for a different client can be a simpler bounded list. Avoid invisible capture layers that swallow mouse wheel or click events. Test modifier keys, mouse down versus mouse up semantics and interaction when a row is disabled.
Set tooltip ownership to the active control and clear it when the control is left, hidden, recycled or loses its data. Keep essential labels visible without hover. On drag start, save the panel's allowed movement state and terminate movement on release or hide; check positioning after UI-scale or resolution changes. Trigger short animation on state transitions and stop or reset it during recycle. Avoid persistent per-frame work for a static panel.
Respect UI restrictions and verify failure paths
Treat protected actions, combat lockdown, and secret values as separate boundaries. Keep the panel's ordinary updates on addon-owned, unprotected UI. If modifying a protected frame is essential, verify the exact supported mechanism and perform only changes the client permits. A configuration update blocked in combat can be shown as pending and revalidated after combat. Do not derive, compare, log, serialize or transmit secret values as a workaround. Use only an explicitly supported display path, or omit the affected UI.
Test 100 records with a small viewport and reuse a visible row after changing the selection and sort. Verify that its tooltip, click and highlight match its current record ID. Hide and reopen while a tooltip or animation is active. Try the declared keyboard or focus path, UI scale and narrow window. For the restricted-path control, ensure a denied operation does not move or alter a protected control, leak data or cause a combat-blocked action. A Lua harness can verify view-state rules, but focus, rendering, taint and combat behavior require the actual supported client.
References and rights
- Blizzard's Add-On Development Policy
- Blizzard on addon restrictions and secret values
- Client-exported frame API documentation
- Client-exported ScrollBox list view implementation
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
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.
Game Balancing
Trigger when balancing game economies, tuning difficulty, adjusting competitive balance, or iterating on progression pacing. Use when the user asks about mathematical models for balance, playtesting-driven tuning, economy simulation, DPS calculations, matchmaking, or how to make a game feel fair without being easy.
Game Design Philosophy
Adaptive game design philosophy coach that learns your design instincts and helps you think more clearly about mechanics, player experience, systems, and what makes games meaningful. Covers core loops, progression, feedback, narrative, player psychology, scope, and aesthetics.