BriefingsNov 22, 2026 · RealmList Editorial

Layer Swap Addons Lose Their Layer ID in WoW Forever: What the API Notes Say and What May Already Be Live

A Blizzard engineer told addon authors that Forever 1.60.1 will obfuscate realm IDs in GUIDs and return empty realm names. A TitanLayer author reports it shipped with the November 20 hotfix. Targeted layer picking appears finished; joining a group still moves you to its layer.

AI illustration made for RealmList. It depicts the idea of distinguishable parallel worlds, not an in-game layer view.

Blizzard has not announced an addon change to Forever players. It has told addon authors. That distinction matters here: the strongest evidence is a set of developer notes posted in the WoWUIDev Discord by Blizzard engineer Daniel Yates ("Meorawr"), reproduced by WoWSoD Pro on November 21 and by Chinese outlet 17173 on November 21 evening. We read both reproductions. We could not open the Discord channel or the original Warcraft Tavern and Wowhead articles directly, so the wording below is quoted from those two independent reproductions, not from the primary post.

Taken together, the notes remove the signal that layer-detection addons need. One addon author reports that the change has already arrived.

What the engineer's notes actually say

Two lines are relevant. The first sits under retail's 12.1.7 PTR addon-security changes:

"The realm ID in creature, vehicle, pet and game object GUIDs is now obfuscated along with the server ID and spawn ID."

The note adds that this "will also apply to Forever in an upcoming 1.60.1 hotfix." The second sits under "Coming soon in WoW Forever 1.60.1":

"APIs that return realm names or IDs now instead return an empty string or zero in-place of those values."

It names GetRealmName and GetRealmID and mentions realm-bearing C_BattleNet returns, then says the change "only applies to WoW Forever."

The notes never use the word "layer" and never name an addon. They also carry a disclaimer that they cover addon-facing API and security changes only. The link to layer swapping comes from how the addons work, a connection both Wowhead and Warcraft Tavern drew on November 20 according to WoWSoD Pro.

Why that breaks targeted layer picking

Forever does not expose your layer number to players. Addons infer it: part of every NPC GUID differed between layers, so targeting one NPC gave you a readable fingerprint. Compare two players' readings and you know whether a swap moved you. Layer Swap built its service on that — it advertises showing "which layer you are on" and a list that lets you request a chosen one.

Once that GUID field varies per creature rather than per layer, there is nothing stable to read. An addon can still automate the invitation step. It can no longer tell you where the invite leads, show a layer number, or confirm that a swap succeeded.

One addon author says it is already live

The most concrete evidence is TitanLayer issue #7, which we read on November 22. The author reports testing on client build 1.60.1.71037 after the November 20 hotfix on a PvE realm in Northshire:

  • Seven NPCs read together, including two standing side by side, returned seven different server fields and seven different zone fields.
  • GetRealmName() and GetNormalizedRealmName() returned empty strings; GetRealmID() returned 0.
  • The GUID's shape was unchanged — still seven fields, none flagged secret.
  • The plan is to show off for Forever in version 1.3.0 and stop reading NPCs there; Classic behaviour stays.

That is one author, one realm, and no test of an actual layer change. It is a reported measurement, not an official confirmation. Blizzard's November 20 hotfix post contains no layer or addon line. WoWSoD Pro also notes that a November 24 date circulating on the forums comes from a player post, not from Blizzard — we could not verify a date from an official source.

What still works, and what does not

ActionBeforeAfter
Joining a party moves you to the leader's layerYesYes
Addon shows your current layer numberYesNo
Requesting a specific layer from a listYesNo
Confirming whether a swap changed your layerYesNo, except by looking around

Practically: asking in chat for an invite still gets you into a group and onto its layer. You just cannot choose which layer you land on. If you were running gathering routes across known layers, assume that is over rather than waiting for a workaround. If you swapped to escape a camped quest mob or a world PvP fight, the escape route is now a random invite and some luck.

Our earlier crowded-layer report and the faction-balance thread coverage explain why this matters on crowded and Horde-heavy rulesets. Blizzard has not answered the player threads objecting to the change.

Why it landed now

Blizzard gave no reason, so this is context rather than fact. WoWSoD Pro points to two complaints that grew after launch: claims of repeated layer swapping to re-farm resource nodes — including a forum post about a claimed 2,000 thorium in a day that the poster admitted he had only seen in a screenshot — and the longer-running use of swaps to drop world PvP fights. Neither claim has been verified by us, and Blizzard has not cited either.

The change sits in the same fortnight as the Blackmaw Hold gold removal and the five-per-hour dungeon reset cap. Sharing a timeline is not proof of a shared motive.

If your layer addon shows a question mark or keeps asking you to target an NPC, the change has reached your client. Otherwise there is nothing to install or update; Blizzard has not published a player-facing date.

Verified on November 22, 2026 (Asia/Shanghai). Applies to WoW: Forever 1.60.1 and, per the engineer's notes, to retail 12.1.7 PTR separately. The API wording comes from two reproductions of a WoWUIDev Discord post — we did not read the Discord post itself, and Wowhead and Warcraft Tavern were inaccessible to us, so treat the quoted lines as reported rather than primary. The shipped-state claim is a single addon author's measurement on one realm; Blizzard's November 20 hotfix post (thread 2403040 post #14) does not mention layer addons, and no official player-facing date exists. A November 24 date seen in forum posts is unverified. API behaviour, addon versions and layer settings can change with any hotfix; check the official forums and the addon's own page before relying on layer tools.