api settings system

Use for any selected combination of Retail, Forever, and Classic progression. First resolve the target and pinned source with wow-client-targets.

Target-specific decisions

For UI input and controller-facing settings, follow controller support. Assess controller reachability and operation, preserve user bindings and CVars, and verify client-specific settings APIs before offering an opt-in change.

For a window that cannot acquire controller focus or a Game Menu-style focus shortcut, use focus acquisition and diagnostics. Resolve the actual action/context and distinguish an unbound action from an unavailable query before installing temporary bindings or rendering a hint.

For visible settings-panel changes, use the mock-up choice and UIForever workflow before production implementation and during visual testing.

Follow visual fidelity when an accepted panel design exists. Preserve its appearance while keeping real settings controls functional; verify the rendered result instead of substituting a default settings layout silently.

Verify loaded Settings panel registration APIs, CVars and their permitted scopes, and client/build detection. If an integration is unavailable, use a verified custom configuration UI rather than guessing a legacy replacement.

Read the relevant row in compatibility guidance. Verify only the APIs needed for this task, using commit-pinned definitions and loaded client code. Missing evidence means unknown, not supported or removed. When offline, disclose the snapshot version/date and unresolved behavior.

Detailed lookup material

Use the pinned source schemas for complete generated contracts in this domain, including typed arguments, returns, event payloads and restrictions. Query only the needed symbols. Source declarations leave loading, runtime behavior and addon permission unresolved unless separately verified.

Start with current settings contracts and integration for Settings registration, CVars and input/media boundaries. For Forever presets, Hardcore and game-mode rules, use Forever GameRules; login-screen setters are not automatically addon APIs.

The historical Retail baseline retains the original API listings and examples. It is a research aid, not current or cross-client verification. Open only relevant supporting references:

• CVARS OVERVIEW

For implementation and release validation, use wow-addon-development.