Customizing Mystery Box Weapons
Customizing Mystery Box Weapons - NZ:P Mapping DocumentationCall of Duty: Zombies Recreation
Landing - GitHub OrganizationDownload the latest available version - Play in your Browser (WebGL)
⇑Introduction
Nazi Zombies: Portable gives level creators the ability to customize what weapons exist in the Mystery Box.
They have full-range of every non-Pack-A-Punch variant in the game. This is done via the file format.
files are created by the creator, placed in with the name , substituting with the same file name as the level .
Here is an example file that simply disables the Ray Gun and Wunderwaffe DG-2 from appearing in the Mystery Box:
All files must begin with the string “”.
Similarly when is used, all weapons will be included aside from the entries listed.
only supports one command, it is recommended to use the command that has the shortest number of entries to decrease loading time for low powered platforms.
Weapon Names
Eligible weapon names are provided via the Weapon IDs documentation entry.
This format is still supported internally, meaning levels that previously utilized it will still function as intended. Provided the command, all weapons listed will appear in the Mystery Box, and those not listed will automatically be excluded. The default value is 0.045, every 45 milliseconds, it calculates the physics. It uses the file extension.
Format Example
The following is an example 1.0 file contents:
Weapon Order
1.0 files used a hard coded weapon order, that differs from the standard internal Weapon IDs used by Nazi Zombies: Portable.
Nazi Zombies: Portable also supports Valve HAMMER based mapping software via a separate FGD. Documentation and by extension headers/categories are a work in progress.
Tools
General
Map Entities
Map Triggers
Search code, repositories, users, issues, pull requests...
Hello. You can contribute to the documentation by submitting a pull request to the GitHub repository
Game Screenshots
Downloading Nazi Zombies: Portable
At this current moment, no marked-stable builds of Nazi Zombies: Portable are made available.
For assets, you will want to download and extract it to the same location as the binary, you should have the FTEQW binary and a directory called beside it. They may not be specifically relevant to custom content creators, though overlap will be present for map features that interact with NZ:P’s QuakeC or for specialty features.
Dedicated Server Documentation
Documents relevant for those who are looking to host a dedicated server for Nazi Zombies: Portable.
Mapping & Modding Documentation
These documents are relevant for level creators who wish to create content for Nazi Zombies: Portable.
The 1.0-exclusive listing follows:
- Colt M1911
- Kar98k
- Double-Barreled Shotgun
- MG42
- Ray Gun
- Thompson
- M2 Flamethrower
- PPSh-41
- Sawed-Off Shotgun
- Wunderwaffe DG-2
- M1A1 Carbine
- Gewehr
- FG42
- M1919 Browning
- Scoped Kar98k
- .357 Magnum
- STG-44
- Panzerschreck
- Ballistic Knife
- PTRS-41
- MP40
- M1897 Trench Gun
- BAR
- M1 Garand
- Type 100
- MP5K
- Springfield
Dedicated Server
Dedicated Server - NZ:P Internal DocumentationCall of Duty: Zombies Recreation
Landing - GitHub OrganizationDownload the latest available version - Play in your Browser (WebGL)
⇑Binary
You will want to obtain the upstream FTEQW server binary for your respective platform.
If you run pterodactyl there is an egg that handles the Binary, Assets, QuakeC, and CVars for you.
For everyone else, you will need to download the Assets and QuakeC files when using upstream FTEQW.
Deny
has two modes: “” and “”. These documents assume you have basic knowledge of mapping for Quake, as well as TrenchBroom knowledge. I can also see the server in the server browser just fine. The NZP folder should now contain some files. This link will always take you to the latest release, identifiable via the build date in the release title.
Core Documentation
Core documents contain information about Nazi Zombies: Portable’s internal design.
We are using the https://nzp.gay browser version to play.
These are the commands I used (one by one):
After loading into the map I see it says in the console:
Then my friend types in his console:
and he is connecting forever in the console. Be careful with raising this value too high as the more times per second the physics are calculated, the more packets are sent out and can be very bandwidth intensive, this becomes more apparent at higher rounds.
After that, you can run the binary with the argument and with the below cvars outlined.
Web
Defining a Port
You would use the cvar to specify which port the WS server will run on.
Protocol Name
=
The dedicated server runs a websocket server, you will need to type explicitly into your console on an HTTP (not S) page of the web client otherwise the browser will block the connection.
Desktop/Native
Defining a Port
You would use the cvar to specify which port the UDP server will run on.
Protocol Name
=
Custom Tick Rates
is how frequently (in seconds) physics frames are calculated.
For QuakeC you will want both and and you will want to extract them inside the folder. This is done to ensure validity of the file. Nazi Zombies: Portable goes to great efforts to achieve parity with it’s gameplay features in such a way that makes content on said wiki valid and applicable to this project as well.
All documentation and media hosted is licensed under CC-BY-SA 4.0, with no exclusions or exceptions.
The following platforms are supported:
- Windows (2000 and above, x86 and x86_64)
- Linux (x86, x86_64, arm, arm64, armhf)
- TI NSPIRE CX II
- PlayStation Portable (all models)
- PlayStation VITA
- Nintendo 3DS (all models)
- Nintendo Switch
This documentation is not designed to cover basic gameplay foundations such as the Power-Up system, what Perk-A-Cola machines are, etc., as those are bases covered by the official Call of Duty Wiki.
If a weapon is listed that is not recognized by the game, the level will not be allowed to load, and the problematic weapon will be reported to the developer console.
Backwards Compatibility
Nazi Zombies: Portable previously primarily utilized the 1.0 format, which was a string-binary list of hard-coded weapon order status.