Does Questie support WoW Forever?

Only in prerelease form. Questie v12.0.0-pre (September 23, 2026) added Forever client support, but the maintainer says the beta is unstable — SavedVariables do not work, settings do not save, and crashes persist. No stable release yet.

Is the CurseForge questie-forever addon official?

No. A Questie maintainer said of the CurseForge questie-forever package: "not sure who that is, they haven't talked to us." It is not affiliated with the Questie team.

Does TomTom work in WoW Forever?

TomTom's public listing covers Retail and Classic flavors but does not name Forever. Treat it as unverified until its author explicitly supports the client.

What can I use for questing instead?

The built-in quest UI. Blizzard is reworking quest logs and maps in-game, and no third-party helper is verified stable on the beta client yet.

WoW Forever Quest Helper: Questie Status, Options and Beta Setup

Which quest helper works with WoW Forever?

None is stable yet. Questie’s official v12.0.0 prerelease (September 23, 2026) added Forever client support, but the Questie maintainer describes the Forever beta as hostile to addons: SavedVariables do not work at all, settings do not save, and crashes persist on most test characters. The popular CurseForge questie-forever package is not made by the Questie team, and TomTom does not list Forever support. The built-in quest UI is the safe default for now.

What is the current Questie status for Forever?

Questie’s path to Forever is visible in public project records. The timeline below is checked against the project’s own releases and issue tracker as of September 24, 2026.

Date	Development	What it means for players
Sept 12–17, 2026	Forever data tooling discussed in issue #7840	Data collection groundwork started
Sept 18, 2026	QuestieTrace v1.0.0/v1.0.1 released with a Forever TOC	Capture/debug tooling, not a quest helper
Sept 20, 2026	Issue #7858: maintainer confirms official release in the works	Blocked by DB rework, beta instability, Lua errors
Sept 23, 2026	v12.0.0-prerelease adds Forever client support	First official Forever-capable build — prerelease only
Stable release	Not yet published	Wait for a non-prerelease v12 before treating Questie as reliable

The v12.0.0-pre changelog entry is explicit: “Added Forever client support (Logonz).” That makes the project’s Forever work official — but the same maintainer comment that previewed it lists why it is not ready: a major database rework is mid-flight, the beta client crashes persistently with addons enabled, and the addon API changes produce ongoing Lua errors. The full add-on environment context is in the addons guide.

How do you install the official Questie preview build?

The maintainer shared a preview path in issue #7858. It is for testers, not for a main-character setup — the beta can crash on login with addons enabled.

Download the forever-303-patch branch archive: Questie preview zip.
Extract it into _classic_beta_/Interface/AddOns.
Rename the extracted folder to Questie.
Disable all other addons before logging in — the maintainer’s own advice, because crashes on 3 of 5 test characters occurred with addons active.
Expect settings not to persist: SavedVariables do not work on the current beta client, so profiles do not save between sessions.

That SavedVariables breakage is not a Questie bug — it is the beta client, and it explains why no quest helper can feel “finished” until Blizzard stabilizes the API surface. The beta guide covers accessing the test itself.

What about QuestieTrace, TomTom, and the built-in UI?

Tool	Role	Forever status (Sept 24, 2026)
Questie v12.0.0-pre	Quest map, tracker, tooltips	Official prerelease with Forever support; unstable
Questie v11.38.0	Current stable release	Classic only — no Forever support
QuestieTrace v1.0.1	Data capture/debugging for the Questie team	Forever TOC added; shares quest logs, movement, spells in traces
TomTom v4.3.10	Waypoints and direction arrow	Listing covers Retail/Classic flavors; no Forever
Built-in quest UI	Blizzard’s default	The only safe default; quest logs and maps being reworked

Two cautions from the project documentation itself. QuestieTrace’s README warns that shared traces can include your character name, realm, level, movement history, quest log, and known spells — review before uploading anything publicly. And if you share beta clips or screenshots that show the community tools landscape, label the client build so readers do not mistake prerelease behavior for launch behavior.

How should you test a quest helper during beta?

If you want to contribute to the compatibility picture rather than guess at it, run a small repeatable test on each build you try.

Record the Forever client build, addon name, version, and source URL.
Install one quest-related addon first so errors have a clear cause.
Accept a quest, track objectives, open the map, change zones, and watch for Lua errors.
Re-log once to test whether settings persisted (they likely will not — that is the SavedVariables issue).
Publish the result with a date and build number: Compatible, Broken, or Unverified.

Result	Minimum evidence	Reader-facing wording
Compatible	Author lists Forever support + your current-build test	“Verified on build X with version Y”
Preview-stage	Official prerelease, known instability	“Works partly; settings do not persist”
Broken	Reproducible error on named versions	“Broken on build X”
Unverified	No support statement or repeatable test	“No compatibility claim”

What do Blizzard’s addon rules mean for quest helpers?

Forever carries Midnight’s addon disarmament approach — in a Kotaku interview, lead encounter designer Mike Nuthals said “in-game or in-combat add-on disarmament … we’re going to bring that over” — and Blizzard’s general UI Add-On Development Policy requires free, unobfuscated addons while reserving the right to disable functionality. Quest helpers that automate too much are exactly the category those rules target. The demo’s redesigned HUD is covered in the Classic-versus-Retail systems comparison.

What is still unverified?

Open question	Why it matters
A stable (non-prerelease) Questie with Forever support	The practical “is Questie ready” answer
SavedVariables fixes on the beta client	Without them, no addon settings persist
TomTom author support for Forever	Waypoint navigation advice depends on it
Built-in quest tracker/map-pin behavior at launch	Determines how much a helper is even needed
QuestieTrace data handling in shared traces	Privacy review before public uploads

Sources

Questie v12.0.0-pre.c24dba5+v1.0.3 release (“Added Forever client support”)
Questie issue #7858: WoW Forever (maintainer status comment, preview-build instructions, CurseForge package disavowal)
Questie issue #7840 (Forever data-tooling groundwork)
QuestieTrace v1.0.0 release (Forever TOC)
QuestieTrace repository (trace data and privacy notes)
Questie v11.38.0 release (current stable, Classic only)
TomTom listing - WoWInterface (supported flavors, no Forever)
Blizzard UI Add-On Development Policy
Kotaku: New Things Learned About World of Warcraft: Forever (disarmament quote)