Skip to main content
Industry & SpecializedGame Design38 lines

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.

Quick Summary9 lines
Produce an addon-owned 3D preview with a known input, a stable camera and a visible fallback for unsupported appearances. Treat a displayed actor as a view. Changes made to preview state must never be mistaken for changes to the character, equipment or account.

## 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 ModelScene frame methods](https://raw.githubusercontent.com/Gethe/wow-ui-source/live/Interface/AddOns/Blizzard_APIDocumentationGenerated/FrameAPIModelSceneFrameDocumentation.lua)
- [Client-exported ModelScene mixin](https://raw.githubusercontent.com/Gethe/wow-ui-source/live/Interface/AddOns/Blizzard_SharedXML/ModelSceneMixin.lua)
skilldb get game-design-skills/world-of-warcraft-addon-model-scenesFull skill: 38 lines
Paste into your CLAUDE.md or agent config

World of Warcraft Addon Model Scenes

Produce an addon-owned 3D preview with a known input, a stable camera and a visible fallback for unsupported appearances. Treat a displayed actor as a view. Changes made to preview state must never be mistaken for changes to the character, equipment or account.

Select and verify the model surface

Record the client product, build and exact preview task. A player model, creature display and a character customization editor do not have the same API. Verify the model type, templates and actor methods in matching client-exported Blizzard UI code. Distinguish native frame or actor methods from functions supplied by Blizzard's mixins. For example, the existence of ModelSceneMixin:SetFromModelSceneID in exported code does not guarantee that a plain frame has that mixin, an appropriate template or access to the same static scene IDs.

Start with a documented model input and one actor in an addon-owned frame. If the intended client exposes a compatible scene/template, verify its actor and camera setup and how the base client retrieves actors. If there is no supported model path for that client or appearance, use an icon, label or other static preview and say what could not be rendered. Do not substitute a different race, equipment model or appearance silently.

Separate the actor, camera and request lifecycles

Track the preview request identity, actor and camera separately. Reset or replace an old actor before binding a new selection. If the chosen path reports model readiness asynchronously, discard callbacks from earlier selections and avoid fitting a camera against an unloaded or empty model. Reuse the scene where supported and clean up in the order its template expects. On hide or close, detach update handlers, stop drag and animation, and release owned actors/cameras if using pooling.

Adjust the camera independently of model identity. Use framing that suits the actor bounds or a documented default; verify that narrow and wide frame ratios keep the focal feature visible. For an inspectable model, offer bounded rotate/zoom and reset controls, with changes based on local input. Do not drive the actor from live restricted game state. Keep controls and fit calculations away from code paths that mutate gear, appearance or the world.

Do not claim full character customization support based on successfully rendering the player. Distinguish the current unit's display from a documented preview-only outfit or display ID. Check allowed methods for each target client. If an appearance is unsupported, inaccessible, or secret, show a fallback without logging or inferring the restricted value. Do not use Blizzard glue/front-end code as evidence that an in-game third-party addon has the same capabilities.

Test visible correctness and state cleanup

Exercise a known supported display, an unavailable one, and a rapid selection change while the first model is loading. The old result must never replace the new preview. Hide and reopen the panel, then test drag release outside the frame and zoom at both limits. Test at two aspect ratios and two UI scales, recording actor identity, camera mode, clipping and fallback states. Verify that replacing or clearing the view does not change character state.

The acceptance record should name the tested client and exact scene/template. A test double can confirm stale-request rejection and cleanup logic. Actual scene asset availability, camera transforms, client restrictions and appearance fidelity need a run in the declared client.

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-design-skills

Get CLI access →

Related Skills

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.

Game Design•38L

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 Design•163L

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 Design•170L

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 Design•169L

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 Design•168L

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•201L