A quest needs an answer path
RealmQuest combines a themed exploration outline with a dependency graph of tasks. A node can open immediately, follow one earlier node or require several branches to be complete. Use it when the host wants actual progression rules rather than a story that merely says a gate is locked.
The planner supplies a shared host-controlled progress record, a countdown and reward/failure text. It does not generate a complete original world from an empty brief, and it does not track each named team independently. Write the fictional setting and task wording so participants know what they can examine and what counts as a valid answer.
Use the six-part node format
Set common event details, then write each node as id | name | prerequisites | answer | hint | points. Use short unique IDs. Leave prerequisites empty for an opening node; separate multiple prerequisite IDs with commas. Answers and node names are required, and points may range from zero to one thousand.
Add exploration team names, a time-limit/failure rule and a completion reward. Unknown prerequisites and circular dependencies are rejected. The tool validates graph structure, not whether a clue’s wording logically supports its answer. Test each task yourself, especially when a participant must derive a word from an earlier result.
What verification changes
The result lists nodes, dependencies, entered answers and hints in a host view. In Team progress, enter a response and use Verify for that node. An answer is checked after trimming surrounding spaces and ignoring case. It must otherwise match the stored answer, so synonyms and numeric alternatives need a host decision.
Verification refuses a node until every prerequisite is complete. The quest finishes when all nodes are verified, not when a partial score threshold is reached. The countdown has start/resume, pause and reset controls. Reaching zero displays a time-limit message; it does not automatically apply penalties, unlock all tasks or implement your written failure rule.
Fictional example: three archive seals
For twelve guests and two teams named Cloud and Reed, enter 90 minutes from 15:00. Use these three nodes: map | Add 8 and 6 | | 14 | Combine both numbers | 10; letter | Reverse RATS | map | STAR | Read backward | 20; seal | Shift NHB backward 3 | letter | KEY | N becomes K | 30. Put each record on its own line.
The first answer is 14. Reversing RATS gives STAR, and shifting N, H and B backward three letters gives K, E and Y. The graph is map → letter → seal, worth sixty listed points. Attempting seal before letter is complete is refused even if someone knows KEY. Verify all three in order to reach Quest complete.
The two team names are part of the plan, but both contribute to this single progress record. The host can divide paper materials between teams, then bring answers together at the final gate. The ninety-minute countdown is an overall host timer, not an independent clock for each team or an automatic record of finishing order.
Rehearse the graph as well as the story
Walk through the opening state, a wrong answer, an early final answer and the successful route. For parallel branches, make sure both can begin and that the finale names both prerequisite IDs. A graph without cycles can still be frustrating if a necessary clue is hidden in an inaccessible place.
Keep exits and breaks independent of game progress. Offer a hint or debrief instead of making a participant remain in a room until they solve something. Save completed progress deliberately and protect the host copy: generic result fields and exports can expose the answers. Use original settings and safe paper props rather than presenting fictional exploration as real survival guidance.
Questions before you begin
Does each team have its own saved progress?
No. The current result has one node-completion state. Team names describe the activity; they do not create separate live team sessions.
Why is a correct answer refused at the final gate?
Every prerequisite must be complete first. Knowing the word is not sufficient to bypass an unfinished branch.
Does the timer apply my written penalty automatically?
No. It displays remaining time and an expiry message. The host applies the announced rule and any debrief procedure.
Are hidden answers secure from participants?
No. This is a host-facing result, not an authenticated player portal. Keep screens and complete exports away from unintended viewers.