Turn the six slots into a concrete purchase decision
The Frostfire Hydra setup gives the framework a specific main-branch example. Establish the base summon, then choose Hydra Regrowth for 4 SP if surviving Hydras need recovery, or Double Dragon for 3 SP if you need another body and have room for the symmetric summon. Both upgrades together cost 7 SP beyond the base spell and defensive tools; the base spell price must be read in the client because the official patch does not publish it.
Trace the loop before buying more support: the permanent Hydra attacks with Fire and Ice, surviving damage allows the per-turn full heal from Regrowth to matter, and Double Dragon expands the number of bodies. Losing the Hydra in one attack breaks the healing loop; losing the wizard breaks the run regardless of minion health. The linked plan includes the placement check, a lower-budget choice, the 9 SP Orochi alternative and a beta-only Flight of the Dragons fix that should not be assumed on main.
For slimes, use the split and trigger checks before copying a historical combo. This is particularly relevant to Slimebirth Cantromancy and to Slime Drake with Dragon Mage, where the official October beta notes identify a caster-sacrifice bug. Keeping the branch and the first failed event visible gives a more actionable next purchase than adding another thematic spell.
Define a build as an engine
A build is not merely a list of spells that share a theme. Start with a core action, identify what triggers from it, show which attributes improve the resulting effects, and state what resource or board condition is required to begin. Then add protection against the situations where that loop cannot start or cannot affect the target. This engine model matches the official promise of new spell and equipment combinations each run better than a fixed class loadout.
Connect attributes, bonuses, and tags
The developer-recommended teaching video separates build reasoning into attributes, bonuses, and tags. A bonus helps only an attribute to which it applies, while tags describe the scope that can receive the bonus. Adding a tag can therefore open another support path, but only if the current tooltip confirms the interaction. Do not assume two effects synergize because their names sound related or because an older video showed a particular value.
Fill six functional slots
A practical build sheet has six jobs: core action, trigger chain, scaling coverage, startup resources, mobility or defense, and resistance coverage. One spell or item can fill several jobs, and that compression is often more useful than adding another isolated payoff. The sheet also exposes what is absent before a difficult rift makes the absence fatal. It is a planning tool, not a claim that every successful run uses exactly six purchases.
- Core action: the cast, summon, movement, or other repeatable event that begins the loop.
- Trigger chain: the effect that converts the core action into damage, bodies, control, healing, or further casts.
- Scaling coverage: the confirmed attributes, bonuses, and tags that reach the important outputs.
- Startup: the charges, health, components, positioning, or turns needed before the engine becomes useful.
- Mobility and defense: the answer when enemies threaten the wizard before the loop resolves.
- Resistance coverage: an alternate type, debuff, control effect, or summon for a poor matchup.
Review the six jobs before and after every major purchase. If startup is already slow, another long-horizon scaling piece may be worse than a tool that buys one safe turn. If one resistance stops the whole loop, more same-type damage does not repair the problem. No source supports universal thresholds for how much coverage or defense is enough, so those exact breakpoints remain 待确认.
Read player builds as dated cases
The June builds discussion reports several different engines, including Flesh Fiend and Devour, Slime Bounce with Annihilator Staff, Storm Drakes with Dragon Mage, summoned blades, and fire-enchantment ideas. These are pre-main player reports and demonstrate variety, not a ranking or guaranteed recipe. Claims such as “strongest” or “clears the whole run” belong to individual commenters and have no controlled sample behind them. Use the list to learn how players connect triggers, then confirm every component in the current client.
The July Flesh Fiend guided run is also pre-main and shows a more useful analytical pattern. Its author starts with Flesh Fiend and Devour Flesh, connects blood-related casting and recovery, looks for cross-tag support, and openly notes startup demands and turn-efficiency weaknesses. That makes it a case in core loop, startup condition, shortcoming, and patch rather than a current exact recipe. Its historical numbers and precise life or charge cycle are 待确认 after the main merge.
The September 12 report is explicitly post-main and describes a player changing direction after an initial Slime Striders idea. The later engine used Sorcery boots, a step-triggered burst, an Earthquake upgrade, and movement or quickstep support, while the player reports losing once to positioning and succeeding on a second attempt. This supports the lesson that movement, defense, and failure correction belong inside build design. It does not establish that the route is foolproof, best-in-slot, or reproducible across seeds.
Pivot when evidence breaks the plan
Pivot when the run cannot supply the startup piece, the next rifts expose a hard resistance, or a new component creates a cleaner trigger chain. A pivot does not require discarding everything; preserve pieces that still fill a functional slot and replace the disconnected assumption. The official open purchasing and crafting structure makes this incremental adjustment part of normal play. Chasing a named build despite missing drops turns a learning template into a brittle prescription.
Diagnose failure by the broken link
When a build fails, locate the first broken link rather than labeling the whole idea weak. A slow start points to resources or setup turns, an immune target points to coverage, repeated exposure points to mobility or defense, and empty charges point to uptime. A component that never appears is a routing constraint, while a component that appears but adds no value may reveal a misunderstood tag. This diagnosis produces a concrete change for the next run.