wow-api-combat

A reference guide to World of Warcraft Retail's combat-related programming interfaces, which add-ons use to read or display combat information. It covers damage, threat, crowd-control effects, combat text, sounds, restricted values, and spectator data, including changes in patch 12.0.0.

In plain words
What is it for?
Use it when building or updating damage meters, threat displays, combat alerts, combat-text features, or spectator tools for the Retail version of World of Warcraft.
Why use it?
It helps add-on developers avoid relying on combat-log functions that patch 12.0.0 no longer makes available to add-ons. It also shows which newer interfaces should be used instead.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/jburlison/wowaddonapiagents/wow-api-combat
Any agent
npx skills add JBurlison/WoWAddonAPIAgents --skill wow-api-combat
Clone the repo
git clone --depth 1 https://github.com/JBurlison/WoWAddonAPIAgents

Made for: Claude Code, Codex.

Per session 149 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,220 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00149 $0.03220
Opus 5 $0.00075 $0.01610
Sonnet 5 $0.00030 $0.00644
Haiku 4.5 $0.00015 $0.00322

Measured 3d ago against content hash 85ada9e46c20, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

wow-api-combat scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/skills/wow-api-combat/SKILL.md · 335 lines

How it starts

The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Combat API (Retail — Patch 12.0.0)

Comprehensive reference for all combat-related APIs in WoW Retail. Critical: The combat log system was fundamentally changed in 12.0.0. COMBAT_LOG_EVENT_UNFILTERED is no longer available to addons.

Source: https://warcraft.wiki.gg/wiki/World_of_Warcraft_API Current as of: Patch 12.0.0 (Build 65655) — January 28, 2026 Scope: Retail only.

CRITICAL: Combat Log Changes in 12.0.0

COMBAT_LOG_EVENT_UNFILTERED (CLEU) is NO LONGER available to addons.

  • CombatLogGetCurrentEventInfo() is unavailable to tainted (addon) code
  • The old COMBAT_LOG_EVENT event is also unavailable
  • Combat log chat tab messages are now KStrings (unparseable escape sequences)
  • Addons like damage meters must use C_DamageMeter or the built-in system
  • A new COMBAT_LOG_EVENT_INTERNAL_UNFILTERED exists but is restricted to Blizzard code

New Combat Log Events (Addon-Facing)

Event Description
COMBAT_LOG_MESSAGE Formatted combat log messages (display text only)
COMBAT_LOG_ENTRIES_CLEARED Combat log entries cleared
COMBAT_LOG_APPLY_FILTER_SETTINGS Filter settings changed
COMBAT_LOG_REFILTER_ENTRIES Entries need refiltering
COMBAT_LOG_MESSAGE_LIMIT_CHANGED Message limit changed

Scope

This skill covers:

  • Combat Log — New 12.0.0 combat log system, COMBAT_LOG_MESSAGE
  • C_DamageMeter — Built-in damage/healing meter system
  • Threat — UnitThreatSituation, UnitDetailedThreatSituation
  • C_LossOfControl — Loss of control tracking
  • C_CombatText — Floating combat text
  • C_CombatAudioAlert — Combat audio alert system (accessibility)
  • C_Secrets / C_CurveUtil / C_DurationUtil — Secret value handling for combat data
  • Encounter Events — ENCOUNTER_STATE_CHANGED, ENCOUNTER_WARNING, timeline events
  • Spectator/Commentator — C_Commentator for spectator mode

C_DamageMeter — Built-in Damage Meter

New in 12.0.0. Provides official damage/healing meter data without needing combat log parsing.

Read the full file on GitHub · 335 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 335 lines · 149 tokens per session scan A 85ada9e46c20

Subscribe to this mod's changes

wow-api-combat is a skill published in the GitHub repository JBurlison/WoWAddonAPIAgents (43 stars, last pushed 6mo ago), licensed MIT. It adds 149 tokens to every session and 3,220 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

particles

Use this skill when creating particle effects in Phaser 4. Covers ParticleEmitter, emission zones, death zones, particle properties, textures, gravity wells, and particle movement. Triggers on: particles, emitter, particle effect, explosion, fire, smoke.

phaserjs/phaser · 53 tokens

web-games

Web browser game development principles. Framework selection, WebGPU, optimization, PWA.

vudovn/ag-kit · 20 tokens

develop-web-game

Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.

netease-youdao/LobsterAI · 64 tokens

gameobject-component-destroy

Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.

IvanMurzak/Unity-MCP · 49 tokens

ship-web-games

Package, deploy, and verify a playable Three.js or web game. Use for release builds, asset delivery, private/public deployment, production smoke tests, browser proof, release notes, rollback readiness, and cleanup of temporary QA resources.

MengTo/Skills · 50 tokens

unity

Compile, test, and drive Unity for this repo's C# packages (unity/core, jint, quickjs, clearscript) and the two Unity projects (tests/, kitchen-sink/). Use when a change touches C# under unity/, when Unity test results are needed, when a rendering snapshot has to be checked or regenerated, or when the app has to be…

ReactUnity/core · 108 tokens