A good quest starts with a learning or exploration goal rather than a target number of stops. HunterGate Builder belongs to LightPath's quest creation tools. This article describes content planning and route testing; check the live interface for buttons and publishing conditions.
Choose a connecting question
A route might gradually answer “How has this neighbourhood changed?” or “Which details reveal a building's purpose?”. Keep stops that add new evidence. Three meaningful observations can be more useful than ten repetitive questions.
Create a stop card
Record the place, observation goal, question, expected explanation and alternative. For example: “Find two repeated façade elements. How do they create a rhythm?” This requires looking closely. If a question asks for a searchable date, connect it to a visible detail or a short, sourced story.
Check content and access
Use permitted images and supported information. Distinguish historical facts from your interpretation. Inspect crossings, entrances, opening conditions and rest areas. Provide an alternative for someone unable to use stairs or make a long walk. A task must not require breaking local rules.
Test with a new reader
Ask someone who did not write the route to try it and explain the instructions aloud. Record actual duration, ambiguous answers, connection problems and unnecessary movement. Revise before inviting a group. Keep a working copy and change log so road works or altered access can be reflected in later versions.