Arcade leaderboard habits carry over to a co-op bomb with little change. Pick one mission and stay on it, set a target for time left that sits just past your best, read the results page module by module, and spend the next attempt fixing the slowest panel. One mission, one number, one fix per attempt.
What do arcade leaderboard habits look like on a bomb mission?
An arcade score-chaser plays one game over and over, knows their best by heart, and studies where each attempt lost points. On a Bomb Appétit mission, the score is the time left when the bomb is defused, the best is shown on the missions page, and the results page breaks each attempt into module splits.
Four habits translate directly.
- One mission at a time. Each mission has its own board, so chasing a best means repeating the same mission, not hopping between them.
- A visible target. The time left from your best defusal is the number to beat.
- Reading the run. After every attempt, look at where the time went before playing again.
- One change per attempt. Fix a single thing, then check whether it helped.
There are differences too. An arcade cabinet ranks one player, while a bomb needs a Defuser and usually Experts. The board lists each Defuser once, by their best verified defusal, with the Experts on that run named beside them. A filter separates solo runs from runs with Experts. Changing who reads the manual changes the team, so a personal best is really a best for one Defuser with one group around them.
Strikes matter as well. The board ranks by most time left first, then fewest strikes, then the earlier run. Strikes also cost time directly, since each one makes the countdown run a quarter faster. A clean run is nearly always the faster run.
Setting a personal best target from the missions page badge
Once you have defused a mission, its card on the missions page shows a badge with your best time left, such as "Defused · 1:56 left". Signed-in players who are ranked also see their place as a percentile, like "Top 40%". That badge is the starting point for the next target.
How far past it should the target sit? Far enough to need a change, near enough to reach in an evening. A useful rule of thumb, offered as a suggestion: aim for about ten percent more time left, or ten seconds, whichever is larger. A best of 1:56 suggests a target of about 2:08. A best of 0:20 suggests 0:30.
Big jumps are rarely worth chasing directly. A team that finishes Strange symbols with two minutes left and sets a target of four minutes has set a goal it cannot reach by trying harder. The move from two to four minutes takes several separate improvements, each of which deserves its own attempt.
The percentile is a different kind of target. "Top 40%" means 40 percent of ranked players on that board did as well or better. Moving into a smaller percentile depends on other people's runs as much as yours, so it suits a longer goal. The full board is on the leaderboard page, with a filter for solo runs and runs with Experts.
Groups that rotate the Defuser should keep a separate target for each person. The board files every defusal under whoever held the bomb, so each Defuser builds their own row and their own best. A friend who takes the bomb for one attempt does not overwrite yours, and your target stays tied to the runs you defused.
Guests can play everything, but only signed-in players are ranked. A team that wants its personal best to appear on the board needs the Defuser to sign in before the attempt.
Module splits on the results page: an arcade run panel by panel
Every results page lists the bomb's modules with the moment each one was solved, measured from when the bomb was armed, and any strikes it caused. Subtracting one solved-at time from the next gives a split: roughly how long that module took. Splits show where an attempt lost time far more clearly than the final number.
Here is a worked example with invented values, two attempts at Strange symbols by the same team. Strange symbols gives five minutes and three strikes for three modules drawn from Wires, Big Button and Glyph Keypad, and since the bomb deals three from a pool of three, every bomb has one of each.
| Module (example values) | Attempt 1: solved at | Attempt 1: split | Attempt 2: solved at | Attempt 2: split |
|---|---|---|---|---|
| Wires | 0:48 | 48 s | 0:40 | 40 s |
| Big Button | 1:31 | 43 s | 1:15 | 35 s |
| Glyph Keypad | 2:55, 1 strike | 84 s | 2:05 | 50 s |
| Results page summary | 1:56 left, 1 / 3 | 2:55 left, 0 / 3 |
The team solved the modules in the order shown both times, so the splits are straightforward. On a real results page, modules are listed in the bomb's own order, which may not match the order the team solved them. Sort by solved-at time before subtracting. If two modules were worked on at once, for example a quick Big Button press while an Expert was still reading the keypad page, the splits blur together. That is fine for spotting the slow panel, but treat any single split as a rough figure, not a stopwatch reading.
Notice that the first attempt's last module was solved at 2:55 but the clock showed only 1:56 left, not 2:05. The strike explains the gap. In this example it came at about 2:19, partway through the Glyph Keypad. After it, the countdown ran a quarter faster, so the remaining real seconds cost more clock than they took.
Reading this example, the Glyph Keypad split changed most: 34 seconds faster and the strike gone. Wires and Big Button improved a little, as they often do with repetition. The second attempt also dropped the strike penalty entirely, which by itself was worth several seconds.
Which module split should the next personal best attack?
Attack the module with the longest split, or any module that caused a strike, whichever costs more time. A strike usually wins, because it adds both the wasted attempt and a faster clock for the rest of the run. With no strikes, pick the single slowest split and ask why it was slow.
Slow splits tend to have one of a handful of causes:
- The Expert hunted for the page. Fix it by assigning pages before the start.
- The Defuser described the module in a way the Expert could not match. Agree on words for symbols, colours or positions.
- A rule asked for edgework nobody had read out yet. Read the serial, batteries, indicators and ports first.
- The module itself is long, and the team has not practised it.
The first three are habits, and fixing them can happen within one evening. The guide to where a defusal loses its seconds looks at each of those waits in detail.
The fourth needs practice away from the board. A freeplay bomb with only that module in the pool lets the team run it a dozen times in the space of one mission attempt. The guide to building your own freeplay bomb covers every setting, and the guide to practising for a ranked run with freeplay bombs turns them into a short drill plan.
Once the slowest split improves, a different module becomes the slowest. That is normal. Work down the list one module at a time, and the overall time left rises with each fix. For the broader speed picture, the guide to time attack games and getting faster without strikes puts these fixes in order.
The arcade leaderboard mistake: a personal best from one lucky random bomb
On most missions every attempt deals a fresh bomb, so one fast run may owe as much to an easy deal as to the team's skill. Judge a best on a random-bomb mission over several attempts. If three runs land near the same time left, that number is real. One run far above the rest was probably the bomb.
Only two missions avoid this. First bite and Button up use the same bomb for every team, and their boards say so above the table. Every other mission, Strange symbols included, deals fresh modules, edgework and positions each time. Two Wires modules can differ in how many wires they hold and what the rules ask about them.
For a team chasing a personal best, this changes how to read progress. Track the time left from your last five attempts, not just the best. A rising average says the team improved. A flat average with one outlier says the team got lucky once, and the next attempt will probably land back near the middle.
Comparing your time with friends has the same problem, only worse, since different groups never share the deal on a random-bomb mission. The guide to why a friends' challenge needs the same bomb explains which missions make a fair contest.
Last, rest between attempts. Arcade players know that the tenth attempt after midnight is rarely the best, and a bomb team is no different. The guide to climbing a board covers the mistake of retrying the same mission while tired and when to stop for the night.