Layer Swap: layer addons lose the realm in WoW Forever

Layer Swap: four translucent zone maps stacked above hills at dusk, with the text "Layer Swap" and "Hidden realms" dated November 21

Article by Kami

Update, November 21, 8:30 p.m. Paris time: the author of Layer Swap confirms that the addon can no longer tell layers apart on Forever, a second addon measures it, and Blizzard’s notes now have an identified author. Two sections were added: what the addon still does, and its limit of ten switches per hour.

You open your layer-switching addon, and the line that showed your realm is empty. Since the November 20, 2026 hotfix, WoW Forever returns an empty realm name and a realm ID of zero to addons. Addon authors are reporting it on their GitHub repositories: the AltStable issue was opened on November 21 at 1:36 a.m. Paris time. For an addon of this kind, like Layer Swap, which exists to show and pick your layer, the basic data disappears, and its author removed the layer list on November 20.

A layer is a parallel copy of the same area of the world: the game spreads players across several copies to avoid crowding. Our October 25 article describes this system as it stood ten days before the November 4 launch.

What Blizzard is taking away from addons

An addon talks to the game through an API, a set of functions Blizzard makes available to it. Two of them, GetRealmName and GetRealmID, gave the realm’s name and number. Blizzard’s text, copied into a ticket on the BrokerAnything repository opened on November 20 at 9:58 p.m. Paris time, says that APIs which returned realm names or IDs “now instead return an empty string or zero in-place of those values”. It specifies that the change applies only to WoW Forever. These notes were posted on November 20 by Daniel Yates (Meorawr), a software engineer at Blizzard, on the WoWUIDev Discord, the server where interface developers gather, as reported by Warcraft Tavern.

BrokerAnything repository issue #6 on GitHub, which copies Blizzard's text on realm APIs returning an empty string or zero, and the LibRealmInfo library error
GitHub, BrokerAnything repository, issue #6 opened on November 20, 2026 at 9:58 p.m. Paris time, screenshot taken November 21, 2026.
Warcraft Tavern article by Luxrah on November 20, 2026: Daniel Yates, aka Meorawr, posts API changes on the WoWUIDev Discord that prevent targeting a specific layer
Warcraft Tavern, article by Luxrah published November 20, 2026, screenshot taken November 21, 2026.

The same source mentions a second kind of masking: the realm ID inside GUIDs is now scrambled. A GUID is the unique number that identifies a creature, vehicle, pet or object in the world. A first version already existed in the beta: the 1.60.1 beta notes of October 16, 2026, as recorded on the Warcraft Wiki, scrambled two other parts of the GUID, the server ID and the spawn ID, “to prevent comparison to determine layer”.

So the reason is only spelled out in black and white for GUIDs. For realm names, it is the ticket’s author who puts it forward: Forever returns empty names “in an attempt to stop targeted layer jumping”. The reasoning fits the beta, but it is not a sentence from Blizzard.

Advertisement
RestedXP Forever - Partenaire officiel -10%

Why Layer Swap and other layer addons depended on it

A layer addon reads a creature’s GUID to know which copy of the zone you are in, then files what it learns by realm. The author of GlassPanel describes this mechanism in a pull request: the recorded layers were sorted by realm name, and with an empty name, every realm fell into the same slot. The same text warned that reading the server field in the GUID could also disappear. It has: the same developer measured it on TitanLayer, another addon they maintain, in an issue opened on November 21 at 3:10 a.m. Paris time. Seven non-player characters read together, two of them standing side by side, gave seven different server fields: the GUID keeps its shape, but it no longer says anything about the layer. Since version 1.3.0, TitanLayer shows “off” on Forever.

Pull request #168 on the GlassPanel repository on GitHub, merged, explaining that recorded layers were sorted by realm name and that this name has been empty since the November 20 hotfix
GitHub, GlassPanel repository, pull request #168 merged overnight between November 20 and 21, 2026, screenshot taken November 21, 2026.
Issue #7 on the TitanLayer repository on GitHub: since the November 20 hotfix, an addon can no longer read the layer from non-player character GUIDs, seven readings giving seven different servers
GitHub, TitanLayer repository, issue #7 opened on November 21, 2026 at 3:10 a.m. Paris time, screenshot taken November 21, 2026.

The table lists the steps of this lockdown, with their source.

Date (2026)What changes for addons
October 16Beta: the server ID and the spawn ID in GUIDs are scrambled, according to the 1.60.1 beta notes.
November 20The realm name and realm ID APIs return an empty string or zero; the realm ID in GUIDs is scrambled in turn. The exact time it went live is not known.
Night of November 20 to 21The author of AltStable and GlassPanel, one and the same developer, publishes a fix for each of the two addons.
November 20 and 21Layer Swap ships versions 1.14.41 to 1.14.44 in a row and removes the layer list on Forever; TitanLayer 1.3.0 shows “off”.

Layer Swap no longer knows which layer you are on

The author of Layer Swap reacted on the day of the hotfix. Version 1.14.41 came out on November 20, then three more on the 21st, up to 1.14.44 in the early evening. The addon’s CurseForge page, which shows nearly 3.5 million downloads, puts it this way: “Since 20 November 2026 the game no longer lets an addon tell one layer from another on WoW Forever”.

Header of the CurseForge page of the Layer-Swap addon by Adam5288, with 3,476,590 downloads and an update 55 minutes old at the time of the screenshot
CurseForge, Layer-Swap page, screenshot taken November 21, 2026 around 8 p.m. Paris time.
Layer-Swap description on CurseForge: since November 20, 2026, the game no longer lets an addon tell layers apart on WoW Forever, and the button sends you to a random layer
CurseForge, Layer-Swap page, section on WoW Forever, screenshot taken November 21, 2026 around 8 p.m. Paris time.

So on Forever, the addon no longer shows a list of layers and no longer asks for a particular one. The /ls swap command followed by a letter, which targeted a specific layer, now only works on Classic Era and TBC Anniversary, where reading creatures still works. Where the list used to be, the panel now tells you what just happened: who moved you, whether the host was already on your layer, how long to wait once the hour’s switches are used up. The description opens with a warning: “We do not support abuse of the addon, or using it to take advantage of PvP situations”.

Ten layer switches per hour, none in the middle of a fight

The “Swap layer” button stays, but it sends you to another layer without letting you choose which one, just as a host’s invite already did (a host is a player who invites you to their group). One click asks for an invite in the “layer” channel. On Forever realms, where an addon cannot post in chat, the request goes out as a hidden message to players in your zone who have the addon. You accept, you join the host’s group and therefore the host’s layer, which you keep when you leave the group: Layer Swap leaves it for you four seconds later. The page also gives a cap: “On Forever the game moves a character to another layer ten times an hour”.

Excerpt from the Layer-Swap page: on Forever, the game moves a character to another layer ten times an hour, and no request goes out in combat or for the next six seconds
CurseForge, Layer-Swap page, “Swap layer” section, screenshot taken November 21, 2026 around 8 p.m. Paris time.

The addon counts your switches for each character, even across logins, warns you when three are left, then shows “Wait” with the time remaining. That cap comes from the author: we did not find it in any Blizzard text. Another lock on Forever: no request goes out during combat or for six seconds afterwards, because “a swap is no way out of a fight”.

What players lose is the choice of destination: joining the layer where a rare monster, an ore vein or a world boss has just been spotted, or seeking out or avoiding a PvP fight on a specific layer. Switching to a random layer, to get out of a crowded zone, is still possible.

Addons unrelated to layers break too

AltStable, an addon that tracks your characters, is nothing like a layer addon and still runs into the problem. It worked out the realm type (normal, hardcore, role-playing or PvP) from the realm name; since the hotfix, characters seen for the first time show as “Unknown”. Its author writes that Forever hides the realm “on purpose”, according to addon authors in the #forever channel of the WoWUIDev Discord, and now reads the game’s active rules instead.

Issue #412 on the AltStable repository on GitHub: since the November 20 hotfix, GetRealmName returns an empty string, and characters seen for the first time show an unknown realm type
GitHub, AltStable repository, issue #412 opened on November 21, 2026 at 1:36 a.m. Paris time, screenshot taken November 21, 2026.

The ticket quoted above also comes from another field: BrokerAnything is an info-bar addon, and it relies on LibRealmInfo, a code library shared between addons. That library contains a check that rejects an empty realm name: the ticket’s author counts about fifteen cascading errors, the first of which comes from there. The same day, the author of BrokerAnything replied “Wrong addon” and closed the ticket.

What is still possible without Layer Swap, and what we don’t know

If your info bar shows a LibRealmInfo error or an “unknown” realm, update your addons: AltStable and GlassPanel received a fix overnight between November 20 and 21, and Layer Swap is now at version 1.14.44. Switching layers by joining a player’s group, without an addon, is still possible: it is in fact all Layer Swap can still do on Forever, and our October 25 article already reported, citing GameSpot, that joining a group places you on your friend’s layer. What disappears is picking a specific layer.

ItemStatus as of November 21, 2026, 8:30 p.m.
Empty realm name and IDEstablished: notes by Daniel Yates (Blizzard) on the WoWUIDev Discord, observed by three addon repositories.
Reading the layer from the GUIDOut of service on Forever: measured by TitanLayer, confirmed by the Layer Swap page.
Time it went liveNot found, beyond the date of the hotfix (November 20).
Layer addons affectedLayer Swap, TitanLayer and GlassPanel have removed layer reading on Forever. No complete list.
Cap of ten switches per hourWritten by the author of Layer Swap, absent from the Blizzard texts found.
Announcement on targeted layer addonsSentence repeated by GlassPanel and TitanLayer, original source not found.

On Blizzard’s side, Daniel Yates’s notes, as Warcraft Tavern reproduces them, describe the APIs without using the word layer. The sentence “targeted layering addons will be disabled through API changes”, repeated by GlassPanel and then TitanLayer, still has no original source found. As of the evening of November 21, no Blizzard employee had replied on the European forum thread about the end of these addons, which had 36 posts. The November 24 date going around comes from a player’s post on the American forum, with no source, while the tickets show a change already in place. Nothing above was tried in game by the site: everything comes from the tickets, notes and page cited.