Co-op sandbox games hand the rules to the players, and Bomb Appétit does this through freeplay. You choose how many modules the bomb holds, how many needy modules join them, the minutes on the clock, the strikes allowed, which modules may appear and which rule seed writes the manual. The game then deals a bomb to match.
What can you change in a co op sandbox bomb?
A freeplay bomb has six settings: modules, minutes, strikes allowed, needy modules, the modules in the mix, and the manual's rule seed. Everything else, such as the edgework, which panel sits where and the exact wires or symbols, comes from a fresh deal each time you press the button to start.
The form lives on the Play page, under the heading for freeplay on this device, and the same fields appear in an online room's lobby when the host picks freeplay instead of a mission. Here is every field with the range the form accepts and the value it starts on.
| Field | Range on the form | Starts at | Example: a beginners' night |
|---|---|---|---|
| Modules | 1 to 11 | 3 | 2 |
| Minutes | 1 to 60, whole minutes | 5 | 6 |
| Strikes allowed | 1 to 5 (1 is labelled no mistakes) | 3 | 5 |
| Needy modules | None, 1, 2 or 3 | None | None |
| Modules in the mix | Any of the 11, at least one ticked | All 11 ticked | Wires and Big Button |
| Manual (rule seed) | 1 to 999,999 | 1, the standard manual | 1 |
The right-hand column is an example, not a recommendation from the game. It describes a gentle first evening: two modules drawn only from Wires and Big Button, five strikes so a nervous Defuser can recover, and a minute more than the form would suggest so nobody feels hurried.
A few details are worth knowing before you build. The pool of needy modules cannot be narrowed. Pick one, two or three and the form notes that they are drawn from Pressure Vent, Discharge Lever and Dial Alignment. The module pool works differently: untick anything you have not learned yet, but the form will not let you untick the last box, so a bomb always has at least one kind of module to deal.
When the modules count is higher than the number of ticked modules, the deal repeats. It works through the pool once in a shuffled order, then shuffles again for the remainder. Ask for four modules from a pool of two and you get both kinds twice. Ask for three from a pool of eleven and you get three different modules.
The seed field is the setting with the biggest reach. A rule seed rewrites every page of the manual, and our guide to what stays the same across seeds and what changes separates the parts that move from the parts that stay put. The button beside the deal button opens the manual for whatever seed the form holds, which saves typing it twice.
Suggested sandbox time: five minutes plus one per extra module
The freeplay clock suggests five minutes for any bomb of up to three modules and adds one minute for each module beyond three. Change the modules count and the minutes field resets to that suggestion. You can then type any whole number from 1 to 60 over it, but do it after you settle the module count.
Worked out across the form's range, the suggestion looks like this:
- 1, 2 or 3 modules: 5 minutes
- 4 modules: 6 minutes
- 6 modules: 8 minutes
- 8 modules: 10 minutes
- 11 modules: 13 minutes
The order of operations catches people. Set the minutes to 4, then raise the modules from 3 to 5, and the minutes jump to 7 because the form rewrote them. Always choose modules first and minutes last.
The suggestion is generous next to the missions. The mission Rush hour gives six modules six minutes, two fewer than freeplay would offer for the same count, and The works gives eleven modules eleven minutes where freeplay would suggest thirteen. That gap is deliberate room to learn. A team that keeps beating the suggested clock with minutes to spare can shave a minute at a time until the margin feels tight.
Needy modules do not change the suggestion. Adding three needy panels leaves the clock where the module count put it, even though the Defuser will spend real seconds on them. If you add needy modules, consider giving back a minute or two by hand.
When does a sandbox bomb switch to the bigger case?
A freeplay bomb uses the 3x2 case while the modules and needy modules together come to eleven or fewer. At twelve or more it moves to the 4x3 case. The 3x2 case has six slots on each of two faces, twelve in all, and one slot always holds the timer, which leaves room for eleven panels.
The 4x3 case has twelve slots per face, twenty-four in all, so it holds up to twenty-three panels beside the timer. With the form's limits of eleven modules and three needy, the most you can build is fourteen panels, which sits comfortably on the larger case with plenty of empty slots.
Some combinations that cross the line:
- 11 modules and no needy: 11 panels, small case, every slot filled
- 9 modules and 2 needy: 11 panels, still the small case
- 9 modules and 3 needy: 12 panels, the 4x3 case
- 11 modules and 3 needy: 14 panels, the 4x3 case
The switch matters for the Defuser more than the Experts. A bigger case means more turning, more slots to scan and empty slots that look like something might be hiding in them. If your group has only played the small case, build one twelve-panel bomb before trying the mission Double shift, which is the only mission on the bigger case. The guide to the twenty missions from First bite upward shows where it sits in the ladder.
Sharing a sandbox setup by link
Freeplay settings travel in the page address, so a setup can be bookmarked or pasted into a chat. When you press the deal button, the address that opens carries the module count, the needy count, the time in seconds, the strike limit and the rule seed, plus the module pool whenever fewer than all eleven are ticked.
An address for the beginners' night above would look like /bomb?modules=2&needy=0&time=360&strikes=5&rule=1&pool=wires,big-button. Note that time is written in seconds in the address, so six minutes reads as 360. The form only offers whole minutes, but an address can carry any value from 30 seconds to an hour, which is handy for a ninety-second drill.
A shared address fixes the recipe, not the bomb. Each person who opens it is dealt a new bomb built from those settings, with different wires, symbols and edgework. That is perfect for practice but wrong for a race, because two groups opening the same link will not face the same puzzles. For a fair contest between groups, use a mission whose bomb is the same for everyone, which the guide to challenge games between friends online explains.
If an address holds a value outside the allowed ranges, such as seven strikes or a seed of zero, the page does not try to guess. It shows a not-found page instead of a bomb, so check the numbers if a shared link fails to open.
Sandbox bombs and the leaderboard: why freeplay has no board
Freeplay defusals never appear on a leaderboard. Each board belongs to one mission, and every runner on it faced the same mission card: the same module pool, clock, strike limit and seed. A freeplay bomb has no such card, so there is nothing fair to rank it against, and its results page has no rank line.
After a freeplay round the results page still shows the essentials. The heading reads Freeplay, then the time left, strikes against the limit and the manual seed, then each module with the moment it was solved and any strikes it caused. That breakdown is the useful part of a sandbox round, since it shows which panel held the team up.
People sometimes expect a fast freeplay defusal to rank and are confused when it does not. Freeplay is only one of several reasons a run can be missing, and the post on why a run did not appear on the leaderboard lists the others, including playing as a guest.
Groups who want a contest with freeplay can still keep score by hand. Two teams can each play the same recipe and compare time left, though each team gets a different deal. The guide to two teams racing one mission board covers a fairer way to run that kind of night.
The sandbox mistake: a bomb nobody can finish
The commonest freeplay error is building a bomb that tests nothing but luck: too many modules, too little time, one strike and modules nobody has read. A bomb like that ends in the first minute, teaches the group nothing and makes the next round feel pointless. A good sandbox bomb is hard in one way at a time.
Pick a single thing to stretch, and keep everything else easy. Some examples of one-dial changes from a comfortable baseline of four modules, six minutes and three strikes:
- Stretch speed: keep four modules, drop the clock to four minutes
- Stretch accuracy: keep the clock, drop strikes to one
- Stretch attention: keep the rest, add one needy module
- Stretch knowledge: tick one module nobody has played and leave three familiar ones
Each of those has a clear lesson when it fails. If the four-minute bomb runs out, the team knows to work on pace. If the one-strike bomb goes off, the strike shows which module was the guess. Turn all four dials at once and an explosion could have come from any of them.
Watch the module pool in particular. A bomb dealt from all eleven modules can hand a new group Labyrinth or Passcode in its first round, and a Defuser who has never seen either will stall while the Experts hunt for the page. Untick what the group has not met, then add one module back each evening.
Last, remember that a strike speeds the clock up. Every strike makes the countdown run a quarter faster, so a bomb set to five strikes is not five free mistakes. By the fourth strike the clock runs at twice normal speed. Five strikes is kind to a nervous Defuser, but a team that leans on them will still run out of time.