Triggers in Dungeonbound resolve inside the single attack action that swept the board, in the order the sweep physically reached the pieces. The first item reached fires first, so placement is what controls trigger order: put the piece whose damage you want to land before the trigger that buffs it, and put crowd-control triggers early so the debuff lands before the damage piece resolves.
Dungeonbound grid trigger order: the sweep decides
Every attack makes a full lap around the hero's board and fires every item it passes. There is no separate trigger phase and no priority list — the geometry of your board is the priority list.
Two consequences follow directly:
- Order the debuff before the damage. Effects that modify the attack itself, such as a debuff applied to the target, must land before the damage part of the action. Control pieces belong earlier in the sweep path than the big hitters.
- Place what you want first, early. If you want a damage piece to land before a retaliation trigger, put the damage piece closer to the start of the sweep.
Since v0.1.51, area-of-effect swings in the incremental mode spread item statuses to every foe they hit, so a status piece placed early in the sweep can tag the whole enemy rank in one action.
The layout rules that decide what the sweep reaches first are in the backpack layout guide.
On-trigger items re-fire from other effects
An on-trigger item does not fire from its own attack — it fires from other effects. Echo Stone makes adjacent on-trigger items fire an extra time, which is the classic way of duplicating a trigger chain, and the Grinding Stone grants bonus attack per adjacent weapon.
That is why adjacency is not decoration. An Echo Stone next to a status-applying item doubles that item's application, and the Grinding Stone next to your main weapon converts a placement into a damage multiplier.
Rogue-style multi-trigger and enrage builds rely on the same ordering rule: more triggers per attack means more chances to fire the chain that was placed in front of them.
Status ticks ignore the sweep clock
Status effects do not wait for the sweep to finish. They run on their own timers:
- Poison ticks every 3 seconds.
- Burn ticks after 1.5 seconds.
- Stun locks the target out for 1 second once 3 stagger stacks have built up.
So a poison piece that lands early in the sweep does not resolve early — its first tick comes on its own clock regardless of where the piece sits. This matters when you are comparing a fast trigger loop against a slow damage-over-time ramp: the two run on different clocks entirely.
The full set of effects and their timers is in the status effects guide.