Choose Breath or Eggs as the core engine
The sourced cases separate into two well-supported families. Dragon Breath cases scale a spell-casting engine through dragon spell density, charges or repeat casting, Ride Drake, and supporting effects, while Wyrm Egg cases build a summoning engine around egg production, minion scaling, egg spell-casting, and space. Both families appear in more than one pre-main player run. They are alternatives with different startup needs, not one shopping list that should be purchased together automatically.
Choose by the earliest coherent loop the current rewards can support. For Breath, ask whether another purchase increases usable casts, a confirmed dragon-linked payoff, or survival while casting; for Eggs, ask whether it improves reliable production, useful minion behavior, or room to hatch and act. A rare vault or shrine may radically change the answer in one seed. The official store supports open spell and equipment combinations, but it does not publish a dragon recipe or tier.
Build Dragon Breath around repeatable casting
Two independent pre-main sources describe a Dragon Breath direction. A July full-run video connects Dragon Breath to increased charges, a larger set of dragon spells, Ride Drake auto-casting, several drake types, multicast, and other supporting equipment, while a July Reddit report pairs Dragon Claw and Dragon Breath before adding inexpensive dragon spells. The common lesson is spell density plus repeated use and support, not any exact historical number. Every present charge count, cost, resistance, or trigger remains 待确认 until checked on current main.
Use a five-part Breath checklist: access to the core cast, a confirmed way to extend or repeat it, dragon-tagged pieces that actually feed the payoff, protection during setup, and coverage for resistant targets. Ride Drake may belong when its current wording reinforces the loop, but it should not replace a plan for the wizard’s safety. Adding every dragon-named spell can consume resources without improving the trigger chain. Prefer confirmed connections over theme purity.
The Reddit author reports completing a run on only a second attempt, but also emphasizes unusually favorable vault or shrine rewards. That makes the post evidence for a successful historical case and for the importance of RNG, not for a stable beginner opening. The video likewise reaches and reviews the Mordred segment, yet its exact values are tied to a July build. Neither source provides a current win rate or controlled comparison against Egg, Void, or Storm routes.
Build Wyrm Eggs around production and space
The pre-main Japanese victory log starts by saving resources to acquire Wyrm Egg, then reports support from crafted equipment, Dragon Hunter's Sigil, Ride Drake with Flight of Dragons, spell-casting support, and Evasive Maneuvers for defense. The author reports a Mordred completion, but the claimed production loop and precise costs need a current check. This is a player-reported route with one run’s drops and decisions. Its strongest transferable lesson is to budget for startup and defense instead of buying only egg payoffs.
An August 27 full-run video sets the goal of producing many Wyrm Eggs and letting eggs cast their own spells. The player follows dragon, fire, ice, egg-spell, and crafting-tag connections and deliberately declines a tempting turn toward a separate ice build. That choice illustrates coherence: once the egg engine exists, unrelated power can weaken the intended loop by consuming scarce resources. The upload is four days before the main merge and is conservatively labeled pre-main.
Use an Egg checklist of transition, generation, scaling, casting behavior, space, and defense. The transition piece must keep the wizard alive before production starts, while generation and scaling must be confirmed by current tooltips. Space matters because bodies that cannot hatch, move, or reach useful targets may not convert investment into control. Ride Drake or Flight of Dragons can be evaluated as support only after verifying their changed post-patch wording and cost.
Keep Void and Storm as lower-evidence branches
The broader builds discussion contains player-reported Storm Drake and Dragon Mage ideas, and a commenter calls a Void Drake route especially strong. The official patch notes also describe a changed Void Mutations progression interaction, which proves that the mechanic was actively revised. These sources establish possible branches worth inspecting in the client. They do not supply a current systematic guide, replicated completion set, or basis for calling Void or Storm best.
Treat these branches as pivots when the run offers their confirmed tags and support. Write down the trigger, startup condition, defensive gap, and resistance coverage exactly as for Breath or Eggs, then compare how many existing pieces transfer. If the route depends on a historical tooltip or one commenter’s superlative, label that dependency 待确认. A promising branch is not a tier placement.
Apply the Aug. 31 boundary
The August 31 Patch Day notes directly changed several dragon-related systems. They altered Void Mutations, multiple Wyrm Egg upgrades, Frostfire Hydra, Flight of Dragons, and Dragon Roar behavior, which makes earlier costs and sequences unsafe to copy. The notes provide a dated official diff rather than a complete post-main build database. This guide therefore names affected mechanics but does not freeze patch-day values as permanent facts.
Before committing resources, open the current tooltip for the exact spell, upgrade, or item and verify its cost, trigger, tags, and recipient. Check whether repeated casts work as expected, whether egg support reaches the intended minions, and whether a defensive interaction still uses the same ordering. If the game client and an older run disagree, follow the client. Current complete tooltip data is 待确认 outside that direct check.
Separate lucky runs from reproducible guidance
Rare vault and shrine rewards can make one dragon run assemble unusually quickly. The first-time Reddit player explicitly describes the Dragon Breath success as lucky, so the case should teach opportunity recognition rather than promise the same opening. The egg reports likewise depend on particular crafts and support pieces. Record which part of a success came from the engine and which came from an exceptional reward.
Several questions remain unresolved in the evidence. There is no current official dragon guide, post-main systematic comparison, same-seed test, verified ranking, or complete live-tooltip dataset. Avoid converting one Void claim or a lucky Breath run into a tier, and keep the repeatability of every player-reported route 待确认. A sound current plan is to choose a coherent engine, verify live tooltips, preserve defense and coverage, and pivot when the rewards support a better-connected route.