Rules
Community maintained rulesets for Call of Duty: Zombies
Full gameplay is MANDATORY. Small amounts of missing footage because of a stream cutting out is fine - as long as no crucial moments in the game are missed.
You can avoid missing footage by recording at the same time.
This rule is very broad, but it applies whenever you cannot find an information about something specific. In some categories, you'll find rules that are essentially a duplication of this one, but for something specific, this means, the community discussed that one specific thing.
Emulator definition ambiguity
This rule technically makes playing on Linux unlegit, because the game is ran through an emulation layer. This has never been enforced, but the rule has not been updated either.
BO1 explicitly voted in:
sv_cheats DVAR to 1 is NOT ALLOWED unless otherwise specified.
Substituting a player in a coop game is NOT ALLOWED.
Substituting a player means a different person joining for another session within the same game, the same set of players need to play throughout the entire game.
Fast Knife exploit is ALLOWED.
Fast knifing is holding the fire button and then knifing rapidly
Voted in:
Voted in:
Abusing fast nades glitch is NOT ALLOWED
Fast nades is when due to pressing the nade button in a very specific interval nades are thrown at a faster rate. This is unavoidable in normal games, this just prevents abuse using external software.
Voted in:
| Platform | Rule |
|---|---|
| Steam | NOT ALLOWED |
| Plutonium | REQUIRED FOR PC |
| Redacted | NOT ALLOWED |
| Xbox 360 / One / Series | ALLOWED |
| PS3 | ALLOWED |
| PS4 / PS5 | ALLOWED |
| WiiU | ALLOWED |
Voted in:
This rule purposefully opens many ways to satisfy this requirement, it's not about dictating how player is suppose to share their gameplay, but to ensure they do it and it's possible to find.
Voted in:
Plutonium is REQUIRED for runs on PC. You MUST be on a most recent version. Versions older than the most recent one become invalid when both of these conditions are true relative to the time the game begin:
- A version is a month old or older
- Newer version was released 72+ hours ago
This was done to prevent cheating and for further enforcement of the rules.
Voted in:
When the rule was drafted, one scenario was not fully covered. In case of an update that happens after more than a month, with that wording the player had 0 buffer. If they started a game 15 minutes after Plutonium updated but didn't run the updater, it would have been a reason to disqualify it. Because of this, the rule listed here is slightly adjusted to give players a buffer and prevent a situation where their game is DQ'd because of factors outside of their control.
Voted in:
The B2FR community patch is REQUIRED for runs on PC. You MUST be on a most recent version. Versions older than the most recent one become invalid when both of these conditions are true relative to the time the game begin:
- A version is a month old or older
- Newer version was released 72+ hours ago
Voted in:
When the rule was drafted, one scenario was not fully covered. In case of an update that happens after more than a month, with that wording the player had 0 buffer. If they started a game 15 minutes after B2FR updated but didn't check for updates or run the updater, it would have been a reason to disqualify it. Because of this, the rule listed here is slightly adjusted to give players a buffer and prevent a situation where their game is DQ'd because of factors outside of their control.
Voted in:
Disabling Plutonium anticheat functionality is NOT ALLOWED. The following DVARs CANNOT be disabled:
cg_flashscripthashescg_drawidentifier
Covering Plutonium anticheat output on the gameplay is NOT ALLOWED. The output is the text in the upper right corner on the screen, and list of checksums listed in the upper left part of the screen every few rounds.
Check your stream overlay alignment BEFORE starting the game, make sure it does not cover any of important information on the screen.
These are the protected elements
There is also a separate hash output on the right, underneath the watermark. Covering this does not disqualify your run at this time, but it's recommended to keep it visible, to avoid controversy in the future in case it becomes necessary to validate games.
Changing any settings in a Custom Game menu is NOT ALLOWED.
Default options are:
| Option | Value |
|---|---|
| Starting round | 1 |
| Magic | Enabled |
| Headshots only | Disabled |
| Hellhounds | Disabled |
Voted in:
Fixed Backspeed is NOT ALLOWED.
Fixing backspeed means changing the player_backspeedscale and player_strafespeedscale values
Voted in:
Revoted in:
Revoted again in:
This is agreed on by the majority of active players, however we don't know of any recorded votes about this topic.
Voted in:
2 Black ops 2 votes that touched on this topic did not include First Room, the bypass is therefore still Not Allowed as per default ruling from years ago. In modern days it does not require any BIOS actions (it's built into Plutonium) therefore we think it should be discussed.
Custom camos are ALLOWED with the exception of following types of textures:
- AI (eg. zombies, hellhounds, leapers)
- Player models (except for hand textures, the hands cannot be very bright or just be covered with gradient color)
- Boards and other objects that delay time of entrance of zombies into the map
Voted in:
Voted in:
The sound REF leak fix is ALLOWED.
This fix is automatically enabled as of Plutonium version R5260.
This does nothing in the first room, as the error in question is not possible to reach with the emount of kills done in a first room game. The rule is put in here for completion.
The use of the pause_hard command is ALLOWED.
While being very helpful for World at War and Black Ops 1, we know of cases where it caused Black Ops 2 crash, we therefore recommend to not use it for the time being.
Voted in:
This rule forbids the use of HealthBar app
Voted in:
This was voted on in a general Black Ops 2 vote that didn't exclude First Room and therefore applies here. First Room players seem to agree with that decision.
The spawn control startegy is NOT ALLOWED
Spawn control strategy is abusing imperfect zoning to cause zombies to spawn from spawns that are not normally active during a First Room game
Voted in:
The vote went over maps that were known to have this exploit at the time, however the overall sentiment was that this strategy is overall unacceptable.
Boarding strategy is ALLOWED.
Boarding strategy means progressing the round by letting zombies bleed out behind windows when played don't do any additional actions to push the round, such as doing a horde up, forcing power ups or shotting windows
Voted in:
Due to players raising a concern about this rule being too opinionated relative to how the map itself works (the machine is naturally available to players), this was re-voted in vote 6 and remains banned. This rule has been in place since the beginning, you will find games with Jug, this is due to the fact
Playing with Jugger-Nog machine in a slot that is accessing for a first room game is NOT ALLOWED.
B2FR patch displays a warning at the beginning of the game if the machine is going to drop in the first room.
Voted in:
Re-voted in:
The rule initially permitted having the Jug machine in the room under a string condition having the full multi-POV gameplay, there are few games from that period of time with Jug in the room. As of vote 6 that is no longer an option, which simplifies the rule.