Co op campaign games give a group a path from easy to hard that it walks together. Bomb Appétit's 20 missions work as one: four sections of five bombs, each section a step up from the last. Played one section per evening, the whole campaign takes four nights, and signed-in players keep their progress between them.
What turns twenty missions into a co op campaign?
The 20 missions become a campaign because they climb in order. Section 1 teaches three module types on small bombs, Section 2 adds new types and more modules, Section 3 brings needy modules, and Section 4 mixes everything with a bigger case and fewer strikes. No mission is locked, so the order is a recommendation rather than a gate.
The game names its four sections like courses of a meal: Appetizers, Main course, House specials and Chef's table. Each section opens with missions that introduce something and closes with missions that test it. Section 2 is a good example. Echo chamber, Word salad and Second helpings each bring in one new module type on a three-module bomb, then Mixed plate and Rush hour throw five and six modules at the team, drawn from all six types it now knows. What each section adds, mission by mission, is set out in what Section 2 adds to the bomb, and the wider tour of the missions from First bite up covers all four.
Because nothing is locked, a group can open the missions page and press Play on Double shift on its first evening. That freedom is useful for a returning group that wants to skip ahead. For a new group it is a trap, since the later bombs assume the team already has names for glyphs, a habit of reading edgework and a plan for needy modules. Treating the sections as chapters, and finishing one before starting the next, is what makes the missions feel like a campaign rather than a menu.
A campaign also needs a cast. Bomb Appétit takes two to five players per bomb, one Defuser and one to four Experts, and the same group should ideally return each night. A pair can play every mission, and our post on two-player campaign games through all 20 missions follows a pair through them. A full table of four splits the manual three ways, which four-player co op campaign games with three Experts works through mission by mission.
A four-night campaign plan, one section per evening
One section per night is the natural pace. The five clocks in a section sum to between 23 and 52 minutes, and real evenings run longer than that once you add setup, retries and talk. A short first night and a long last night suit how a group learns: quickly at first, then slowly as the bombs grow.
The table below takes each section's clock total straight from the game's mission data. The Defuser column is our suggestion for who holds the bomb that night, not something the game sets.
| Night | Section | Its five missions | Clocks added up | Suggested Defuser for the night |
|---|---|---|---|---|
| One | 1, Appetizers | First bite, Button up, Strange symbols, Table for three, Quick snack | 23 minutes | The player newest to the game |
| Two | 2, Main course | Echo chamber, Word salad, Second helpings, Mixed plate, Rush hour | 28 minutes | Whoever described things most clearly on night one |
| Three | 3, House specials | Signal fire, Spaghetti, Pressure cooker, Full boil, Back of house | 34 minutes | The calmest player under a ticking needy module |
| Four | 4, Chef's table | Lost in the sauce, The works, No substitutions, Double shift, Bomb Appétit | 52 minutes | The player with the most bombs behind them |
Night one is short enough to fit before dinner. Its bombs have one to four modules, three strikes each and clocks of four or five minutes, so most of the evening is spent learning to describe wires, a button and four glyphs. Plan on about an hour if this is the group's first time with the game.
Night two adds Color Echo, Word Grid and Recall, then two big bombs at the end. Rush hour's own description tells the team to split the manual between Experts, so night two is also when a group with more than one Expert should decide who owns which pages.
Night three is the hardest jump. Signal fire and Spaghetti introduce three new module types, then Pressure cooker brings the first needy module, and Back of house finishes with eight modules, two needy ones and the back of the case to check. Budget the most retries here.
Night four is the long one. The works is one of every regular module type on eleven minutes. No substitutions allows two strikes. Double shift is the only mission on the bigger 4x3 case, and the final mission, named after the game itself, uses rule seed 2026 instead of the standard manual and allows a single strike. Splitting night four across two evenings is a sensible change rather than a failure.
What does a campaign save between nights?
A signed-in player keeps their best verified defusal of each mission, shown on the missions page as a Defused badge with the time left and a percentile rank. Their dashboard counts how many of the 20 they have defused, and that progress follows them to any device. Guests can play every mission but are never ranked.
Signing in is done with GitHub and costs nothing. Once a player is signed in, each mission card they have beaten shows the best time left, such as "Defused · 1:32 left", and their position on that mission's board as a "Top N%" figure. The dashboard reads "6 of 20" or wherever the group has reached, which makes it the simplest campaign tracker there is. How to sign in, and what changes once you do, is covered in signing in with GitHub for a ranked run.
Progress belongs to the Defuser. When a bomb is defused, the run is saved against the person who held it, and the Experts in an online room are recorded by name beside them on the board. If the group wants one account to show the whole campaign, the same person needs to defuse every mission, or each player keeps a partial record of the missions they defused.
Guests are a different case. A guest who has created or joined an online room gets a guest name stored in that browser, and that browser's missions page can still mark a mission as defused. Nothing follows the guest to a different device, nothing appears on a leaderboard, and there is no dashboard. A guest playing on one device without ever opening a room keeps nothing between nights. For a four-night campaign, the Defuser of each night should sign in.
Replaying a campaign mission you already defused
A second run at a defused mission is worth it when the first was scrappy or the group wants a better place on the board. Only the player's best verified defusal is kept, so a slower replay changes nothing. A faster one, or an equal time with fewer strikes, replaces the old result on the missions page and the board.
Most missions deal a fresh bomb on every attempt, so a replay is a new puzzle under the same rules. First bite and Button up are the exceptions, since each always deals the same bomb. That makes them good warm-ups at the start of a campaign night: the group already knows the bomb and can spend the round on clean talk rather than discovery.
The result page after each run is what tells you whether a replay is needed. It lists every module with the time it was solved and any strikes it caused. If one module took three minutes and the rest took thirty seconds each, that page in the manual needs practice, and replaying the mission is a cheap way to get it. If the times were even and the bomb was simply big, move on to the next mission instead.
A replay also helps when the campaign changes cast. If a new friend joins on night three, replaying Rush hour from night two gets them used to the manual before needy modules arrive.
When a campaign night should end before the section does
A campaign night should stop when the mistakes change kind. Strikes from misreading a new module are part of learning; strikes from mishearing a word the group has used all evening are a sign of tiredness. Two such strikes in a row, or a Defuser asking for the same instruction three times, mean the next bomb will go worse.
Other signs are easy to spot once you look for them. Experts start answering before the Defuser finishes describing a module. Nobody reads the edgework at the start of a round. A lost bomb draws a shrug instead of a debrief. Each of these costs time on the next mission, and the next mission in a section is always bigger than the last one.
Ending early does not cost the campaign anything. The missions page keeps every defusal for signed-in players, and the remaining missions in the section will be there next time. A good rule is to stop before the section's closing mission rather than after a loss on it, since Rush hour, Back of house and Double shift are the bombs that most need a fresh team.
When a group stops early, the next night can begin with a quick replay of the last mission it beat, then pick up the section where it left off.
The campaign mistake: a new Defuser every mission
Changing the Defuser after every mission resets what the team has built. Within a section, the Defuser learns how the Experts phrase things and the Experts learn how the Defuser describes things. A new Defuser on each bomb throws that away, and the closing missions of each section are where it is missed most.
There is also the progress problem. Because runs are saved against whoever defused them, a different Defuser each mission spreads the campaign across five accounts, and no one's dashboard shows a finished section.
Rotation still matters, since everyone deserves a turn with the bomb. The fix is to rotate per night rather than per mission, as the four-night table suggests: one person keeps the seat through a whole section, then hands it on. If a group wants more turns than that, rotate on the early missions of a section and keep one Defuser for the last two. Ideas for spreading the bomb fairly across one evening are in how to rotate the Defuser so everyone gets the bomb.