If your run ends without a bond
Failure has been reported in Dragonkind. MoodReads’s own October 2 attempt ended with a dragon attack and a countdown. Follow the retry instruction shown in your game; a failed attempt does not tell you which single decision caused it.
Before leaving the screen, note the time, the last few decisions and the wording of the result in your journal. Leave out account codes and personal details.
How long do you need to wait?
Use the countdown or retry time on your own screen. A captured timer from another player does not establish the full wait, the timer’s units or a rule that applies to every account.
If the game gives you a specific next-attempt time, add it to your journal entry. The journal shows time remaining on your device. It is a personal reminder and does not change or synchronise with the game’s cooldown.
A waiting screen or a loading problem?
| What you see | What to do next |
|---|---|
| A countdown after a result | Keep the displayed time and wait for the original game to allow another attempt. |
| A queue message | Follow its instructions in the existing tab. |
| No game window | Allow the popup or use the direct new-tab link. |
| No email code | Check the address you typed and your spam folder. Request a new code only through the original game. |
| A blank or broken page | Check your connection. Preserve any visible result before reloading the original game. |
Make the next attempt easier to compare
Give each run a short name and keep one note for each major decision. After the next attempt, filter your journal to failed or bonded runs and compare the relevant entries side by side on a wide screen.
Clearing site data can remove saved information. It is not a reliable cooldown fix. Export your local journal before changing browsers or clearing storage.