Co-op strategy games reward the team that decides the boring things before play begins. In a Bomb Appétit mission, that means two minutes in the lobby settling who owns which manual pages, who calls the time, who watches any needy module and how the team confirms an action. Once the timer runs, nobody has spare attention to negotiate.
What does a co op strategy plan need before a mission starts?
A plan for a bomb mission needs four decisions: which Expert owns which manual pages, who reads the clock aloud, who watches needy modules if there are any, and the phrase that confirms an action. All four can be settled from the mission card before the bomb is armed. None of them should be decided under the timer.
Many of the best co-op strategy games share this trait. The interesting choices happen in the moment, but the structure that makes those choices fast is agreed in advance. A bomb defusal makes the split unusually clean. The Defuser cannot see the manual and the Experts cannot see the bomb, so the plan is mostly about who talks to whom, and when.
Some things cannot be planned. The exact modules, their positions on the case, the serial number and the batteries all come from the deal, and on most missions the deal is fresh each time. A plan that tries to script the order of modules will break. A plan that says who answers which kind of question survives any deal.
The template below covers the four decisions in a form that fits on a sticky note. Fill one in for each new mission, then reuse it for every attempt at that mission.
| Decision | Question to answer in the lobby | Example: Mixed plate, one Defuser, two Experts |
|---|---|---|
| Mission facts | Modules, needy, clock, strikes, seed? | 5 modules, no needy, 7:00, 3 strikes, manual 1 |
| Module pool | Which modules can appear? | Wires, Big Button, Glyph Keypad, Color Echo, Word Grid, Recall |
| Page owners | Who reads which pages? | Expert A: Wires, Big Button, Glyph Keypad. Expert B: Color Echo, Word Grid, Recall |
| First words | What does the Defuser say first? | Edgework: serial, batteries, indicators, ports |
| Timekeeper | Who calls the clock, and when? | Defuser, at every solve |
| Needy watcher | Who handles needy modules? | Nobody needed on this mission |
| Confirm phrase | How is an action approved? | Expert instructs, Defuser repeats, Expert says "yes" |
The right-hand column is an invented example for one team. Its page split is one sensible way to divide six modules between two people, not a rule of the game.
Reading the mission card for strategy: modules, needy and strikes
The mission card on the missions page tells a team almost everything a plan needs. It shows the number of modules, any needy modules, the clock, the strike limit and the manual seed, then lists the modules the bomb may draw from. Read it aloud in the lobby, because each number points to a decision.
Take the card line by line.
- The module count sets the pace. Divide the clock by it to get a rough time per module. Mixed plate gives seven minutes for five modules, about 84 seconds each.
- The needy count decides whether you need a watcher. Zero means skip that decision entirely.
- The strike limit decides how much checking the team does. Three strikes allows a little risk. One strike allows none.
- The manual seed tells every Expert which manual to open. Nineteen missions use seed 1; the last uses 2026.
- The "From" list is the module pool. That is the list to split among the Experts.
One more fact from the deal is worth knowing. The game deals every module in the pool once before it repeats any. So when the count is smaller than the pool, every module on the bomb is a different kind, and when the count equals the pool, the bomb has exactly one of each. Mixed plate draws five from six, so exactly one of the six pool modules will be missing.
That detail sharpens the page split. Each Expert on Mixed plate should expect two or three of their pages to be used, and one page somewhere will sit idle. The missions page shows every card, and reading three or four of them together is a quick way to see how the pools grow through the sections.
Timekeeper strategy: should one Expert call out the clock?
Someone should call out the clock, but who depends on where the team is playing. In an online room, Experts see the timer above their manual, so one Expert can be the timekeeper. In the same room, the bomb screen faces away from the Experts, so only the Defuser sees the time.
A timekeeper who talks constantly is worse than none. The clock is useful at a few moments: when a module is solved, when a checkpoint passes, and when the team must decide whether to rush or slow down. A simple rule is to read the time after every solve and at every whole minute in the last three.
Keep each call short and in the same shape every time. Time first, then progress: "four ten, three down" tells everyone the clock and the count in four words. On Mixed plate, a team on pace should hear about 5:36 when the first module falls and about 2:48 when the third does. Those marks are simple division of the clock, offered as an example, not targets the game sets.
Online, giving the job to an Expert frees the Defuser's attention for the bomb. Pick the Expert with the lightest page load. On Mixed plate with two Experts, either can take it, since neither owns more than three pages. On a mission with a needy watcher, the watcher should not also keep time, because both jobs ask for interruptions.
Strikes complicate the clock. Each strike makes the countdown run a quarter faster, so the time read out after a strike falls quicker than it seems. That is the moment to slow down rather than rush, as the guide on when a fast team should slow down explains.
Strategy for a mission with a module nobody has read
If the mission card lists a module nobody on the team has read, give that page to the Expert with the fewest other pages and have them read it in the lobby. A full read takes a minute or two. Meeting a new page for the first time with the timer running costs far more.
The card's module list is the place to spot this. A team moving from Section 2 to Section 3 meets Blinker, Tangled Wires and Wire Panels for the first time. A team moving into Section 4 meets Labyrinth and Passcode. Any of those can appear on the next mission's bomb.
Three options, from best to worst:
- Practise the module first in freeplay, with it as the only module in the pool. One or two rounds teach the page and the face.
- Read the page aloud in the lobby, with the Defuser listening, so both sides know what the module asks for.
- Tackle it last during the attempt, once the familiar modules are done.
Option 3 is a fallback, not a plan. A guide to the eleven modules makes the case against solving the hardest module first, but leaving an unknown module to the end only works if the team has time left to learn it. The guide to practising for a ranked run with freeplay bombs shows how to set up the single-module drill from option 1.
The Defuser's first words help with any module, known or not. Reading the serial number, batteries, indicators and ports before anything else means the Experts have them in hand when a rule asks. The guide on why reading edgework first saves the most seconds puts numbers to that habit.
The strategy mistake: a plan nobody can remember under the timer
The most common planning error is a plan too long to hold in mind once the clock starts. Under pressure, people remember two or three rules, not ten. A page split, one timekeeping rule and a confirm phrase will be followed. A plan with a module order, contingencies and backup roles will be forgotten by the first strike.
Test a plan by asking each player to say their part in one sentence. The Defuser: "I read edgework first, then describe each module before I touch it." Expert A: "I own Wires, Big Button and Glyph Keypad." Expert B: "I own the other three and say yes when an action is confirmed." If anyone needs more than a sentence, the plan is too long.
Keep the rest for after the round. The results page lists each module with the time it was solved and any strikes it caused. That is where the team learns whether the page split was fair, whether one module stalled and whether the timekeeping helped. Adjust the plan then, not during the attempt.
Once a plan works, write it down and reuse it, changing only one thing per attempt. That is how a team turns a lucky defusal into a repeatable one, and it is the starting point for arcade leaderboard habits that chase a personal best. A team that wants to cut seconds once the plan is stable will find the rest in the guide to time attack games and getting faster without strikes.