Black and blue dragons
Both colors are possible. Seeing one during a run, surviving its encounter and bonding are separate events.
Encounter does not mean bond.
A shared path does not promise this result.
- Choices
- Encounter
- Outcome
Can you get a black or blue dragon?
Yes, all dragon colors are possible. A run that encounters one without bonding does not make that color unavailable. Equally, a screenshot of someone else’s successful bond does not give you an exact recipe or a success rate.
Use the dragon types guide to read a result and the tail comparison to keep its color and tail separate.
No black or blue option on your screen?
Use the choices actually offered in your run. If a shared route mentions a shadow or another option you cannot see, do not substitute it or assume that the missing prompt is a browser fault.
| Your screen | What it tells you | Useful next step |
|---|---|---|
| The shared option is absent | Your current prompt does not offer that choice. | Record the options you do see; continue with one that exists. |
| You meet a black or blue dragon | You reached an encounter, not yet a confirmed bond. | Keep the encounter and next choice separate in your notes. |
| The encounter ends in death | This attempt did not end in a bond. | Use the wait displayed in the official game before retrying. |
| You receive a bond result | The result identifies the dragon you bonded. | Copy the displayed details into your bond notebook. |
Use the run journal to compare earlier prompts as well as the final choice. A missing option alone does not establish that a color is unavailable or that a particular earlier answer will unlock it.
What are you trying to figure out?
| Your situation | What is known | Next step |
|---|---|---|
| I want to see a blue or black dragon | The author confirms all colors are possible, but publishes no guaranteed route or odds. | Follow the choices shown in your run; compare reports only as individual examples. |
| I met one but did not bond | An encounter and a bond are separate outcomes. A death does not prove that color is unavailable. | Record the encounter and last choice separately. |
| I want to test whether a path worked | One result cannot isolate the effect of a route, battery level or opening scene. | Log the choices, encounter, outcome and any screen wording across attempts. |
| I need the next attempt reminder | After a death, the wait can be a few hours; use the wait actually shown in the game. | Set the local retry reminder from that screen. |
Use the path report finder to compare examples by outcome, then use the private run journal for your own evidence.
Compare player reports without treating them as a recipe
Recent community reports describe very different counts: some players have not seen the shadow after many attempts, while others report a blue bond only after repeated encounters. Every dragon color and tail type is possible; no published odds or guaranteed route are provided. Use this finder to locate the kind of report you need, then keep your own attempt separate. The latest bonding thread adds more no-shadow reports alongside blue encounters that ended in burns and successful bonds, without establishing shared odds.
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.
The community also collects attempts through an anonymous, one-run-per-response form and route sheet. Its contributor asks for varied routes and warns that copied answers, uneven submissions and inconsistent rows can distort percentages. Our local run journal helps you review one attempt before sharing it; compare community rows as observations, not official odds.
| What the player reported | How to read it |
|---|---|
| 93 runs in a spreadsheet; roughly 110–120 attempts overall | A personal log and an approximate total, not a complete published dataset. |
| 14 Blue appearances among 38 runs they considered eligible | Counts from that player’s route categories. They do not estimate your chance of seeing or bonding a Blue. |
| Different opening encounters appeared to change which routes worked | A player’s evolving interpretation; it does not establish a universal unlock sequence. |
This is one community account, not a controlled test. See the source notes for the underlying player discussion and official guidance.
For your own records, note whether you saw a color, survived the encounter and bonded; those are different outcomes. The local run journal keeps your choices and results on this device.
Black-hunt logs and the new-account theory
A player in the current bonding megathread logged repeated Black searches over about a week, ending at at least 39 failed attempts in that account of their run. In the same thread, another player suggested a clean first run to the tree on a brand-new account might improve Black sightings. These are separate player reports, not a comparison study.
| Report | Evidence boundary |
|---|---|
| A dated log rose from at least 22 to at least 39 failed Black attempts | Shows one person kept updating a failure count; it does not measure everyone’s odds. |
| A new-account first-run theory was proposed | The author described a few sightings across email accounts, but did not compare matched runs or rule out other differences. |
| The megathread’s form contributor said available data did not support account, time or squad assignment effects | This is a community-data caveat, not an official explanation of the game’s algorithm. |
Do not create extra accounts or change emails based on this theory. Record your starting context, choices, encounter and outcome in the private run journal.
Does battery percentage decide the color?
Battery-percentage tips conflict. A recent Blue-bond video describes seeing a Blue at about 98% and 60% phone charge, and while playing on a plugged-in computer. That is one creator’s recorded experience, not a controlled test, but it gives you no reason to drain your phone for a result or interrupt a run to hit a particular percentage.
All dragon colors and tail types are possible. If you compare attempts, record the actual choices, encounter and outcome in the run journal. One successful attempt cannot distinguish a battery effect from other differences. Keep the video’s limits in mind when comparing player reports.
Did a certain question produce the Blue?
A recent video comment asks whether Blue always appears after the same questions; another viewer says two questions in that video helped them bond one. Treat both as reports to compare, not a repeatable answer key. Record the exact prompt, your answer, whether a dragon appeared and whether the run ended in a bond. If the next run differs, keep both records instead of rewriting the earlier one.
| Observation | What it supports | What it cannot establish |
|---|---|---|
| Blue appeared after a recorded choice | That prompt and encounter occurred in that run. | That the answer always triggers Blue. |
| A later choice ended in a bond | The player reached a bond in that attempt. | A universal route, odds or causal rule. |
| Another attempt gives a different result | The outcomes differ across those recorded runs. | That either record should be discarded. |
Compare the existing outcome-labeled player reports and keep your own sequence in the private run journal.
What about a guaranteed answer path?
A route can help you understand a branch, but shared answers can lead to different outcomes. Read the answers guide before copying a path. Keep your screen’s wording in view and do not substitute an answer that is absent from your run.
If you die, use the official wait and your retry reminder. Avoid treating another email address or a cleared browser session as a confirmed shortcut to a new color.