Warcraft Logs is tightening its API as AI addons flood WoW: Forever

World of Warcraft: Forever goes live at 23:00 UTC on November 4, Blizzard says — about 32 hours after this is published. It arrives as a third permanent version of Azeroth, with more than 1,000 new quests and its first level-60 raids on December 9, per Blizzard's launch announcement. It also arrives with a problem no WoW launch has had before: the addon ecosystem around it is already full of AI-generated clones of other people's work.

The flood arrived before the servers

Joseph Cox reported for 404 Media on Tuesday that the Forever subreddits are already overrun with AI-written addons that copy long-time developers' work, and that Warcraft Logs — the site raiders have used for a decade to record and analyse their fights — is changing its API in response, according to 404 Media.

The numbers Warcraft Logs chief executive Sildri Silentcrest gave Cox are the story. Two years ago roughly 200 developers used the site's free API and two to four of them were abusive. Today it is 10,000 developers and about 1,000 abusive. Commercial projects are supposed to ask permission first, and the queue has become a daily event. "One new World of Warcraft analysis company every day!" Silentcrest said. "It's hard to keep up."

Why a launch is the best job an LLM has ever been given

Every Forever addon has to be ported, because it is not the client anyone's addon was written for. Patch 1.60.1 introduces a distinct game type — the TOC interface number moves to 16001, and addon authors get an AllowLoadGameType: forever directive so one package can serve both clients, documented on the Warcraft Wiki. Porting is mechanical work: adjust the interface number, chase the functions Blizzard changed, fix the SavedVariables that stopped loading in early beta builds. That is exactly the shape of task a language model is good at, and it is why the barrier between "player" and "addon author" collapsed in about six weeks.

There is already a tool that closes the loop inside the game. Witchcraft is an open-source addon that runs Claude Code and Codex in a terminal panel over the client, with a local server that feeds the model character context, quest state and Lua error output, per its GitHub repository. It has 13 stars, an MIT licence, and a 0.1.1 release prepared for November 4. You no longer need a second monitor to vibe-code an addon; you need one window.

The point is not that AI writes bad Lua. The point is that the cost of producing a plausible addon — one that installs, loads and mostly works — has fallen to roughly zero, while the cost of checking whether it is any good, or stolen, has not moved at all. That is the same economic shape as the AI-slop problem generally, which we laid out in AI 101 — What is AI slop?: the bottleneck was never production, it was the person who used to stand between production and publication.

Warcraft Logs is pricing accountability, not code

The change itself is undramatic on paper. Warcraft Logs is narrowing its API toward tools that help a player understand their own performance — Cox's example from the company is an addon that explains why you died to a boss — and away from sites that scrape the log database and republish summary statistics on their own domain. It is also adding a paid commercial key so that developers earning money on top of the data contribute to the infrastructure.

The commercial-approval rule is not new. Archon's API documentation, last updated in December 2025, already tells developers that anyone "earning revenue through ads, subscriptions, or selling data" must obtain prior approval, per the API docs. What changed is the enforcement posture: a clause nobody read became a product, and a free API became a metered one. Note the honesty in Silentcrest's framing — the complaint is not that the new tools are bad. It is that "policing API use has become a struggle" for a small team, and the cheapest way to police a thing is to make it cost money.

We have watched this exact move twice this autumn. Google paused an open-source bug bounty programme when AI-generated junk reports made triage impossible, as we covered in Google pauses open-source bug bounty as AI junk reports flood in. The pattern is consistent: when generation is free and review is human, the platform stops publishing a policy and starts publishing a price.

Who wins and who loses

CurseForge wins week one, in volume. The archetype of the new cohort is already live there: an addon called NCL, whose own listing describes it as "Warcraft Logs-inspired" raid analytics with custom scoring modes, sits at 5,837 downloads, four months old and updated on November 3. It may be perfectly good software. It also exists because the API made the underlying data free and the model made the UI cheap.

Long-time authors lose, and they are the ones with the least recourse. plusmouse, a well-known addon developer, told 404 Media that a nameplate design they introduced now turns up in what feels like every AI addon, and that copyright complaints to CurseForge sometimes produce a takedown and sometimes fail because the code is "just different enough." They have since made some GitHub repositories private, on the theory that it keeps the models from training on them.

Players lose second, and later. Silentcrest's own worry is not clones but abandonware: tools that load on day one, go stale by December, and ship bugs nobody is around to fix. With the December 9 raid tier the demand for meters and logs spikes, and the addons that survive that spike will be the ones with a maintainer behind them.

The contrarian read

It is worth separating two things that are being reported as one. The first is AI theft, which is real and which copyright law is badly equipped to handle when the copied thing is a UI concept rather than a file. The second is volume, which would have broken this API with or without a single language model. A 50-fold increase in developers using a free service in two years is a business model failure on its own schedule; the models compressed it into a launch window and made the abuse cheap enough to be industrial.

That distinction matters because it predicts what the commercial key will and will not fix. It will not stop a clone from existing — the code is written in an afternoon either way. It will stop a hundred clones from scraping at once, because scraping now has a line item. Warcraft Logs is not solving attribution; it is putting a meter on the thing it can measure, which is what every platform ends up doing.

And the biggest constraint on this ecosystem was never the model. Blizzard spent 2026 stripping addon access to combat data in the retail client — combat log events gone, chat log messages converted to strings addons cannot parse, per the 12.0 patch notes catalogued on that same wiki — which is why porting anything to a new client is hard in the first place. If the Forever client inherits a narrower data surface than the 2004 game it is reimagining, the addon gold rush may turn out to have been about a much smaller prize than the subreddits believe. Players are already asking Blizzard to block public combat-log uploads entirely in Forever; that forum thread, not CurseForge, is where this gets decided.

What to watch

Launch volume on November 4 is the first data point: how many new addons appear in CurseForge's Forever filter in 72 hours, and how many of them credit a model. The commercial key's terms are the second — per-application, per-revenue, or per-volume is undisclosed, and the answer tells you whether Warcraft Logs wants rent or wants fewer customers. December 9 is the real test, when the first raids make logging compulsory for anyone who wants a raid slot. And watch whether the Forever build shows up as a selectable game in the Warcraft Logs uploader. If it does not, the platform has answered the volume problem by not serving the market at all.

If you develop addons, would you pay for an API key, or would you rather the platform stayed free and unpoliceable? Write to us via our contact page.