For an in-game journal with dungeon quests, their map locations and boss drops, DungeonJournal has an explicit Forever release: ForeverDungeonJournal1.6.6.zip, dated November 3, 2026, for game version 1.60.1. Open it with /dj.
Do not confuse it with the separate project Forever Dungeon Journal, which describes a spoiler-light exploration journal and lists much of its functionality as planned. A similar name does not mean the two projects share features, data or release status.
Match the journal to the question you need answered
The phrase dungeon journal can describe several different tools. Start by deciding whether you need information inside the game, a browser reference, or a way to record exploration.
| Tool | Main purpose | Important boundary |
|---|---|---|
| DungeonJournal | In-game boss drops, dungeon quests and quest locations | Choose its Forever file, not its separate Era or TBC package |
| Forever Dungeon Journal | A spoiler-light atlas and personal discovery journal | Its feature list is primarily a development plan |
| Wowhead's Forever Dungeon Journal | Browser pages for dungeons and bosses | A website, not an addon you open with /dj |
If your immediate task is collecting dungeon quests before meeting your group, DungeonJournal is the most direct match among these options. If you want boss abilities and role-specific notes in a browser, the web journal serves a different job.
Open DungeonJournal and find a quest
After choosing the Forever package and enabling it in your Forever installation, use this short check:
- Enter
/djto open the journal. - Select the dungeon you intend to visit.
- Review its quest entries and rewards.
- Click a quest to display its location on the map.
- Compare the quest's information with your character's current quest log before planning the trip.
This flow helps you connect a dungeon to a quest location without memorizing a separate list of quest givers. It does not mean every entry is available to your particular character. A visible quest is information to check, rather than proof you have met its requirements.
The author continues correcting quests and rewards as the game changes. If a reward or location looks wrong, retain the dungeon name, quest name and addon version rather than assuming that an old Classic entry must be right.
Restore a missing minimap button
DungeonJournal allows you to remove the minimap button by right-clicking it. If the window still opens with /dj, the missing button alone does not mean the addon has stopped working.
Use /dj minimap to add the button back. This separates a hidden shortcut from a loading problem and avoids reinstalling the addon just to recover the icon.
Read a loot entry without assuming complete coverage
DungeonJournal is described as providing boss drops, quests, rewards and useful in-game details. Use the boss list to inspect a drop before deciding whether a particular dungeon is relevant to your character.
Keep two questions separate: whether the addon opens successfully, and whether its database contains the latest correct information for that boss. A file tagged for Forever answers the compatibility target; it does not certify every item entry.
For an upcoming run, check the exact dungeon and boss you care about. If the entry is absent, do not fill the gap with a different WoW branch's loot list. Forever expands the original world, and familiar dungeon names do not guarantee unchanged rewards.
Choose a boss to inspect the listed items; the picture does not certify every loot entry.
Understand the separate exploration journal
Forever Dungeon Journal describes an atlas that preserves discovery instead of automatically revealing every detail. Its planned features include authored floor plans, dungeon markers, personal notes, discovery tracking and configurable spoiler levels.
Those are useful design goals, but the project labels them Planned features. Do not select it on the assumption that every dungeon already has a complete floor plan, a verified marker pack or a working progress history.
Its description also says that the framework can function before every data pack is complete. When evaluating a release, ask whether the specific dungeon data you need is included, rather than treating the existence of the framework as complete dungeon coverage.
Choose it for exploration only after checking the available release and data packs. Choose DungeonJournal when you want the clearly described /dj quest-and-loot workflow.
Prepare a short dungeon note from the journal
Use the journal to leave with a plan you can act on, rather than a large copied list. For a single planned run, separate the entries into three groups: quests to investigate before leaving, loot you want to inspect, and information that remains uncertain.
For each quest, keep its exact name and the location shown when you select it. Compare that with your current quest log. If it appears to continue a chain, do not assume the journal entry alone confirms that you can collect it immediately. Your current character state still matters.
For loot, keep the boss association and item name. That is enough to identify what you are looking for without turning a database entry into a guaranteed drop or a promise that the item is the best choice for your role.
For unresolved information, state the gap precisely. “This boss has no entry in my current addon version” is useful. “The dungeon has no loot” is a different claim and is not justified by an empty addon panel. Keeping that distinction prevents a missing database row from changing your entire plan.
You can use the note when discussing the run with your group. It keeps a missing quest pickup or an uncertain entry visible before you travel, while leaving encounter strategy to a relevant boss guide rather than inventing it from a loot window.
Identify what failed when the journal seems wrong
Start with the simplest observable result: can /dj open the window. If it can, you have a different problem from a package that never loads.
| What you see | What to check next | What the symptom does not prove |
|---|---|---|
| The window opens but a dungeon is absent | Selected project, version and available dungeon data | The dungeon is absent from Forever |
| A quest appears but its map action is unexpected | Exact quest selected and current quest text | Every quest marker is wrong |
| A boss is listed with incomplete drops | That boss's entry and the package's updates | The boss drops nothing |
| Only the minimap icon is missing | /dj and /dj minimap | The addon must be reinstalled |
| A similarly named addon behaves differently | Full project name and its stated workflow | The two projects share commands or features |
Change one relevant part of the setup at a time. If the error concerns an item or reward, retain its name and the addon release so the author can identify the entry. If it concerns opening a window or clicking a quest, retain the action and any complete error text.
A useful journal does not have to answer every dungeon question. It needs to answer your chosen question clearly, while making incomplete entries recognizable enough that you can avoid building a plan on them.
Use a web journal for mechanics and role notes
Wowhead's Forever web journal organizes dungeons and bosses into their own pages. Its described sections include level ranges, quests, loot and role-specific boss notes, with recorded changes from Classic Era where available.
That is a useful companion when preparing outside the game. It should not be confused with an in-game Adventure Guide feature or with a plugin installed by another addon.
Read the Forever entry for the exact dungeon and encounter. Missing pages can reflect unfinished coverage, and a boss's Changes tab only contains changes already recorded there. For a practical first run, leave with a short list of the quests you want, the boss information you need and any unresolved entries to check with your group.