api combat
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
Verify addon access to combat logs, events, damage-meter data, threat and loss-of-control fields separately. Read security annotations and preserve opaque values. Retail 12.0 notes do not establish Forever or Classic restrictions.
For damage meters or Forever swing timers, start with reviewed contracts: exact functions, payloads, structures, enums, client loading and access annotations. Runtime acceptance remains separate.
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.
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:
For implementation and release validation, use wow-addon-development.


