WoW: Forever
GRIP-EMS on WoW: Forever
Forever launched on November 4, and this is where Forever sequences live on LazyGrip, kept apart from retail so nobody copies a sequence built for the wrong client. Until real sequences have been run on it, this page is mostly a plain record of what has been confirmed and what has not, and it only says something is true once somebody has seen it happen.
The longer write-up, including the Blizzard addon rules and the save bug, is on the WoW: Forever guide page.
What has been observed
GRIP-EMS loaded on the live Forever client on launch night, build 1.60.1.70790, with no Lua errors at login or at any point after it. The copy tested was the development build that follows v2.4.22, not the v2.4.22 download.
Saving works on the live client. GRIP-EMS wrote its saved data at a UI reload and read it back, and all three saved sequences came back, so the beta-era save bug did not show up at launch.
The CVar health check leaves out the three encounter timeline settings Forever does not have, and /gems status says so, as the v2.4.22 changelog describes.
The spell picker opens on its Class tab and lists the class spells there, Fireball and Frost Armor on a level 1 Mage, as the v2.4.22 changelog describes.
UnitName("player") returns a two-part name as two separate values, the first name and then the surname, and GetUnitName("player", true) returns the two joined. An addon that keeps only the first value of UnitName sees the first name alone.
Whether a sequence actually runs correctly once the addon has loaded. Loading and working are different claims. On launch night three imported sequences loaded and came back after a UI reload, but none was run in a fight, and no Forever sequence on this site has been validated.
GRIP-EMS loaded on the Forever beta without any changes. Forever declares interface 16001, which GRIP-EMS added to its .toc in v2.4.18 on September 17, so the addon passed the interface check exactly as it shipped at the time.
Forever is classed internally as Mainline, meaning it runs the current retail codebase while declaring the older Classic-style interface number. Neither retail testing nor Classic Era testing fully covers it.
v2.4.20 stopped at a Lua error at every Forever login because two spec functions it calls are gone from that client, so the settings panel, sending and receiving sequences, and the tracker never loaded. v2.4.21 fixes it. We have not tested v2.4.21 on the beta ourselves.
Check the dates before you trust any of this as still current, because a Forever patch can change any of it.
Forever sequences
There are 4 Forever sequences on the site. Read the validation notes on each one, because a sequence only counts as validated if it was run on a Forever client.
Browse Forever sequences (the plain Browse page shows retail only).
Posting one
Post it the way you post any sequence, then open it and set Game version to WoW: Forever. That control is only visible to you as the author, and until you set it the sequence is listed under retail. The post form still asks for a retail class and spec, because that is the model the site knows, and Forever may not fit it, so that part will change once it is measured and not before.
If you have tested something on Forever, tell us in the GRIP-EMS Discord with the date and what you ran, and it can go on the list above with your name on it.