FAST ANSWER / QUEST MAP
Use the quest map as a lead, not an autopilot.
Start with the quest's visible pressure point, then compare the reported minimum, outcome class, and any special knight or state requirement. If the page says a result came from game files or a player report, reproduce it before calling it guaranteed.
- Write down the quest name, visible stat pressure, party size, and current story state.
- Use the reported minimum and unexpected-outcome notes to choose one test candidate.
- Log the debrief, reward, branch, and build state before changing one variable with a rewind.
What the new quest map adds
The latest community guide is useful because it treats the game as a collection of quest states rather than a simple stat checklist. It maps reported success conditions, possible result classes, and special outcomes tied to particular knights or story states. The author says the map was built from game files and then checked in-game, so it is richer than a purely anecdotal list, but it can still contain errors or version-specific behavior.
- Use it to locate the relevant quest and outcome
- Keep file-derived values separate from what the current build visibly confirms
- Treat comments and corrections as new leads, not automatic truth
- Record the exact build when a result matters
How to read one quest entry
Break each entry into four questions: what stat or trait is being tested, what minimum is reported, what outcome class is possible, and whether a named knight or story state changes the result. That structure turns a long quest list into an actual dispatch decision.
- Pressure point: Strength, Agility, Charisma, Magic, Wit, Luck, or a hidden trait
- Threshold: the reported minimum or the range that still needs testing
- Outcome: Critical Success, Critical Failure, or Unexpected Outcome
- Branch: knight, relationship, evolution, location, or story state
Unexpected outcomes are the reason to keep a log
The community material specifically emphasizes that some quests change when a particular knight is sent. A result that looks like a failure in a generic guide may be a deliberate character branch, an evolution trigger, or a state-dependent outcome. Keep the special knight and preceding state in the note instead of flattening it into a universal best choice.
- Record the assigned knight, equipment, party order, and quest state
- Capture the result and any new scene or trait
- Compare the same quest with a different knight only after restoring the baseline
- Mark a suspected bug or impossible branch as unresolved
The safe verification loop
Use one checkpoint for one question. Start from the same preceding state, test the reported candidate, and write down the result before rewinding. If the result changes after an unrelated dialogue choice, day, party member, or upgrade changes, split the note by state rather than publishing a single rule.
What we will not publish as fact yet
A file-derived minimum is not automatically a player-visible guarantee, and a single successful run is not proof of a universal outcome. This page will keep exact conditions behind an evidence label until they are reproduced in the current build or supported by an official explanation.
Baseline source: official Sovereign Tower page on Steam. Additional reference: recent community all-quests map and corrections. This note is an independent editorial guide; evidence status is shown where it matters.