Guildrun
Systems Guides · Demo 0.5.1

Guildrun Stall Explained

A direct explanation of Stall as a delayed combat trigger, which heroes use it, which timings matter, and why stall teams fail before payoff.

AuthorFrontline PathfinderMaintainerGameplay EditorUpdated2026-08-04
Guildrun stall guide image for Pimenta and delayed Stall trigger teams
Opening plan

The plan in three moves

  1. Read Stall as a delayed combat threshold, not a button you press.
  2. Protect the board until the first useful Stall timing actually resolves.
  3. Use Stall Certainty, shields, taunts, and healing only when they solve the next fight.

What stall means

In Guildrun, Stall is a delayed combat timing condition. When a hero, specialization, relic, or modifier says After Stall (15), it is asking the board to survive long enough for that delayed threshold to matter. It is not a manual cast button and it is not the same thing as playing slowly in the shop.

The exact implementation can move with Demo patches, so use the in-game wording first. In the current local Demo 0.5.1 data, Stall appears as timed thresholds such as 10, 15, 20, 30, 35, 40, 50, and 60 seconds, plus wording like On Stall trigger.

Simple definition

TermPractical meaningHow to read it during a fight
After Stall (10)A first delayed payoffThe board must avoid early collapse.
After Stall (15)Common sustain or damage breakpointPimenta, Pollen, and Irini start showing value here.
After Stall (20)Mid-fight conversion pointGrace resurrection, Pollen poison boost, Aria scaling, and several crit/shield paths become relevant.
After Stall (35)Deep survival breakpointSecond Wind can fully heal and refill mana, but only if the holder is alive.
On Stall triggerPayoff when a Stall checkpoint resolvesRepeated trigger wording rewards multiple Stall thresholds or faster trigger access.

Why stall matters

Stall is valuable because it converts time into stats, shields, healing, taunts, debuffs, or mana. That makes it strongest when the team already has a reason to survive longer: a poison cloud ticking, a shield engine scaling, a back-line mage channeling, or a tank gaining permanent defense.

The trap is obvious: a delayed payoff does nothing if the fight is already lost. Before buying a Stall modifier, watch the first 10 seconds of the failed combat. If the carry dies, the support is targeted first, or the tank never receives pressure, you have a formation problem before you have a Stall problem.

How stall works in practice

A reliable Stall plan has three parts: a front line that owns first contact, a payoff that activates at a known timing, and enough damage or debuff conversion to finish the fight after the delay. Surviving for 40 seconds without a kill plan is not a win condition.

Trigger or setup conditions

Hero or modifierStall hookUse case
PimentaPepper Spray gains HP/S after Stall (15)Front-line poison tank that rewards enemies staying inside the cloud.
PollenSanctuary heals after Stall (15), then upgrades at 20 and 40Mystic sustain field for poison, shields, and longer fights.
AriaThe Crescendo gains Magic on Stall trigger and upgrades at 20/40/60Back-line Mage scaling if the team can protect the channel.
RowanHearty gains HP/S after Stall (10)Defensive anchor for Tank and Vanguard teams.
GraceSalvation can resurrect after Stall (20)Late-fight recovery when the team can avoid immediate wipeout.
Stall CertaintyStall abilities trigger 6 seconds fasterBackup acceleration for Tank, Mystic, or Mage paths that already have payoff.
DistractionTaunts at Stall 10/20/30/40/50Repeated enemy control when the tank can survive being targeted.

Common stall mistakes

  • No early contact control. If the wrong hero is hit first, your Stall timer is irrelevant. Fix formation before buying another delayed modifier.
  • No payoff density. One Stall keyword on one hero is not a team engine. Pair tanks, Mystics, shields, poison, or Mage scaling so the timer creates multiple values.
  • No damage conversion. Pollen and Pimenta can keep a fight alive, but the run still needs a way to kill priority enemies.
  • Wrong mode timing. Red Rift punishes deaths. Endless rewards scaling. Do not use the same greed level in both modes.

How to build a Stall team

Start with the first death. If the board dies before 10 seconds, buy immediate durability or reposition. If it reaches 15 seconds but cannot finish, add damage conversion. If it reaches 20 seconds and stabilizes, then deeper Stall triggers become realistic.

Board needBetter Stall answerConnected page
First contactPimenta, Rowan, Skorn, or a true tank laneClass data
Team sustainPollen, Gustav, Grace, Shield Formation, Protective MagicShields
Delayed damageAria, Irini, poison stacks, Burn or Frost absorptionStatus effects
Mode pressureSafer pivots for Red Rift, scaling for EndlessFight modes

For a full run context, use the strategy guide. For exact stat rules, use the stats page. This Stall page should answer the mechanic quickly, not replace every hero dossier.

Common mistakes

  • Building for Stall while the frontline dies before 10 to 15 seconds
  • Buying Stall pieces without a payoff hero already active
  • Ignoring target access because the team survived longer
  • Stacking delayed modifiers in Red Rift before stabilizing deaths
  • Treating every Stall number as equal when 10, 15, 20, and 35 seconds do different jobs