A bomb defusal game splits one problem between people who each see half of it. In Bomb Appétit, one round runs like this: the Defuser sees a ticking bomb, the Experts hold the manual, and the team talks until every module is solved, or until the timer or one strike too many ends it.
What does a bomb defusal game actually ask you to do?
A bomb defusal game asks a group to solve puzzles they can only solve by talking. One person can see the bomb and touch it. The others can read the rules but cannot see the bomb. Nobody holds both halves, so every answer has to travel out loud between them before the clock runs out.
People sometimes search for a "bomb diffuser game" when they mean this genre. The spelling does not matter much, because the idea is the same: a bomb, a countdown and a set of instructions that only make sense once someone describes what is in front of them.
In Bomb Appétit the bomb is a case covered in modules. A module is one small puzzle panel with its own section in the manual. There are 11 regular modules, such as Wires, Big Button and Glyph Keypad, and solving every regular module on the case defuses the bomb. There are also 3 needy modules. A needy module cannot be solved at all. It wakes up now and then and has to be kept happy, or it hands the team a strike.
The puzzles themselves are rarely hard. Take Wires. The panel has three to six wires, and exactly one of them must be cut. The Expert's page has a short list of rules for each wire count. The Expert reads the right list from the top and stops at the first line that is true. That is easy with the panel and the page side by side. It gets hard when the person with the page has never seen the panel and the person with the panel has never seen the page.
That is why this is a co op bomb defusal game rather than a race. Nobody plays against anyone else. The whole group wins together or the whole group watches the bomb go off together. The skill being tested is how clearly one person can describe something and how carefully another person can listen.
The manual itself is generated from a number called the rule seed. Rule seed 1 is the standard manual and the right place to start. A different seed rewrites every rule, so the bomb and the manual have to use the same number. If you want a tour of every puzzle on the case, the guide to which modules a new Expert should learn first walks through all eleven.
The Defuser and the Experts: one bomb, two views
Every round has exactly one Defuser and one to four Experts, so a game holds two to five people. The Defuser sees the bomb and is the only player who can touch it. The Experts hold the manual and never see the bomb. The whole game lives in the gap between those two views.
The Defuser's job has three parts. Describe what is on the bomb, out loud and in order. Wait for an instruction. Do exactly what the instruction says. The Defuser is not allowed to look at the manual, so guessing at the rules from memory is off the table, at least in the spirit of the game.
The Experts' job is the mirror image. Ask what the Defuser sees. Find the right section of the manual. Read the rule that applies and turn it into one clear instruction. The manual opens with a short note for the Experts that says almost exactly this: ask what they see, tell them what to do, and do not look at their screen.
With more than one Expert, the manual can be shared out. One Expert might take Wires and Big Button while another takes Glyph Keypad, so two people never search for the same page at once. With a single Expert, that one person handles every lookup.
What the Experts can see depends on where everyone is sitting. In the same room, they see nothing of the bomb and rely on what they hear. In an online room, the app gives Experts a status line with the time left, the strike count, how many modules are solved and whether a needy module is awake. It never shows them the bomb itself.
If you are still working out the practical side, the guide to what a free bomb defusal game needs on the table covers the people, devices and calls a round needs. For a close look at the Defuser's screen, including the edgework printed on the case, read what the Defuser sees on the case.
How does a bomb defusal round start, run and end?
A round starts when the Defuser presses Play and starts a mission or a freeplay bomb. It runs while the team solves modules one at a time, in any order they like. It ends in one of two ways: every regular module shows a green light and the bomb is defused, or the bomb explodes.
The steps below follow one full round of the first mission, First bite. First bite has a single Wires module, a five-minute timer and the usual limit of three strikes, and it uses rule seed 1. The wire colors, the edgework and the rule quoted are example values. Your bomb and your manual will have their own.
- The Defuser opens the bomb. The Defuser goes to Play, picks First bite from the missions and waits on the start screen. The Defuser says: "First bite, rule seed 1."
- The Expert opens the manual. The Expert opens the standard manual, rule seed 1, on a second device or on paper. The Expert says: "Manual 1. Ready."
- The screens separate. The Defuser turns the bomb screen away from the Expert. Nobody says anything useful yet, but someone usually says "no peeking."
- The timer starts. The Defuser starts the bomb. The countdown begins at five minutes. The Defuser says: "Started. Five minutes."
- The edgework goes first. Before touching anything, the Defuser reads the details on the sides of the case. Example: "Serial number K, 7, A, 2, R, 4. Two batteries. One indicator, lit. One port." The Expert writes all of it down.
- The module gets described. The Defuser says: "One module. Wires. Four wires. Top to bottom: red, blue, blue, white." (Example values.)
- The Expert finds the rule. The Expert turns to the Wires section, finds the list for four wires and reads from the top. Example: the first true line says to cut the second wire. The Expert says: "Cut the second wire. The second from the top."
- The Defuser repeats it back. The Defuser says: "Cutting the second wire from the top." The Expert says: "Yes." Only then does the Defuser cut.
- The bomb goes quiet. The module's light turns green. First bite has only one module, so that green light is the whole bomb. The countdown stops and the round is over. The Defuser says the time that was left, and everyone breathes out.
Most missions follow the same shape with more steps in the middle. A bigger bomb means more modules to describe, more pages to find and more chances to mix up which module the team is talking about. The order of solving is free, so a team usually starts with whatever module the Expert knows best.
If a player is signed in, the finished run goes to the server. The server replays it from the recorded inputs before it can appear on the leaderboard. A guest plays exactly the same round; the run is simply not ranked.
Strikes, the timer and the speed-up after a mistake
A strike is a wrong move on the bomb, such as cutting the wrong wire or pressing a key out of order. Each strike makes the timer run faster: 1.25 times speed after the first, 1.5 times after the second. On most missions the third strike sets the bomb off. The bomb also explodes when the timer reaches zero.
The speed-up is the part new players forget. After two strikes, the countdown runs at one and a half times its normal pace. As a worked example, a display that reads 1:30 at that point gives the team about 60 seconds of real time, not 90. That changes how much talking fits into what is left.
Three strikes is the default, not a rule for every mission. The late missions tighten it. No substitutions allows only two strikes, and the final mission, named Bomb Appétit, allows just one. Those are missions for teams that already talk well.
Strikes do not only come from the regular modules. A needy module that is left alone too long also gives a strike. Pressure Vent, for example, wakes up with a question and a 40 second countdown. A wrong answer is a strike, and so is letting its countdown reach zero. The team has to keep half an ear on it while solving everything else.
After a strike, the module usually stays as it was and still needs solving. Some modules change when a strike lands, though. On Color Echo the mapping between flashes and answers changes after a strike, so the Expert has to look up the new one. The safest habit is for the Defuser to say "strike" out loud the moment it happens, together with which module caused it.
A strike is also not the end of a round. The best response is short: say what happened, check the rule again, and carry on a little faster. A team that spends thirty seconds arguing about who misheard loses more time than the strike cost.
The first-round mistake: showing the Experts the screen
The most common first-round mistake is letting the Experts see the bomb. It feels helpful, especially when a description stalls, but it removes the one thing the game is built on. Once an Expert has looked at the wires, nobody practises describing them, and the next bomb is just as hard as the first.
It usually happens innocently. The Defuser says "there is a weird symbol, I cannot explain it," and turns the laptop around. The Expert looks, the module gets solved, and the round feels like a success. What the group has really done is skip the puzzle.
In an online room this mistake cannot happen by accident. The server sends the bomb to the Defuser's browser only, and Experts get the rule seed and a status line. In the same room it is down to the players. The setup advice is simple: turn the bomb screen away from the Experts before the timer starts, and keep it turned away until the bomb is quiet.
The same rule runs the other way. The Defuser should not read the manual over an Expert's shoulder. A Defuser who knows the rules stops describing and starts deciding, and the Experts lose track of what is happening on the bomb.
When a description stalls, there are better fixes than turning the screen. Describe the shape first, then the color, then where it sits on the panel. Agree on a name for an odd symbol and keep using it. Ask the Expert what detail would help, since the manual page usually only cares about one or two things. Each of these builds a habit the team will need on harder missions.
Bomb defusal round checklist for your first game
A first game goes better with a short checklist run before anyone starts the timer. It covers the people, the devices, the rule seed, the seating and the words the team will use. Each item takes seconds, and each one prevents a strike that has nothing to do with the puzzles.
Run through this list once, out loud, before the first round:
- People. Two to five players. Pick one Defuser. Everyone else is an Expert.
- Bomb device. The Defuser has a browser open on Play, ideally on the larger screen.
- Manual. Each Expert has the manual open on another device or printed on paper.
- Rule seed. The bomb and the manual show the same seed. For a first game, that is seed 1.
- Talking. Everyone can hear everyone, either in one room or on a phone or video call.
- Seating. The bomb screen faces away from every Expert.
- Edgework. The Defuser agrees to read the serial number, batteries, indicators and ports first, and an Expert has something to write them on.
- Repeat back. The team agrees that the Defuser says every instruction back before acting.
- Mission. Start with First bite, then move on through the missions in order.
The order of the list matters less than covering it. A team that skips the seed check can follow every rule perfectly and still get blown up, because the rules on the page belong to a different bomb. A team that skips the edgework will find the manual asking about the serial number halfway through a module, and the Defuser will have to stop and hunt for it.
After the first round, swap the Defuser. Each seat teaches something different. The Defuser learns how much detail an Expert needs. The Experts learn how little a description can carry when it is rushed. Two or three rounds with different people in each seat usually settle the group's shared vocabulary for colors, positions and symbols.
When the team is ready for more than one module, the mission list shows what each step up adds, from a second module on Button up to needy modules later on. The how to play guide has the full rules on a single page, and it is worth one read by every player before the second session.