bloxlore Shards of Order
View on Steam

Combat Countdowns

A repeatable preview check for choosing the next card, confirming the response window, and recovering before an enemy action resolves.

Start here

Quick Guide

15-second route

Before playing a card, compare its preview against every visible enemy countdown; defend, delay, or interrupt when the priority enemy would act before your next answer.

Start from

A combat hand with every enemy countdown and the candidate card preview visible.

Before you start

Read the current enemy countdowns and compare how the candidate changes their displayed order.

Success looks like

The priority enemy is delayed or resolves into the defense prepared for it while the party keeps its response window.

Pending verificationEditor-adopted referenceChecked Steam release checked 13 Aug 2026

Route

  1. Read every visible enemy countdown before selecting a card and identify the action closest to resolving.

  2. Preview the candidate card and compare the displayed countdown changes across every enemy before committing it.

  3. Choose a defense, delay, or interruption when the preview shows the priority enemy acting before the party can answer.

  4. Commit an attack only when its preview preserves the party's required response window.

  5. Check every displayed countdown again after the card resolves because the timing order has changed.

Extra tips and limits

TipWhat to do
Tip 1Combat has no conventional turn rotation: each card advances time while enemy actions count down. Threat selection, card cost, positioning, and retained responses determine whether an action is safe.
Tip 2Card costs move the combat clock, redraws also consume time, and a position swap costs one time. Use Weakness, defense, or movement only when it makes the next dangerous countdown survivable.
Tip 3Read timers before acting, preserve defense for unavoidable damage, interrupt the highest-impact action, and attack during a safe window. Keeping one flexible answer is often stronger than emptying the hand.
Tip 4Visible enemy timers replace ordinary turns. Delay and interruption buy time for damage or longer combinations, but every added shared-deck card changes how reliably those answers can be drawn.
Tip 5Named enemy effects remain partly unconfirmed. Audio and trailer tension may locate possible threats but do not prove mechanics; use an ability only after current gameplay or official material shows its name and result.

Current selection catalog

memberrolebestUseboundary
Threat scanFirst decisionCompare every visible countdown, action impact, target position and possible overlap before playingThe shortest timer is not automatically the most dangerous action
Card timeClock costCompare the printed time cost with the countdowns that will reach zero during the sequenceA strong effect is unsafe when its cost lets a lethal action resolve first
RedrawClock costSpend the reported three time only when no current card can neutralize, survive, postpone or escape the imminent actionDo not redraw merely to improve a hand that already has a safe line
Position swapClock costSpend the reported one time to move a fragile hero out of the targeted position or put a durable hero thereConfirm the enemy intent before the swap advances the clock
WeaknessMitigationReduce an unavoidable hit enough to make the next damage, healing or setup action safeUse direct defense when Weakness still leaves lethal damage
DelayControlPush a high-impact action far enough back to draw, heal, set up or finish the enemyDo not spend delay on harmless pressure while a larger action remains active
InterruptControlHold premium interruption until the dangerous action and its timing are confirmedUse cheaper protection or ordinary attacks against routine pressure
Safe windowDamage timingBuild Rage, colored mana or quiver order only after the next attack is controlledStop a long sequence when a new urgent countdown appears
QuiverExile setupRead stored arrows in their displayed order and fire before a full quiver forces an unintended targetMore arrows are not automatically better
Healing BellLimited recoveryUse a full-party refill when broad damage, a boss approach or slow card healing makes the breakpoint valuableTreat the limited supply as route planning, not routine recovery
Shared deckDraw consistencyCenter the party on one damage plan with compact defense, control, cycling and recovery supportEvery unrelated reward makes the next required response harder to draw
Low-cost lethalFinishRemove an enemy about to act with the cheapest sufficient optionDo not advance the clock further for unused damage
Boss phaseReassessmentPause the current combo, reread all timers and learn the new action orderOld timing assumptions may fail after a phase change
Law changeReassessmentReview timing, card roles and emergency responses after restored world rules changeRemove cards whose old interaction no longer supports the shared plan
Failed fightRecoveryFind the first missed countdown decision and change that response before adding damageRepair the earliest timing failure, not the final visible collapse
Unknown enemy moveCurrent boundaryNo name, damage value, cooldown, status or range is accepted from trailer mood aloneGroans, screams, light and urgent dialogue can signal danger without proving an effect
Ability recordPlayer observationKeep the official enemy name, visible intent, countdown, target, effect and immediate result togetherUse a neutral temporary label until current gameplay shows the move's name
First encounterPattern checkPreserve defense or interruption, watch the visible countdown and test one response before committing the damage sequenceOne successful answer does not prove every future target, value or phase timing
Trailer cueAtmosphere onlyUse repeated sound or lighting only to locate a possible moment for closer observationDo not convert a cue into fear, chase, darkness, stun or weakness mechanics
Confirmed moveCompletionUse the current game or official combat demonstration to verify trigger, effect and resultKeep all unsupported numbers and named effects unresolved

Choose the next move

SituationChooseWhy
The required state is visibleContinueThe current build confirms the next action
A prerequisite is missingBack out and satisfy itRepeated input cannot bypass a locked requirement
No feedback appearsReturn to the last confirmed stepThis isolates the first broken assumption

Success check

The priority enemy action is delayed, blocked, or survived and the party reaches its planned damage window.

If it fails

If the preview shows the priority enemy acting before the party can answer, cancel it and select a defense, delay, or interruption.

Sources & last checkedAug 13, 2026
Report a correction for this page