- Underkeep endings are tied to planned story choices, quest events, and branching outcomes.
- Mushroom questline decisions may influence later content and should be tracked carefully.
- No ending list is confirmed before the planned November 5, 2026 release.
- Personal map markers help preserve unresolved routes, NPC locations, and return points.
- Balanced parties make it easier to explore optional content without wasting key resources.
Underkeep Endings: What Is Confirmed
Underkeep endings are expected to reflect player decisions across quests, events, and exploration rather than functioning as a single fixed conclusion. Current official information describes different endings as part of the game’s planned content, while also highlighting quest choices that can affect later events.
The most useful approach is to separate confirmed information from route speculation. The game is planned for PC release on November 5, 2026, with Steam and GOG listed as launch storefronts. Until the full story is available, exact ending names, requirements, and outcome summaries should not be treated as established facts.
| Confirmed element | Current status | Practical meaning |
|---|---|---|
| Different endings | Planned feature | Player decisions may produce more than one final outcome |
| Mushroom questline | Planned full-game content | Track choices and follow-up objectives carefully |
| Quest decisions | Mentioned in development information | Some events may change after a player makes a decision |
| Story details | Not fully published | Avoid relying on unverified ending spoilers |
| Release timing | November 5, 2026 | Route pages should be updated after the full game becomes available |
The official Underkeep website presents the game as a first-person, grid-based, turn-based dungeon RPG built around a four-person adventuring party. That structure matters for endings because exploration, encounters, and quest decisions are connected systems rather than isolated activities.
Do not label rumored endings, unverified route names, or assumed character outcomes as canon. Mark them as unconfirmed until they appear in the released game or an official update.
A reliable endings guide should therefore record:
- The decision that begins a branch.
- The location where the decision occurs.
- Any NPC, quest, or item connected to the branch.
- Whether the player can return after making the choice.
- The later event or objective that confirms the route.
This format keeps the wiki useful without inventing conclusions that are not supported by the available material.
How Quest Choices May Shape the Story
Underkeep’s planned quest structure makes route tracking especially important. Development information describes a Mushroom questline that can enter the full game, with some events potentially changing according to player decisions. That does not confirm a specific ending, but it does establish a reason to document choices and follow-up content.
Treat each major decision as a route marker. A choice may affect an immediate conversation, unlock a later objective, change access to an area, or alter the context of a final event. Until the released quest data is verified, the safest method is to record the decision without assigning a final outcome.
Decision Point
- Record the exact choice or response.
- Note the quest and location.
- Mark whether the decision appears permanent.
Follow-Up Event
- Check nearby NPCs and objectives.
- Revisit connected locations.
- Record new dialogue or route changes.
Ending Evidence
- Confirm the final scene or result.
- Separate direct evidence from interpretation.
- Link the outcome to the earlier decision.
| Route record | What to write down | Why it matters |
|---|---|---|
| Quest name | Exact quest or storyline label | Prevents similar objectives from being merged |
| Decision | Chosen response or action | Creates a clear branch reference |
| Location | Dungeon room, NPC area, or event site | Helps players reproduce the route |
| Immediate result | Dialogue, access change, or objective update | Shows the first confirmed consequence |
| Later result | New event, reward, conflict, or ending scene | Connects the branch to its final outcome |
For the Mushroom questline, use a neutral record until the full sequence is confirmed. A good wiki entry might state that a decision changes a later event, while leaving the exact ending interpretation to a separate, evidence-based section.
Create one note for every major decision and update it after each return visit. A short route log is more reliable than trying to remember which response produced a later event.
Avoid building a traditional “best ending” ranking before the game’s outcomes are documented. A route may provide different story information, character consequences, or exploration access without being objectively superior. Once the game is available, outcome pages can compare requirements, missed content, and replay value instead of forcing every result into a tier list.
Step-by-Step Ending Route Tracking
Use the following process when exploring Underkeep’s branching quests. It is designed for first playthroughs and later route comparisons. The method also works well with the game’s automatic map and personal marker systems.
Prepare a Route Log
Create a simple record with the quest name, current objective, decision made, and next suspected location. Keep separate entries for different playthroughs so their choices do not become mixed.
Mark Unresolved Locations
Use personal map markers for NPCs, locked doors, unexplored branches, suspicious rooms, and events that require a return visit. Add a short label explaining why the location matters.
Record the Immediate Consequence
After making a decision, check the quest journal, nearby dialogue, accessible routes, and map state. Write down what changed before moving into another encounter.
Revisit Connected Areas
Return to locations linked to the quest when a new objective appears. Compare NPC dialogue and environmental changes with your earlier notes rather than assuming the branch has ended.
Confirm the Final Outcome
Only mark an ending as verified after reaching the relevant final scene, conclusion, or explicit story result. Record the preceding choices and any requirements needed to reproduce it.
| Tracking stage | Recommended marker | Example note |
|---|---|---|
| Unresolved clue | Question mark or “Check” | Symbol near a blocked passage |
| Quest branch | “Choice” | NPC decision may affect later event |
| Return point | “Revisit” | Door or room connected to a future objective |
| Optional content | “Side” | Possible quest or encounter away from main route |
| Verified outcome | “Confirmed” | Ending scene reached and recorded |
This process reduces accidental spoilers while making later comparisons easier. It also prevents a common mistake: assuming that the first completed quest objective is the final result of that storyline.
Verify the outcome first, then write the interpretation. This keeps the wiki clear about what the game shows and what the community infers from it.
A route log is especially valuable when choices interact with exploration. Underkeep uses grid movement, handcrafted dungeon spaces, environmental dangers, puzzles, and optional paths. A player who rushes through the main route may miss the location, clue, or NPC needed to understand a later consequence.
Party and Exploration Preparation
Ending routes are not only about dialogue. Accessing optional events may require careful exploration, repeated returns, or surviving encounters while preserving endurance and mana. The four-person party system gives players flexibility, but the group should still cover complementary combat responsibilities.
Before entering a section connected to a major quest, review the party’s condition and map markers. A difficult encounter can force a retreat, while an unresolved puzzle or locked route may require returning after another objective. Preparation keeps story exploration from becoming a resource problem.
| Preparation area | Recommended approach | Main risk |
|---|---|---|
| Party roles | Cover frontline pressure, damage, utility, and flexibility | One weakness can limit optional routes |
| Endurance | Save high-cost actions for decisive turns | Early spending may weaken later encounters |
| Mana | Use expensive abilities when they change the fight | Low reserves can reduce route flexibility |
| Map markers | Label unresolved doors, NPCs, clues, and branches | Important return points become easy to forget |
| Exploration pace | Check side routes before leaving a region | Optional story content may be missed |
Balanced Expedition
A flexible party for uncertain routes. Keep enough durability and utility to investigate optional areas without committing to one combat plan.
Resource-Control Team
A measured setup that preserves endurance and mana across multiple encounters, making longer quest routes easier to manage.
Control and Adaptation
A tactical setup focused on spacing, movement, and responding to changing grid conditions during difficult route sections.
The official game information identifies classes such as Warrior, Voidcaller, Archer, and Wizard, with additional planned options including Thief and Blood Mage. These class references support broad party planning, but they do not establish a required class for any particular ending.
Do not assume an ending requires a specific class until the released game confirms it. Build a party around reliable coverage, then record any genuine class-specific requirement after testing it.
The same principle applies to equipment. Gear upgrades and special attributes may help compensate for character weaknesses, but no verified ending-specific equipment requirements are currently available. Treat equipment as a tool for safe exploration rather than a presumed story key.
Ending Checklist and FAQ
Use this checklist before committing to a major route. It is intentionally spoiler-light and focuses on preserving information rather than forcing a particular result.
Ending Route Checklist:
- Record the quest name and current objective
- Write down every major dialogue choice
- Mark unresolved NPCs, doors, clues, and return locations
- Review party endurance and mana before optional encounters
- Confirm the final outcome before labeling an ending as verified
| Before a choice | After a choice | Before the final result |
|---|---|---|
| Save the current objective in your route log | Check dialogue and quest updates | Review all connected route notes |
| Mark nearby unresolved locations | Revisit linked NPCs and areas | Confirm the final scene or story result |
| Note available responses | Record access or environmental changes | Separate evidence from interpretation |
| Check party resources | Avoid deleting useful map markers | Add requirements for replaying the route |
The Underkeep Steam page and official news updates should remain the primary references for release information and confirmed systems. The planned release date is November 5, 2026, so detailed ending pages should be expanded as verified gameplay information becomes available.
Q: How many Underkeep endings are confirmed?
A specific number is not confirmed in the available official information. Different endings are planned, but exact ending names and requirements should wait for verified full-game data.
Q: Can the Mushroom questline affect an ending?
The Mushroom questline is planned for the full game, and some events may change according to player decisions. That supports careful route tracking but does not yet confirm a specific ending outcome.
Q: What should I record when following an ending route?
Record the quest, location, decision, immediate consequence, return condition, and later story result. Personal map markers are useful for unresolved NPCs, doors, clues, and branches.
Q: Is there a confirmed best ending in Underkeep?
No verified ranking is currently available. Different outcomes may emphasize different story consequences or discoveries, so avoid calling one route best until the released content can be compared.
When new ending information is confirmed after November 5, 2026, update route requirements, outcome summaries, and spoiler labels together so every page remains consistent.