World at War Modding on OpenMods

Where custom Zombies came from

Call of Duty: World at War is Treyarch's 2008 Second World War entry, built on the same engine as Call of Duty 4 and released with the same kind of official mod tools. On its own that would make it one more moddable shooter of its era. What sets it apart is a bonus mode unlocked after the campaign: Nazi Zombies, four players in a boarded-up bunker. Treyarch's mod tools shipped shortly after launch, and the community immediately started building its own Zombies maps.

Seventeen years later, that is still what the game is for. Multiplayer servers are quiet, but custom Zombies maps for World at War keep appearing, and the scene has its own tooling, its own conventions, and a generation of mappers who later moved on to Black Ops III when Treyarch finally gave Zombies official mod support again.

What the toolchain looks like

The World at War Mod Tools are a free item in your Steam library under Tools, or a standalone download for retail owners. The package is the direct ancestor of the Black Ops III tools:

• Radiant for level geometry and entity placement.
• Asset Manager for defining models, materials and weapons.
• Launcher for compiling, lighting and building fast files.
• GSC scripting for gameplay logic. World at War's Zombies scripts are the foundation that most later custom Zombies scripting descends from.

The important quirk is where mods live. Unlike Call of Duty 4, World at War stores mods in your user profile rather than the game folder: %LOCALAPPDATA%\Activision\CoDWaW\mods\. Every custom Zombies map is technically a mod, so each one becomes its own folder in that directory, and you load it through the in-game Mods menu.

The community layer

Two names come up constantly. UGX Mods has been the central hub for World at War custom Zombies for over a decade: a forum, a map database, tutorials, and a map manager that handles installation. T4M is a community patch that lifts the engine's memory limits, and a large share of modern custom maps refuse to run without it because they simply contain more assets than the original engine budgeted for.

Content-wise, the scene ranges from faithful remakes of the official maps and of Black Ops era maps, to original stories with multi-step Easter eggs, to gimmick maps that exist to be difficult. YouTube playthroughs are how most maps get found.

What you'll find on OpenMods

OpenMods indexes projects that publish from GitHub, and for World at War that is a small but useful subset. Finished maps mostly circulate as downloads through UGX and similar sites, without public source. What surfaces on GitHub tends to be scripting resources: perk and weapon script packs for mappers, tooling that patches or automates parts of the Launcher workflow, and template projects that show how a mechanic is wired.

Treat the World at War catalogue here as a creator's resource. If you want maps to play, the community hubs have thousands; if you want to understand how those maps are built, this is a good place to read real project files.

Practical notes

• Patch to 1.7. Custom maps assume the final official patch. The Steam version is already there; retail needs the patches applied in order.
• Install T4M early. It is a single library dropped into the game folder. Most maps released in the last several years list it as a requirement, and the failure mode without it is a crash with an unhelpful memory error.
• Mods menu, then Launch. Selecting a map in the Mods menu restarts the game into it. Then you start it from Solo or Co-op like an official map. New players frequently miss the second step.
• Co-op means matching folders. Everyone needs the same map installed in their own mods folder. There is no automatic download.
• Keep the game folder clean. If the game stops launching after a bad install, Steam's Verify integrity of game files fixes the core files, while your mods folder in AppData stays untouched.

For a step-by-step of installing the tools, T4M and a first custom map, see the World at War getting started guide.