CoD2Getting StartedCall of Duty 2 versions explained
Everything about CoD2 versions: the 1.0-1.3 patch history and what each changed, the protocol version-lock (115/117/118), why both 1.0 and 1.3 servers are still around, what a "cracked" server actually means, the state of PunkBuster, and the libcod / CoD2x tooling modern servers run.
TL;DR - which version do I need?
- Playing today? Steam gives you 1.3 (protocol 118), which reaches the modern tooling-standard servers. Old 1.0 community servers (protocol 115) need a manual downgrade - the two populations do not mix.
- Hosting a server? Use 1.3 plus libcod or CoD2x for scripting, stats, and modern anti-cheat.
Full detail below.
Call of Duty 2 is one of the oldest shooters with a genuinely living server scene - two decades on there are still populated servers every day and even the odd LAN tournament. If you are joining or hosting today, two version numbers do almost all the work: 1.0 and 1.3. Here is what actually separates them and everything in between.
The patch history (2005-2006)
Infinity Ward patched CoD2 for about eight months after its October 2005 launch, then stopped at 1.3. Every version below is a PC release, and each carries a network protocol number that has to match for a client and server to talk:
| Version | Date | Protocol | What changed |
|---|---|---|---|
| 1.0 | Oct 25 2005 | 115 | Retail launch build. No PunkBuster. Still the baseline a lot of old private servers run |
| 1.1 (aka 1.01) | Dec 2005 | - | An optional Intel dual-core/Hyper-Threading performance patch, marked "not required". No gameplay or multiplayer content. Nobody runs servers on it |
| 1.2 | Apr 2006 | 117 | Added PunkBuster (opt-in), the only two new official PC maps - mp_rhine and mp_harbor - an HTTP redirect for downloading custom maps, a server MOTD/objectives screen, better spawns, and several exploit/crash fixes |
| 1.3 | spring 2006 | 118 | The final official patch. Raised the match gamestate limit (16k to 128k), fixed a PunkBuster GUID bug, added a PunkBuster filter to the server browser, and bug-fixed the two 1.2 maps. Includes everything from 1.2 |
A couple of things to pull out of that table. The exact 1.3 release date is genuinely disputed between sources (some say early May 2006, others early June) - it was spring 2006, and there was never an official 1.4 (a "1.4" you may see is either the completely separate 2003 original game, or a community mod). Also, official patches added only two multiplayer maps to PC in the game's whole life, both in 1.2. The Xbox 360 got separate paid DLC map packs that never came to PC.
Why your version has to match exactly
CoD2 locks each build to a numeric protocol - 1.0 is 115, 1.2 is 117, 1.3 is 118 - and a mismatch is a hard connection failure, not a warning. A 1.3 client cannot join a 1.0 server, full stop. This is why community tooling only bothers to support those three versions (the optional 1.01 Intel patch is ignored by everyone), and why the scene never fully consolidated onto one number the way some games did.
The 1.0 vs 1.3 split (it is not as clean as people say)
You will hear that "1.0 is the cracked/community version and 1.3 is the legit/Steam version". That is half true and worth untangling:
- 1.3 is the modern standard. Steam installs and locks to 1.3, and every current tool - PunkBuster, the competitive Promod mod, the CoD2x patch, the official master server - is built on 1.3. If you are setting up something new, target 1.3.
- 1.0 persists out of inertia. It is the original retail-disc build that private communities installed 15-20 years ago and simply never patched. There was little reason to: no PunkBuster to lose, and Activision's own patch downloads are long gone. So a large pool of old 1.0 servers just kept running.
- "Cracked" is a separate axis, not a version. A cracked server is one where CD-key validation is disabled (via a modified server binary or a libcod flag) so keyless or duplicate-key clients can join. That is independent of the game version - cracked servers exist on 1.3 as well as 1.0, and normal Steam/CD-key clients generally cannot join a cracked server and vice-versa.
So the honest summary is: 1.3 = current tooling and Steam; 1.0 = legacy retail-disc servers that never updated; cracked = a key-check setting that can sit on either.
PunkBuster is effectively dead
PunkBuster arrived in 1.2 and was tightened in 1.3, but it is unmaintained now - Even Balance's update servers for CoD2 are gone and there are no new cheat signatures. Community archives preserve the old PB files so an admin can still switch it on, but it provides no real protection anymore. Most current servers run without it, or lean on the HWID-based bans in modern tooling instead.
libcod and CoD2x: what modern servers actually run
Because Infinity Ward stopped 20 years ago, the community keeps CoD2 alive with two big open-source projects:
- libcod - a library injected into the Linux dedicated server that adds new functions to the game's own GSC scripting language: MySQL/SQLite access (stats, XP, ban databases), shell commands, physics and weapon-tuning natives, plus engine-level fixes and faster downloads. It builds for 1.0, 1.2, and 1.3. The advanced zk_libcod fork requires a 1.3 base.
- CoD2x - a broader unofficial patch layered on 1.3 that raises the tickrate (30 to 40), adds raw-mouse input, an HWID ban system to replace dead PunkBuster GUIDs, DDoS/flood mitigation, and its own backup master server. This is the toolchain the competitive and actively-maintained scene runs on.
If you host on Linux and want stats, custom scripting, or modern anti-cheat, you are almost certainly running one of these on top of a 1.3 server.
Don't confuse it with the rest of the series
CoD2 is its own game with its own version numbers. Call of Duty (2003) and its United Offensive expansion use a separate 1.x line (up to 1.5/1.51) and are completely incompatible with CoD2. Call of Duty 4 (2007) and everything after run on different engines entirely - none of CoD2's 1.0/1.2/1.3 numbering, PunkBuster status, or libcod tooling carries over. A stray "1.4 patch" you find online is almost always the 2003 original, not CoD2.
The bottom line
- Playing today? Steam gives you 1.3, which reaches the tooling-standard servers. To join an old 1.0 community server you have to downgrade to 1.0 (manually swapping in the old files). The two populations do not mix.
- Hosting a server? Use 1.3, add libcod or CoD2x for scripting, stats, and modern anti-cheat, and treat PunkBuster as optional legacy weight.
- "Cracked" is about CD keys, not the version - decide it separately from which patch you run.
FAQ
Can a 1.3 client join a 1.0 server?
No. The protocols (118 vs 115) do not match, so the connection is refused. You have to run the same version as the server.
Is 1.0 or 1.3 better?
For anything new, 1.3 - it is what Steam ships, what the tooling targets, and what most organized play uses. 1.0 mainly matters for reaching specific old community servers that never patched.
What is a "cracked" server?
One with CD-key checking turned off so keyless clients can join. It is a server setting independent of the game version; cracked servers exist on both 1.0 and 1.3, and legit key-checked clients usually cannot join them.
Do I need PunkBuster?
No. It is unmaintained and provides no live protection. Modern servers run without it or use libcod/CoD2x HWID bans instead.
MantaScope tracks the live Call of Duty 2 server list - population history and graphs, per-server rank against the rest of the CoD2 servers, uptime and downtime incidents, and decoded server details - so you can see which servers are populated right now and watch your own from the browser. Browse Call of Duty 2 servers.
