THE SHORT ANSWER
Record the scene, visible options, choice, and outcome for each attempt. Community reports describe differing options and results, so matching one answer does not establish a guaranteed path. A run log preserves observations; it does not reveal the hidden decision rules.
A route needs more than its final answer
In the October 1–2 player discussion, one person described a second attempt by another player that followed the same remembered choices but offered a different later option. The bonding discussion also collects multiple possible endings. These reports support caution when comparing short answer sequences.
A useful comparison begins earlier: were the scenes alike, were the same choices available, and was the final result actually recorded? If any of those details are missing, keep the comparison provisional. Similar wording does not prove identical game conditions.
Use four fields for each turning point
You do not need to copy an entire story page to preserve an observation. A concise summary in your own words is easier to search later and keeps your notebook focused on what you did.
- Scene: enough context to recognize the encounter again.
- Options: the choices you could actually see at that moment.
- Action: the option you selected, without adding a motive after the fact.
- Result: the next scene, a confirmed bond, a stated failure, or an interruption.
Keep facts and explanations separate
“I selected this option and then failed” is an observation. “That option always causes failure” is a much stronger claim. Your notes should preserve the first without silently turning it into the second.
If you develop a theory, write it as a separate note and include what would contradict it. Changing one choice on another attempt can be informative, but it is not a controlled experiment when other conditions are unknown. Do not erase a result because it disagrees with the route you expected.
Compare responsibly with other players
Include the date when sharing a route, and say whether it came from your own attempt or someone else’s report. A screenshot can substantiate one moment, while a complete sequence requires more context. Leave missing steps marked as missing.
Personal records are also selective. You may remember dramatic failures more clearly than ordinary scenes, and players who post online may have unusual results. A journal is valuable because it reduces that memory problem, not because it produces a population-wide probability.
Use your completed record to decide what you want from the next session: explore a different branch, capture a missing detail, or simply enjoy the story. There is no need to present exploration as a solved formula for it to be useful.
Questions along the way
Can a run log predict which dragon I will get?+
No. It can preserve and compare your observations, but it cannot establish hidden rules from a small number of attempts.
Should an interrupted page count as a failed attempt?+
Only record failure when the game confirms it. Otherwise label the attempt interrupted or unknown.
Sources & evidence
Official sources establish the rules. Community reports describe individual experiences, not guaranteed outcomes. We have not independently tested game routes.
communityPlayer reports — choices and results, October 1–2, 2026communityPlayer reports — Dragon bonding megathread, October 2, 2026