A strong run plan is not a script. It is a small set of decisions that helps you notice opportunities, recover from setbacks, and learn without turning discovery into homework.
Use this guide before a run when you have a broad intention—testing a build, reaching a region, or practicing a mechanic—but do not yet know the exact path. Keep the plan spoiler-light by recording questions, priorities, and fallback choices rather than answers.
Prepare the decisions, not every surprise.
The planning loop / repeatable sequence
Five choices before you press start
Name one run objective. Write it as an observable action: test a weapon interaction, reach a checkpoint, or practice surviving a particular encounter. If the goal needs several unrelated outcomes, split it into separate runs.
Choose a learning question. Pair the objective with something you want to understand. “Does this upgrade improve my opening?” is more useful than “make the perfect build,” because it still teaches you something when the run goes badly.
Set a minimum viable build. Pick one core idea and two supporting qualities, such as damage plus safety or mobility plus resource efficiency. Mark desirable additions as optional so an imperfect early choice does not invalidate the plan.
Sketch route priorities. Decide what deserves attention—currency, healing, upgrades, or information—then identify the kinds of rooms or encounters that support it. Leave one or two decision points open for discoveries and offers you cannot predict.
Define the review note. Before playing, decide what you will record afterward: the strongest choice, the point where the plan changed, and one adjustment for next time. A short review turns a failed run into usable evidence.
Route reading / compare without spoilers
Compare options by function
When two paths look appealing, avoid ranking them as universally good or bad. Compare what each route gives you now, what it asks you to risk, and which future choice it keeps available.
Immediate value
Does the route support the current objective with healing, resources, upgrades, or practice?
Cost of commitment
What does it make harder—health, time, flexibility, or access to a different kind of reward?
Recovery room
If the next encounter goes poorly, does the route leave a safer choice or a way to stabilize?
Use neutral labels in your notes, such as “resource-heavy,” “high practice value,” or “preserves options.” This keeps the plan useful even when the game changes the exact contents of a room.
Route notes should describe decisions, not reveal outcomes.
Build preparation / flexible by design
Build around a spine, not a shopping list
A build spine is the interaction you want to test. Everything else is support. Start by naming the spine, then list the conditions that make it work and the warning signs that suggest a pivot.
Core interaction: the one relationship between abilities, items, or tactics you want to explore.
Support needs: two practical qualities that keep the interaction usable, such as range, defense, energy, or crowd control.
Pivot signal: a clear reason to change course, like missing the required support after several choices or losing the resources needed to sustain it.
Success evidence: what you will look for during play, rather than a promise that the run must reach a particular ending.
Record alternatives by role instead of by exact name: “any reliable ranged option” or “a defensive substitute.” Role-based notes protect discovery and help you make decisions when the ideal piece does not appear.
After the run / keep the signal
Review in three lines
Do not rewrite the whole run. Capture only the details that can change your next decision.
01 / worked
What helped?
Name the choice, route feature, or habit that made the objective easier.
02 / shifted
Where did the plan bend?
Note the moment new information or a setback changed your priorities.
03 / next
What will you test?
Carry forward one adjustment, not a complete redesign.
The best plan leaves room for the game to answer back. Set a direction, preserve a fallback, and let each run make the next question more specific.
QuestNest has no optional tracking until you give consent. Your choice is saved only to remember this preference. Read the privacy policy.
