Dragonkind quiz answers and paths
A shared answer list can help you recognize a branch. It cannot promise that your run will encounter or bond the same dragon.
- Read the prompt
- Match the branch
- Record your choice
- Record the result
Which answers should you choose?
Choose from the options the game actually gives you. Treat another player’s route as a description of their attempt, not a universal answer key. If the prompt or encounter differs, the list has stopped matching your run.
Dragonkind’s Threshing choices are also different from an unofficial personality quiz. A fan quiz can assign a playful dragon result, but it does not create a bond in your official account. To begin the actual game, follow how to play Dragonkind.
Find a report that matches your run
Start with what appeared on your screen, then compare the reported encounter and ending separately. The reports below are individual attempts; they are not a guaranteed answer key.
Player reports · not game rules
Find a black or blue report
Search what happened in another run. Each card keeps the encounter and the final outcome distinct; route details stay closed until you open one.
Blue encounter and bond reports are different outcomes
Recent replies in the same Reddit megathread disagree on what happened after a blue appeared. Compare sightings, encounters and bonds separately before borrowing anyone’s route.
| Reported outcome | What players described | What it supports |
|---|---|---|
| Community route-form sample | The megathread contributor links an anonymous form for one attempt per response and asks players to log varied or random routes, not only copied paths. | A self-selected spreadsheet can help compare reports, but inconsistent entries and route-copying bias mean its percentages are not official odds. |
| Blue appeared; bond did not happen yet | One player says they had found blue four times and were still trying to bond it; another describes seeing blue several times and being burned each time. | The thread separates seeing blue from bonding it. |
| Blue sightings followed by a bond | One player estimated 150–200 attempts overall; after switching routes, they reported five blue sightings in eleven attempts and bonded on the fifth blue encounter. They also said the same answers had led to deaths before. | One player's sequence, not evidence that the route caused the sightings or bond. |
| Blue bond reported after a different route | Another player describes a blue bond after many attempts and a fourth blue encounter, after trying varied paths. | Different self-reported timelines; not a spawn or success rate. |
| No shadow after many attempts | Some players report no shadow after 100 or even 200+ runs; another player says a shadow appeared on a first run with a new account. | Contrasting accounts do not establish an unlock condition or encounter rate. |
| Black search and account age | In a recent megathread update, one contributor said newer email accounts seemed to encounter Black more often; another player logged 28 failed attempts before continuing the search. | The contributor explicitly called this a correlation with unknown causes, not an account rule or measured rate. |
| Black bond after a new-email run | One player reported bonding Black after starting a new email and using Safari private browsing, while saying they did not know whether private browsing mattered. Another commenter logged a new account followed by more failed attempts. | These separate accounts cannot isolate email, browser session, route or chance; they are not a reason to create accounts or use private browsing. |
| Blue bond after a long search | A player reported bonding Blue after roughly 250 incinerations. | A striking individual history, not evidence that attempt count unlocks Blue or predicts when it will appear. |
Keep your exact prompt, preceding choices, encounter and final result in the private run journal; a route comparison cannot establish odds or guarantee a bond.
Black bond reported after a new-email, private-tab run
One player described a Black bond after using a new email and Safari private tab, but said they could not tell whether the private tab mattered.
Reveal the reported route and its limits
This is one player's account, not a controlled comparison. A separate commenter reports creating another account and then continuing to log failed attempts. Neither report establishes an email, account-age or browser-session effect. Do not create accounts or change privacy settings expecting a dragon result; record the choices and outcome you actually see.
Shortened from the player’s description:
- Enter alone and head west toward the scream.
- Help the cadet, pause to assess, engage the smaller cadet and let the squadmate get revenge.
- Continue west, climb the tree and follow the shadow if that option appears.
- When Blue appears, lower your eyes and hold still; after it leaves, return to the cadet and wrap the burns.
- Continue south, face the threat and meet its gaze.
New Blue encounter routes proposed in the route megathread
A contributor proposed two additional routes to a possible meadow Blue and shared changing estimates from their route spreadsheet.
Read limits and source
Try these only as leads for a possible meadow sighting. The reported counts use uneven samples and can shift as attempts are added; seeing Blue still does not mean a bond. Record the exact prompt, whether Blue appeared, and the final outcome separately.
Newer-email Black reports and a Blue bond after about 250 failures
A megathread contributor noticed newer email accounts seemed to encounter Black more often, while another player reported bonding Blue after approximately 250 incinerations.
Read limits and source
These are separate recent player anecdotes. The account-age observation has unknown causes and does not establish an email or attempt-count mechanic. The Blue report does not show that failure count unlocks a bond. Compare your own encounter and outcome records rather than changing accounts based on this claim.
Several Orange bonds reported during Black searches
In a recent black-dragon thread, one player said Orange bonded on three separate attempts while they were trying for Blue or Black. A later reply described three more Orange bonds across different accounts and routes.
Read limits and source
These are separate player anecdotes. They show that a color encountered during a search can still end in a bond, but they do not establish Orange odds, an account or email effect, or a useful Black/Blue route.
Five Blue sightings in eleven attempts; bond on the fifth encounter
One player estimated 150–200 attempts overall. After switching paths, they reported five Blue sightings in eleven attempts and a bond on the fifth Blue encounter.
Reveal the reported route and its limits
The player says those same answers had also led to deaths before, and explicitly allows that the short streak may have been luck. It is a single account, not a controlled comparison, encounter rate or guaranteed route.
Shortened from the player’s description:
- Enter alone and head west; respond to the opening Brown or Green encounter as it appears.
- Continue deeper into the forest, investigate the scream, help the cadet and engage the smaller bully.
- Head east; at the Red encounter, the player says they first accepted, then changed their mind.
- Approach the Blue in the meadow if it appears. The player reports that the later bonding choices also failed on previous attempts.
One player reported getting both Blue and Black after a week of attempts
The player shared a sequence that reaches a Blue encounter at the tree, then returns to the cadet and continues toward a later Black encounter.
Reveal the reported route and its limits
This is one player's account after trying for a week. The comment does not say how many runs the described sequence took or show that these choices reliably produce either color. Treat the order as a report to compare with your own prompts, not an unlock recipe or odds estimate.
Shortened from the player’s description:
- Enter alone, head west, lower your eyes, investigate the scream, help your squadmate and assess the bully encounter.
- Let the dragons handle the smaller cadet, continue west, climb the tree and investigate the shadow if that option appears.
- Follow the shadow; when Blue appears, lower your eyes and hold still until it flies off.
- Return to the cadet, cut a piece from your sleeve and wait for the wing leader.
- Do not engage the later dragon; explore, turn toward what is behind you, hold your ground and look into its eyes.
No shadow sighting after many attempts
In the current bonding megathread, several players describe seeing no shadow after repeated runs; some separately report blue encounters that ended in burns.
Read limits and source
The thread also contains successful bonds and conflicting route claims. These comments show an active question, not shared odds or an official mechanic. Record whether a dragon appeared, whether the encounter continued, and whether the run ended in a bond.
No shadow sighting after many runs
One player estimated about 100 runs, had seen blue several times, and still had not seen the shadow; their blue encounters ended in burns.
Read limits and source
This is one player's account, not a measured rate. It illustrates why a missing shadow and a failed blue bond are separate observations. The author FAQ does not publish encounter odds or an unlock condition.
Blue appeared, then the attempt burned
A different player described finding a blue after several days, then being incinerated during that encounter.
Read limits and source
An encounter is not the same as a bond. Keep the screen choices and final result in your own journal; this report does not establish that its route is required or repeatable.
Blue bond after many attempts
One player reported bonding a blue after roughly 150 runs and a fourth blue encounter, after trying varied paths.
Reveal the reported route and its limits
The player shared a route after the result. Treat it as a spoiler and a single account, not a guaranteed answer. No published odds or guaranteed route are provided.
Shortened from the player’s description:
- Started alone and took an east/orange branch, then retreated.
- Investigated and helped; later chose the options they described as ‘even out’ and ‘end yourself.’
- Continued east into the valley, declined the red dragon and selected blue.
These are individual attempts, not controlled replays. Every dragon color and tail type is possible, but no published odds or guaranteed route are provided. A repeated answer path can still produce a different encounter or outcome.
When you finish comparing, save your exact prompt order in the private run journal. For the specific question of a black or blue encounter, continue to the color comparison and outcome table.
| Compare | Why it matters |
|---|---|
| Prompt wording | A similar-looking question may belong to a different situation. |
| Available answers | A missing option means the shared route does not match this screen. |
| Encounter | The same recorded choices may lead to another dragon or situation. |
| Final outcome | Encountering a dragon, surviving and bonding are different observations. |
Why one successful choice is not an answer key
A short report can omit earlier choices or stop before the final result. Compare only the actions it actually describes. Two accounts describing a similar encounter are not a controlled replay of the entire path.
Spoilers: two orange-dragon reports
| Report | Actions described | Reported result |
|---|---|---|
| Bond report | Told the orange dragon to stop; was allowed to climb aboard. | A successful orange bond. |
| Burn report | Told the orange dragon to stop; tried to climb after it lowered itself. | Was burned during the attempt. |
These reports do not establish that the earlier choices matched or explain what caused the different results. Treat the stop-and-climb sequence as an observation to compare, not an instruction that guarantees a bond.
Build a useful comparison
In the run journal, record the choices in sequence and the last visible encounter. Add whether the attempt ended in death or a bond. Avoid rewriting earlier notes to fit a result you hoped to get.
For color-specific claims, the black and blue guide separates battery tips from useful observations. If the attempt ends in death, use the retry wait rather than repeatedly refreshing the game. If you are unsure whether an encounter is finished, check the bond-or-burn result table.