Pivot Mid-Run

What Counts as a Pivot

A pivot is a deliberate shift in your build axis or role allocation after the run started. Minor item tweaks are not pivots. Selling your heal-trigger plan because a relic offered shield stacking — that is a pivot.

Guildrun’s demo size makes off-axis rewards common. Roughly three hundred relics and one hundred eighty specializations mean you will often see tempting packages that do not match your opening plan. The question is not “is this cool?” but “can I converge before difficulty catches me?”

Role pivots are subset of axis pivots. You might keep heal triggers but move your healer archetype into frontline tank gear because relics convert overheal to shields. The team still heals; the healer’s job on the board changed.

Signals You Should Pivot

Signal one: your main trigger fires inconsistently. If your on-hit engine never reaches critical mass by fight four, continuing is often slower than switching to a relic that already dropped and matches your items.

Signal two: a run-defining relic appears that points away from your plan but doubles your current stats if you lean in. Take the relic, then shop heroes and specs that activate it — not the other way around.

Signal three: Lovers pairing offers a partner that completes a stronger axis than your current duo. Breaking an old pair hurts emotionally; losing the run hurts more.

Signal four: repeated close losses on the same encounter type — swarms, burst bosses, backline divers — mean your axis lacks a counter package. Pivot flex slot or role assignment before changing everything.

• Low trigger uptime after mid-run
• Run-defining relic off-axis but high ceiling
• Lovers partner completes stronger synergy
• Repeated losses to same encounter pattern

Signals You Should NOT Pivot

Do not pivot because one fight went badly due to placement. Fix hexes first. Do not pivot with only two fights left unless the new plan wins immediately. Do not pivot into an axis that requires a hero you cannot shop for.

Do not pivot twice in three fights unless you are learning in low difficulty. Double pivots scatter gold and specialization progress. Finish one turn before steering again.

Do not pivot because a content creator’s build looks flashy. Their axis started on fight one. You are mid-run with different items. Compare structures, not screenshots.

Role Pivot Patterns

Healer to tank: take shield or overheal relics, move healer forward on hex grid, itemize health and mitigation instead of healing power. Triggers may still be heal-based while role on board is frontline.

Support to carry: stack amplification items on the support archetype once a relic converts buffs into damage or attack speed. Protect them with tanks until they scale.

Tank to controller: swap item priority from raw health to debuff or slow effects when relics punish enemies that attack the tank.

Ranged to melee: rare but possible when items grant lifesteal or dash on kill — reposition aggressively and accept aura changes.

These patterns use archetypes, not specific hero names, so they apply across the twenty-five hero demo roster.

Using Save Mid-Run to Learn Pivots

Save before accepting a pivot relic or buying the hero that completes the new axis. Run the next fight. If loss rate improves, commit. If not, reload and try a smaller adjustment — placement, one item, specialization upgrade.

This is the fastest way to learn pivot timing without burning twenty-minute runs. Guildrun’s save feature is especially valuable here; treat it as a lab, not a crutch.

Document outcomes: “Pivot at fight five to shields — survived two more waves.” Patterns emerge quickly across a handful of saves.

Recovering From a Bad Pivot

If you pivoted wrong, you may still recover by re-committing to whichever axis has the most items and spec text supporting it. Roguelikes reward partial honesty — stop buying for the fantasy, buy for the inventory you have.

Sometimes recovery means selling down to three heroes mentally — stop funding the flex entirely and stabilize anchors. You can still complete standard runs on lower difficulties with a scrappy third axis if placement and survival are fixed.

For preventing bad pivots, strengthen upfront planning in how to build in Guildrun. For encounter pacing context, see how to play. For endless-specific pivot math, see endless mode.

Pivot Decision Tree

Step one: identify remaining fights and current win condition. Step two: score the new axis by trigger frequency with existing inventory. Step three: estimate gold needed to shop missing pieces. Step four: pivot only if convergence before boss or endless wall is plausible.

If step four fails, take incremental power on your current axis even if boring. Boring wins runs. Flashy pivots lose demos.

Guildrun from Leyline embraces autobattler experimentation with Hearthstone and The Bazaar DNA — tight economies, big swings. Pivots are those swings. Make them deliberately.

• Count fights remaining before pivoting
• Score new axis against current inventory
• Save before committing gold to pivot package
• One pivot at a time unless on learning difficulty
• Recover by re-committing to strongest existing axis if wrong