Check splitting and level-one triggers before adding damage
Use the August 31 main-branch fixes to separate three slime problems. A summon that cannot appear, a bonus that does not reach a spitter and an event that never qualifies for a trigger need different responses. Run these checks on a small clear part of the board before expanding the historical routes above.
- Leave a valid place for a split. The patch fixed slimes losing half their HP when their split summon failed. A failed split still does not establish a new body, so inspect available space and the actual summon result before spending on more swarm scaling; the notes do not publish the split threshold or all placement rules.
- Read Slimebirth Cantromancy as a level-one-spell condition. The patch explicitly corrected text that said cantrips. Do not assume that a spell with another level qualifies merely because you use it as a cantrip; verify the qualifying spell level and whether the expected slime appears.
- Check the resulting unit, not just the wizard. The patch repaired Goo and Lava Spitter bonus inheritance and made Lava Spitter use Poison resistance rather than Slime resistance. Inspect the summoned unit's resulting attributes and its target's resistance when the damage seems wrong.
- Keep the Dragon Mage hybrid branch-specific. The October 12 beta notes fix Slime Chucker sacrificing its caster when used by a Slime Drake with Dragon Mage. If that hybrid loses its own caster, stop feeding the same trigger and verify your branch before blaming low minion health or buying extra slime generation.
A low-risk alternative while diagnosing the hybrid is to use a slime source that does not rely on that Slime Chucker interaction, with a separate damage spell for the target the swarm cannot handle. This is a troubleshooting choice, not a claim that another named slime setup has been tested to win. Exact current Slime Bounce costs and a complete post-main slime shopping list remain unverified; the Hydra example is the costed summon plan available here.
Choose a slime route before buying every slime piece
The evidence supports several distinct slime directions rather than one canonical build. A Japanese victory log contains a Gray Goo and Armor Melter route, a Reddit comment proposes Slime Bounce with Annihilator Staff, an older video centers Metal Slime Sword, and a September 10 video develops a slime-cantrip hybrid. These cases show that slime can be a core or a half-core in a completed run. They do not establish a tier list, win rate, or universal opening.
Choose the route by naming what creates bodies and what converts those bodies or slime effects into progress. Gray Goo focuses attention on slime presence and physical-resistance support, Slime Bounce emphasizes repeated sorcery interactions, Metal Slime uses summoning alongside another weapon engine, and the cantrip route uses slimes inside a broader spell-trigger chain. Do not blend all four simply because they share slime terminology. A route stays coherent when each purchase strengthens its trigger, scaling, uptime, or hard-matchup answer.
Use a generation-to-coverage skeleton
Start with generation, then decide which slime types or tags the run is actually trying to preserve. Add only scaling that the current tooltip confirms reaches those minions or effects, followed by propagation, splitting, charge support, or cantrip triggers that advance the chosen loop. Finish the skeleton with a non-slime answer for resistances, crowded positioning, or a boss-like single target. This sequence is a reasoning framework and not an exact purchase order.
- Generate: identify the reliable spell, equipment effect, or other source that creates the relevant slimes.
- Select: keep the slime types, damage types, and tags that serve the route instead of widening the pool automatically.
- Scale: verify minion attributes and inherited bonuses in the current tooltip before investing.
- Propagate: decide whether splitting, bounce, spreading effects, or triggered casts are the actual multiplier.
- Sustain: account for charges, setup turns, board space, and protection for the wizard.
- Cover: reserve a plan for resistances and concentrated targets that the slime swarm handles poorly.
Treat Gray Goo, Bounce, and Metal Slime as pre-main cases
The Gray Goo victory log predates the August 31 main merge. Its reported chain combines Gray Goo with Armor Melter for physical resistance, Emerald Flame for ignition, Slimeshot for spreading Slimefy and Lifedrain, and Red Majesty, but the author also says Icy Vengeance may have produced much of the actual clearing. That self-correction matters because it prevents attributing the result to Gray Goo alone. The run is evidence that a slime-centered package participated in a win, not proof of the package’s independent strength.
The Slime Bounce direction comes from one commenter in the June builds discussion. The player connects Annihilator Staff with Slime Bounce, additional bounces, and damage types, then recommends another answer for Mordred. This is a player-reported pre-main idea, and its claim about clearing most of a run is not independently replicated in this chapter. Copy the concept of repeated triggers plus separate boss coverage, while treating every exact interaction as 待确认.
The Metal Slime Sword video is older still because it predates the Early Access launch and the August 31 patch. It explores Poison Slimes, Slime Shot, slime counts, and a sword-summoning core, but later calls the finished result a slime plus dancing-blade run. That label makes it a hybrid case rather than a clean test of pure slime power. Its upgrades, resistances, summon counts, and strength claims must not be projected onto current main.
Label the Sept. 10 completion as a hybrid
The closest current case is a September 10 full run recorded after the main merge. The player originally aims for slimes that cast Death Bolts, uses Soul Charge and Death Cleave in the trigger plan, later adds Cantrip Cascade, and uses Vampiric Gaze with a slime upgrade. During the run, the player explicitly describes the result as hybrid and more cantrip than pure slime. The reported completion supports feasibility for that one assembled run, not a standard recipe.
Recheck every slime tooltip after Patch Day
The August 31 notes directly touched the slime ecosystem. They report a Vault of Slime rework, a new rare component, wording correction for Slimebirth Cantromancy, fixes to failed slime splitting, and corrections to Goo or Lava Spitter bonus inheritance and Lava Spitter resistance. The notes also changed Cantrip Burst, which matters when evaluating an older cantrip-adjacent plan. These are dated official changes, not permission to treat the patch-day values as timeless.
Diagnose dilution, resistance, and space
When the build stalls, check whether random slime selection diluted the intended composition. Then inspect whether physical, poison, or another relevant resistance blocks the main output, whether summons inherit the expected bonuses, and whether board space prevents useful generation or splitting. Finally, test whether the route has focused damage or control for a durable single target. These checks locate the broken part without declaring slime itself weak.