No. Playing the same seed twice will give you the same manual, not the same bomb. Bomb Appétit uses two numbers per round: the rule seed writes the manual's rules, and a separate bomb seed deals the modules. Unless a mission pins its bomb seed, each round draws a fresh bomb against the same rules.
The bomb seed deals the bomb and the rule seed writes the manual
Every round in Bomb Appétit rests on two numbers with two separate jobs. The rule seed decides what every manual page says. The bomb seed decides what the Defuser finds on the case: which modules, which colours, which symbols, and what the edgework looks like. Changing one never changes the other.
The project's own description of its engine says it plainly: a bomb is a function of its bomb seed, and a manual is a function of its rule seed. Function here means a fixed recipe. Feed in the same number and you get the same output every time, on any computer.
That determinism is why the rule seed is something a group can share. Type 1 into the manual's seed box and you get the standard manual, identical for every player anywhere. Type any other whole number up to 999,999 and you get a different manual, but still the same one for everyone who types that number.
The bomb seed works the same way, but players almost never see it. When the Defuser presses the button to deal a bomb, the server picks a bomb seed and hands the Defuser a bomb built from it. The Experts never receive that number at all. The reasons for keeping it off their screens are covered in the post on why Experts never receive the bomb seed.
It helps to picture a single round as a meeting of the two outputs. The bomb seed produced, say, four wires and a keypad. The rule seed produced the pages for wires and keypads. The Experts can only solve the bomb because both were built for the same rule seed, which is why the bomb also carries the rule seed inside its setup.
A worked example on rule seed 1
The rules below are invented for this example. They are not copied from manual 1 and should not be used in a real round.
Suppose a group plays two freeplay rounds with the rule seed set to 1 both times.
- In both rounds the Experts open the same Wires page. Imagine its four-wire list begins: "If there is exactly one red wire, cut the second wire. Otherwise, cut the last wire."
- Round one deals a bomb whose Wires module has four wires: red, blue, white, blue. There is exactly one red wire, so the first line applies and the Defuser cuts the second wire.
- Round two deals a different bomb seed. Its Wires module has four wires: blue, white, white, blue. There is no red wire, so the first line fails and the "Otherwise" line sends the Defuser to the last wire.
The page did not change between rounds. The bomb did, so a different line of the same page fired. That is the normal experience of replaying a seed.
Who chooses the bomb seed in a round?
The server chooses it, at random, every time a bomb is dealt. Players pick the rule seed, the module count, the timer and the strike limit. They do not pick the bomb seed in normal play. In an online room, a new bomb seed is drawn each time the host arms the bomb.
On the Play page, freeplay settings travel in the address so a setup can be bookmarked or shared. Those settings are the number of modules, the number of needy modules, the time, the strikes allowed, the rule seed and, when you narrow it, the pool of allowed modules. The bomb seed is not among them. Opening the same freeplay link twice asks the server for two bombs, and each gets its own seed.
Pressing "Play again" after a round works the same way: the game requests a fresh bomb, so the next round is a different bomb under the same settings.
Online rooms follow the same pattern. The room stores the rule seed so every Expert opens the matching manual, and the host can change it while the room is in the lobby. When the host arms the bomb, the server draws a new bomb seed and sends it only to the Defuser. A second round in the same room, after the host resets it, draws again.
The server keeps the bomb seed for a reason beyond variety. Bomb Appétit verifies runs by replaying them: the Defuser's browser records every action, and the server replays that log on the bomb it issued. That only works if the server knows exactly which bomb it dealt. The details are in what the server checks before it lists a run.
First bite and Button up: the two missions with a fixed bomb
Two missions deal the same bomb to everyone, every time. First bite and Button up, the opening missions in the Appetizers section, each carry a fixed bomb seed in their data. Every other mission and every freeplay round lets the server draw a new bomb seed for each attempt.
The game's mission definitions describe the fixed seed as a way to make a mission the same bomb for everyone, used for the tutorial. That fits what the two missions are for. First bite is a single Wires module with five minutes on the clock. Button up adds the Big Button, for two modules in five minutes. Both use rule seed 1.
A fixed bomb on a teaching mission has clear benefits. A friend who already played First bite can help a newcomer, because the newcomer sees the same case. A group can replay it until the conversation feels smooth. And nobody starts their first round with an unlucky deal.
The cost is that these two missions stop being puzzles after a few plays. Once the Experts remember which wire to cut, the round is a test of memory. That is fine for a warm-up and the reason the next mission, Strange symbols, goes back to a random bomb.
Here is how the twenty missions split:
| Missions | Bomb seed | Rule seed |
|---|---|---|
| First bite, Button up | Fixed in mission data | 1 |
| The other 17 missions in sections 1 to 4 | Drawn fresh per attempt | 1 |
| Bomb Appétit, the final mission | Drawn fresh per attempt | Its own seed, 2026 |
The final mission is the one place the rule seed leaves the standard manual. So the manual changes for that mission while the bomb stays random, the opposite of the two tutorial missions.
Can two groups on the same seed compare bombs?
Two groups on the same rule seed share a manual, not a bomb. Outside First bite and Button up, each group gets its own bomb seed, so their cases will differ in modules, colours and edgework. They can compare how they handled the same rules, but not move by move on the same case.
What they can fairly compare is the outcome under matched conditions. If both groups use the same freeplay link, they get the same module count, timer, strike limit, module pool and rule seed. The results screen after each round shows time left, strikes and time played, plus when each module was solved. Those numbers make a reasonable friendly comparison, as long as everyone accepts that one group may have drawn a kinder bomb.
Luck evens out over several rounds. A single round can turn on whether a group drew a Labyrinth or a Wires module. Five rounds each on the same link gives a much fairer picture than one.
Missions add a ranked option. Each mission has its own leaderboard, and signed-in players appear once, by their best verified defusal: most time left, then fewest strikes, then the earlier run. Every attempt on a random-bomb mission is its own deal, so the ranking already accepts that bombs differ and rewards consistency across many attempts.
A two-group evening built on this idea is set out in the guide to playing against friends with one seed, and running both groups from a single room is covered in the post on one rule seed for the whole room.
The same seed assumption: expecting yesterday's wire order
The common mistake is believing a familiar rule seed means a familiar bomb. A group plays seed 1 on Monday, remembers that the second wire was the answer, and on Tuesday cuts the second wire without asking. The manual is the same; the bomb is not. Rules carry over between rounds, answers do not.
This assumption usually shows up in groups that started on First bite. That mission really does repeat its bomb, so a group learns, correctly, that the answer stays put. Then they move to freeplay or a later mission and carry the habit with them.
The fix is a simple rule for the Defuser: describe every module fresh, every round, even if it looks like one you have seen. Four wires today are not yesterday's four wires until someone reads out the colours.
Experts have their own version. An Expert who knows a page well may answer before the Defuser finishes describing the module, because the start of the description sounds familiar. Learning the page is good. Skipping the description is not. The Expert's job is to apply the page to the bomb in front of the Defuser, and that bomb was dealt a few seconds ago.
There is one safe form of memory. Knowing a seed's rules well is a real skill, and it speeds up every round on that seed. Groups that want to test memory honestly can use the missions page to pick a random-bomb mission on rule seed 1, where rule knowledge helps and the bomb still has to be read. When that gets too comfortable, a new rule seed resets the manual without changing anything else about the game.