Questie has a Forever-supported release: v12.6.0, dated November 4, 2026, is listed for the Forever flavor and game version 1.60.1. Use that explicit Forever listing when choosing your download. Questie can add quest locations, a configurable tracker and a searchable quest history, but a supported release does not mean every new Forever quest is already mapped correctly.
Start with the current release and a small amount of visible information. If a quest marker is missing, compare the quest log and objective text before treating the addon as broken. Forever-specific database corrections are still appearing in Questie's release notes.
Choose the Forever release and its matching data
Questie's file can support several WoW branches at once. A file shown under MoP Classic or another branch is not automatically the wrong file: the important check is whether that same release also lists Forever. The v12.6.0 entry does.
The project's GitHub release combines Questie 12.6.0 with QuestieDB 1.0.10. These are separate version numbers for the addon and its database. Do not mistake the smaller database number for an older Questie release, or combine an arbitrary older package with newer data just because the names look related.
When comparing downloads, use the release version and intended game flavor first. Download totals and file size do not tell you which game branch a package supports. A mirror can also lag behind the project's own release list.
Set up the information you actually need
Open Questie's configuration with /questie or by right-clicking its minimap button. The project provides extensive controls, so decide whether the immediate problem is finding quests, following an accepted quest, or reviewing what you completed.
| Your task | Questie feature to use | What to look for |
|---|---|---|
| Find a quest giver | Map and minimap notes | Start and turn-in markers |
| Follow accepted objectives | Quest tracker | The current objective and progress |
| Reduce competing markers | Focus quest | Other quest icons become translucent |
| Find unfinished quests in a zone | Quests by Zone | Available and completed quest lists |
| Review your progress | My Journey | Your recorded quest history |
| Look up an entry | Database search | The specific quest, NPC or object |
For your first check, accept a quest and compare its name and objective with the tracker. Then open the map and hover the relevant marker. This gives you a more useful result than enabling every option and trying to diagnose a screen full of icons.
Keep the tracker readable
Questie automatically tracks accepted quests. Clicking a tracker entry can open the quest log, while the right-click menu exposes additional actions. The project also supports focusing one quest so unrelated map icons fade.
Use focus when several quests occupy the same area and you keep following the wrong objective. It changes emphasis; it does not establish that a quest is available to your character or that its location data is complete.
The latest release adds Spoken play buttons and a setting to hide VoiceOver and Spoken buttons. If those controls are taking space you need for quest text, hide them in the tracker settings instead of removing the whole tracker.
Use the map and Journey for different jobs
Map notes describe quest start points, turn-ins and objectives. Hovering notes gives more context, and holding Shift can reveal additional information. Use the actual quest text to interpret the marker rather than reading every pin as an instruction to travel there immediately.
For a broader view, open My Journey from the minimap menu or enter /questie journey. Quests by Zone separates available and completed quests. These views help you find a particular quest or review your history without turning your entire map into a list of everything you might do.
Questie's general documentation also describes an objective arrow through TomTom. Treat that as an optional integration: TomTom itself needs suitable Forever support. You do not need to add it just to use Questie's map markers and tracker.
Map notes show quest state. An absent marker can still reflect incomplete quest data.
Interpret the current release without chasing every old fix
Questie supports several game branches, and its release notes describe changes for more than Forever. Read the branch label attached to a change before assuming it applies to your character. A TBC phase change or a Titan quest correction is not evidence of new Forever content.
For Forever, the notes include database updates, quest-log synchronization changes, map interaction corrections and controller-related adjustments. These establish ongoing work on the branch. They do not mean that every possible error with a similar symptom has the same cause.
Use the release history to make a focused decision. If you are running an older package and encounter the settings-window errors addressed in the current release, updating the supported package is relevant. If your only problem is an unknown quest entry, a new settings interface is a different change and may not answer that question.
Keep the addon and database versions in your notes when comparing results. A report that says only “latest Questie” becomes ambiguous as soon as another release appears. Recording both numbers also makes it easier to distinguish a code change from a data correction.
Check one quest through its full lifecycle
Choose a quest you can already identify in the game and follow it from acceptance to completion. This is a practical check of your setup, not a requirement to abandon your normal route.
- After accepting: compare the quest log with the tracker. Check the title, current objectives and whether the correct entry appeared.
- While working on an objective: compare the progress displayed in the game with the tracker and any relevant tooltip. If only one view is wrong, record which view it is.
- When the objective is complete: inspect the turn-in marker and compare it with the quest text. Do not follow a marker blindly if the description points somewhere else.
- After handing it in: confirm that the completed entry no longer appears as an active objective. If a follow-up is offered, treat it as a separate quest rather than assuming every chain step is immediately available.
This sequence narrows the point of failure. A quest that never appears, a counter that stops updating and a completed quest that remains on the map are different symptoms. Reporting the transition that failed is more useful than saying the whole map is inaccurate.
If the quest is not in the database, keep using the game's objective text for that quest. That allows you to continue playing without turning an uncertain marker into a false prerequisite or location. The absence of a Questie pin should not be used as the sole reason to abandon an accepted quest.
Separate a missing quest from a failed addon
A missing marker and an addon that never initializes need different responses.
- The options and tracker open, but one quest is absent: compare its title and objective with the game log. Search for the quest in Questie. A missing entry can be a data problem rather than a failed installation.
- A quest appears complete in one view and unfinished in another: compare your current objectives and items before abandoning or repeating anything. Release notes include quest-log synchronization fixes, so use the current supported release first.
- Only an old screenshot or guide matches your menu: check the guide's game branch and date. Questie 12.5.0 introduced a native settings interface, replacing the older Ace menu.
- The addon produces a Lua error: retain the complete error text and the action that caused it. A partial final line is much less useful than the first complete error.
Questie's project instructions provide /console scriptErrors 1 to show Lua errors and /console scriptErrors 0 to hide them afterward. Include the addon version, game version, quest name and a repeatable action when reporting an issue.
A Forever file is the right starting point. Correct tracking of your actual quest is the check that matters after that.