WoW: Forever addon restrictions limit combat automation
Blizzard designers told Kotaku that WoW: Forever's in-combat addon disarmament will block computational marking and communication; exact API boundaries remain unpublished.
Guide details and editorial record
Guide context
The quick answer
Blizzard says WoW: Forever will keep in-combat addon restrictions that block computational automation for marking and communication. The exact API boundaries and addon-by-addon outcomes remain unpublished.
- For
- Players and addon authors preparing for WoW: Forever beta
- Game version
- World of Warcraft: Forever developer interview and secondary UI report, checked September 17, 2026
AI-written and automatically published after automated review ·
Responsible editor: Max · Editorial record: medium risk · automated review · AI assistance: draft
In this article
Blizzard designers told Kotaku in a September 14 interview that World of Warcraft: Forever will use in-combat addon disarmament to block computational automation used for marking and communication. Kotaku also reports that the one-button rotation feature will not carry over. The interview does not publish the exact API rules behind that boundary.
What the interview establishes
The restriction is aimed at addons that calculate combat decisions and then automate player-facing marking or communication while combat is underway. That is the supported observation from the direct interview. It does not identify every protected API call, event, value, or user-interface feature.
The one-button rotation feature is a separate, clearer carry-over decision: Kotaku reports that it will not be part of Forever. The source does not turn that statement into a broader list of allowed or disallowed addons.
What the secondary report adds
Wowhead’s September 16 report attributes additional detail to a WoW UI Discord statement. It says Forever shares most of the mainline 12.1.5 UI architecture and mentions secret values, AuraContainer, and the wider disarmament work.
That report is a secondary, manual-discovery source. Realm First has not treated it as a public Blizzard API specification. It does not establish full API compatibility, and it cannot determine whether a named addon works, fails, or needs changes.
What addon authors can verify next
The evidence currently supports a broad combat-automation limit and the removal of one-button rotations. It does not support an addon compatibility table. Exact API behavior needs a named beta build, reproducible tests, and a source record for each observed result.
The WoW: Forever systems guide keeps the wider source ledger and its evidence limits together. This page will be updated when Blizzard publishes API details or a beta observation supplies them.