Find the answer you need.
Select a record. Its reported route remains hidden until you ask to see it.
Choose the encounter on your screen, reveal a reported route when you want it, and compare what players actually observed. Sources and uncertain outcomes stay beside the advice.
Search the words on your screen. Choose a result to see what is known; encounter choices stay hidden until you reveal them.
Select a record. Its reported route remains hidden until you ask to see it.
| Current branch | Reported encounter | Reported endings | Look up |
|---|---|---|---|
| Tree: descend slowly | Two greens in the meadow; an orange or brown may intervene | Bond or death reported; the final prompts matter | Slow descent |
| Tree: descend quickly | Red dragon, unless the player backtracks | Bond or death reported | Quick descent |
| Tree: additional shadow choice | Blue first; some reports continue to a black | Encounter can end in death, a bond or a continuing search | Shadow encounter |
| Center: first red encounter | A red dragon; some players pass it and reach a meadow | Accepting an encounter still does not guarantee acceptance | Center red |
| Meadow: orange and brown | Either named color in a reported clearing scene | Both successful and fatal choices reported | Orange and brown |
| Meadow: additional blue choice | A blue appears as another option in one mapped branch | Seeing blue and bonding are separate outcomes | Valley blue |
The comparison condenses a community map, with corrections from other players in the same discussion. Read it left to right: your current branch, the reported encounter, then the possible ending. A color listed under “encounter” is not a promised result. If your screen offers different choices, use the matching field note rather than forcing it into a branch that only sounds similar. The comparison covers reported branches, not every path through the game.
| Report | Choices or conditions described | Observed result | Limit |
|---|---|---|---|
| Tree report, 2 October | Travelled with others, went west, helped a cadet, continued into forest, found shadow | Blue departed; black encountered afterward | One player’s success; not a tested guarantee |
| Detailed report, 4 October | Went alone and west, helped a cadet, climbed tree, followed a shadow, stayed still for blue, then held black’s gaze | Player reported a black bond | Depends on receiving a shadow option; preceding choices not independently reproduced |
| Repeated-attempt reply, 3 October | Tried tree and clearing, varied company and earlier decisions | Reported 31 attempts without the sought luck encounter | Self-reported attempts; demonstrates why a success story cannot promise the same encounter |
If your tree prompt contains the additional shadow option, that is the scene described by several black and blue reports. If it does not, the published accounts do not establish a way to force it to appear. Players have reported success with different earlier decisions, including travelling alone and travelling with others. That disagreement is a reason to separate a recognizable encounter from an asserted prerequisite.
Some accounts describe a blue encounter followed by continued exploration and then a black. Others report seeing a blue and dying without bonding. Record the color you encountered separately from the dragon you actually bonded. A guide saying “this branch leads to blue” may be describing the scene rather than a successful ending. The field notes preserve that distinction so you can compare the next prompt in your own run.
These expandable notes work without JavaScript. The finder above uses the same source records. Three records cover general game problems; the other entries describe encounters. Initial sightings and later bonding tests have separate records. This page was reviewed on 5 October 2026.
A failed attempt does not end your chance to bond. The official FAQ says you can try again after a few hours and that there is no limit on attempts.
Use the wait displayed in your game to set a local reminder. Avoid treating one player’s timer as a universal rule.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Open retry journal →The official FAQ says all dragon colors and tail types are possible. It does not confirm a guaranteed black or blue route.
Compare reports with your own complete sequence of choices, but leave room for random or hidden factors until they are verified.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Read color guide →The official FAQ says codes are sent in batches and suggests checking your spam folder.
Check the address you entered and your spam or junk folder, then return to the official game for account-specific help.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Open login help →Players report both bonding and death around the two-green encounter.
Several players describe dying after indecision between the greens. Another describes choosing one, then holding ground during a tail swing and bonding with the other. Compare the exact test and choice; this account does not establish a universal safe response.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record this attempt →Players report a third shadow choice while climbing a tree. Its appearance and the outcome of taking it vary across reports.
If the third option appears, players associate it with blue and black encounters. Its appearance has not been shown to be forceable.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record this attempt →A player route map describes slow descent from the tree leading toward green dragons in a meadow. Reported outcomes differ.
A familiar route only identifies the encounter. Read the choices in this run; reports do not establish a guaranteed result.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record this attempt →A community route map places the slow descent before a meadow encounter. It describes several possible outcomes, including death.
Players report that two green dragons may be waiting in the meadow. Brown or orange dragons have also been reported during this encounter, so the path is not a color guarantee.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Explore meadow record →A community route map associates quick descent with a different encounter. Reports still include both success and death.
The map describes a red dragon on this branch. Treat that as a player observation, not a guaranteed encounter or bond.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record this route →Later test · a red dragon at the center, separate from an initial stalking sighting.
A community map describes a first red encounter after heading toward the center. A player can pursue that encounter or continue toward a meadow.
The detailed walkthrough reports accepting the red encounter and continuing the approach, followed by a successful talon test. It also includes fatal outcomes. Save the follow-up prompt; accepting the first encounter alone is not the full successful sequence.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Detailed community walkthrough ↗
Record this branch →Players describe orange and brown choices in a clearing, with both bonds and deaths. Match the colors and prompt before comparing this encounter.
One player reported death after chasing a brown indecisively and after turning away from an orange. Compare which dragon approached, whether you followed it, and what the next test asked. A death report does not establish that the opposite response always succeeds.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record this encounter →A player route map lists a blue appearing as a third option alongside the orange and brown meadow encounters.
The map identifies a possible encounter, not a guaranteed blue bond. Keep this valley option separate from the shadow branch reached by climbing the tree, and record whether you actually bonded or only saw blue.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record a blue encounter →Players have reported different results after choosing to help another cadet. The choice alone does not establish a safe route.
Record what happened before the scream and which follow-up action you chose. One player reported dying after helping, then bonding on a later run with the same initial choice.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record this route →Initial encounter · dragon behind you. Keep this separate from a squadmate encounter and a final bonding test.
Match the scene’s stage and companions before comparing outcomes. The map is a work in progress and contains untested branches.
The player map records continuing after lowering the eyes and turning to face it, or holding still. It does not establish a final bond from either response.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record this encounter →Initial encounter · dragon in front of you and another cadet.
Match the scene’s stage and companions before comparing outcomes. The map is a work in progress and contains untested branches.
The map reports continuing after helping the squadmate and death after standing on your own. Standing still is marked untested; its outcome must remain unknown.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record this encounter →Initial encounter · a red dragon is approaching. This is not the center-red bonding test.
Match the scene’s stage and companions before comparing outcomes. The map is a work in progress and contains untested branches.
The map reports continuing with eyes lowered and death after hiding behind a tree. These are route-map observations, not this site’s replay tests or a guaranteed response to every red.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record this encounter →Initial encounter · an orange dragon lands in front of the cadet.
Match the scene’s stage and companions before comparing outcomes. The map is a work in progress and contains untested branches.
The map reports continuing after lowering the eyes and retreating, and death after hiding behind a boulder. Keep this separate from the orange roar or claw test in the clearing.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record this encounter →Initial encounter · two greens are sunning. This is a different scene from the later two-green question or tail test.
Match the scene’s stage and companions before comparing outcomes. The map is a work in progress and contains untested branches.
The map reports continuing with eyes lowered while holding position. Approaching either green is marked untested. Do not infer that an untested choice causes death.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record this encounter →Cadet encounter · a follow-up choice after the initial decision to help.
Match the scene’s stage and companions before comparing outcomes. The map is a work in progress and contains untested branches.
The detailed wiki reports success after assessing and engaging the smaller opponent, and death after direct interposition. The initial decision to help alone is not a complete route. Players have reported different endings after helping.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Detailed community walkthrough ↗
Record this encounter →Tree shadow branch · a black dragon has appeared after the earlier blue and cadet scenes.
Use the encounter and follow-up prompt to match this report. The source is community material, not a verified official algorithm.
The black-dragon wiki relays a route involving helping a cadet, looking back, then holding the black dragon’s gaze without bowing. A complete independent success record was not located in this research. This is a candidate report, not a guaranteed way to produce the shadow option.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record the exact prompt →Tree shadow branch · blue encounter, separate from the meadow-blue option.
Use the encounter and follow-up prompt to match this report. The source is community material, not a verified official algorithm.
The blue-dragon wiki reports holding still and following the blue. Its stated successful-bond confirmation is a relay; the complete original sequence was not checked here. A blue sighting alone is not a confirmed bond.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record the exact prompt →Later clearing test · brown tail prompt, not an initial landing.
Use the encounter and follow-up prompt to match this report. The source is community material, not a verified official algorithm.
The detailed walkthrough reports mounting the tail and committing body weight in a successful account. It also describes a fatal indecisive chase. Compare the exact tail prompt and previous choices; one successful account does not make every brown encounter safe.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record the exact prompt →Later clearing test · orange roar or claw, separate from an orange landing in front.
Use the encounter and follow-up prompt to match this report. The source is community material, not a verified official algorithm.
The walkthrough contains successful roar and claw-test reports. A claimed link to earlier rescue choices is an association in its sample, not proof that rescuing is a necessary condition. Record which test appeared rather than combining the reports into one universal orange response.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record the exact prompt →Injury encounter · missing leg. Do not confuse it with a fight following a scream.
Use the encounter and follow-up prompt to match this report. The source is community material, not a verified official algorithm.
The original player PDF lists tourniquet, leaving, and taking weapons choices. The text extraction did not establish every arrow between those choices and their endings. Outcomes for the incompletely mapped connections remain unknown here.
Checked 5 October 2026. Community routes have not been replay-tested by this site.
Record the exact prompt →Try “green two,” “tree slowly,” “shadow” or “orange brown.” Each query word must match a record. Shorten a long query if there is no match. Selecting a result shows its title and evidence label; choices stay hidden until you reveal them. The same finder works on the homepage.
Officially confirmed refers to the author’s FAQ. Player reports identify community observations. Single report means one account. A community map can identify an encounter while remaining unverified as a repeatable route. Each field note links its source, so you can read the wider account before following it.
Use the retry journal to preserve the branch, encounter, response and ending. Keep wording consistent when two attempts match. The tool flags different outcomes for the same written scene and choices. Record “saw blue, no bond” separately from “bonded blue,” and keep earlier decisions that may distinguish the runs.
The Dragonkind game guide has a missing-code checklist. Its result-field reference explains names, tails and lineages. If you died, enter the game’s current wait in the retry timer. These actions do not require opening a route spoiler.