Latest source review
We read the author’s public Dragonkind FAQ directly. It supports a broad wait after death during Threshing and explains that login codes are sent in batches. It does not supply a precise delivery deadline or an exact four-hour cooldown.
Our retry answer now cites that FAQ. The personal timer still has no preset and never synchronizes with the official game. Email help now distinguishes the author’s actual advice from general troubleshooting.
Read the author’s Dragonkind FAQs ↗Use the official-email checklist →Read the current retry answer →Three different kinds of claim
A named first-party source
We link the public page and date we read it. Its wording supports only what it actually says. “A few hours” is not an exact four-hour promise.
An individual observation
A person’s note may describe their own experience. It is not automatically verified by this guide, representative of other players, or proof that a choice caused an outcome.
A lead, not a rule
A repeated rumor or an unattributed route needs evidence. Reposting the same claim does not create independent observations. We do not offer guaranteed black-dragon routes or ways to bypass a wait.
Browser troubleshooting is a separate category of practical guidance. It can help compare symptoms, but it cannot diagnose your account or establish an official outage.
Inspect our sources and their limits →Keep two personal observations separate →Questions that stay open
How should I interpret a precise wait reported elsewhere?
Keep the source, date, units and context together. The official FAQ gives a broad duration. A personal countdown or a third-party screenshot cannot by itself establish one exact wait for every session. Follow the instructions your official session actually shows.
Use a reminder with your own duration →Can two attempts prove a route or a dragon probability?
No. Two recollections do not control for other factors, establish a representative sample or reveal the game’s rules. Our notebook compares what you wrote without turning it into a success rate, prediction or route recommendation.
Does this log announce future game features?
No. These dates describe changes to this guide. We have not verified a future feature-unlock date here. Follow a dated first-party announcement before treating a repeated date as confirmed.
Open the official experience ↗Guide change history
A reading room and a recoverable notebook
Added source search, dedicated email and result-reading topics, a tab-only outcome-context preference and a fictional notebook demonstration. Notebook backups now support previewed local restore and selected-note printing. This is a guide update, not a game-release announcement.
Local notes and clearer evidence
Added a private attempt notebook, two-note comparison and reviewed text export. Strengthened the low-spoiler entry guide and official-email checklist. No player records, success metrics or gameplay simulations were added to the public site.
Retry wording corrected to its source
Added the author’s actual FAQ as a source for the broad wait. The previous guide already avoided an exact preset; the update makes the available first-party wording explicit.
English and Simplified Chinese
Added full Chinese pages, a starting guide, saved reading and public-answer selection links. Those links contain public answer IDs, not private searches or personal notes.
Initial identity review
Cross-checked the official Dragonkind destination against the author’s link and published source-tracked starting questions.
This log is maintained with content changes, not automatically advanced by a build. We do not run live monitoring or accept public player submissions.
Check the complete source ledger →