Call of Duty 2

PAM Mod 2.03 PAM Mod 2.03 Tuesday 15th 2608 August 2017 | 345,2 kB
PAM 2.03
--------
C: Removed Players Left Display from Ready-Up
+: Scripted in an artificial fast_restart for pam_mode changes
+: Added a reminder at the end of Ready-Up to remind about recording your match
C: Reworked the scripting to be more friendly with Custom maps (does not require special scripting for custom maps to work with PAM2)
C: Removed Ready-Up weapon drops & MG nests (less accidental UN-readying up)
+: LIVE! HUD Element - Flashes for a few seconds when PAM2 has just gone LIVE! just so there is no doubt.
+: Ready-Up Kill Counter
+: Beta of Strat Mode (No killing, Damage ammount reporting, Ammo/Nade auto-refills, sv_cheats on) - g_gametype "strat"
+: Very ROUGH version of a Bash-Round gametype - g_gametype "bash" Rifle bashing only, with option to allow pistols for bashing as well (scr_bash_pistols).
+: Pub-mode Feature TK Monitor
+: Pub-mode Feature AFK Monitor
+: Pub-mode Feature Admin Tools
+: Pub-mode Feature Message Center
+: Pub-mode Feature Welcome Messages
F: Attempted to fix missing Team headicons when voice chatting during "Strat" time in S&D
C: Added about 5 leagues/ladders and many more pam_modes
Pam 204 ESL Version Pam 204 ESL Version Tuesday 15th 2608 August 2017 | 444,5 kB
Standalone anti camper mod Standalone anti camper mod Tuesday 15th 2608 August 2017 | 49,0 kB
Irgendwie gab es das noch nicht. Gott weiß warum, jeder Mod der was auf sich hält hat Anti-Taktischer-Spieler Funktionalität, aber als Stand Alone nicht zu finden.
Also: Nimm das!
Idealerweise entpacken, und den Server mit fs_game nocamp starten. Alles andere ist ungetestet.

Details in der Liesmich.


*batteries not included.
Pam 2.04 final Pam 2.04 final Tuesday 15th 2608 August 2017 | 408,3 kB
PAM 2.04
--------
C: Added dvar to turn on/off regen breathing sounds (scr_allow_regen_sounds)
C: Added "Players Left" display to Strat Mode.
C: Changed the strat mode nade refills to give 1 nade instead of 3 (since that is the most popular number of nades available in competition)
C: Changed strat mode to use the standard ambient effects dvars for strat mode.
F: Fixed a bug in the message center that could cause a crash if you were welcoming players without using the message center
F: Fixed an extremely rare crash bug involving map exits.
F: Fixed a script exploit that could be used to either crash a server or allow players to choose weapons from the other team's weapon menu.
+: Added PUB-MODE support for DM
C: Changed the TK Monitor - Added another option for tk_punish_type: "pb_kick"  This will set the score of a player flagged as a TKer to -10.  You can then use PB to detect this and kick the player.
   Note: The mod cannot set up PB for you to do this, it will be up to you to set up PB appropriately. The advantage is that PB logs the ID's of who it kicks for your future reference.
+: Added ability to set sv_fps on the server between 20 and 30.  stock = 20.  This will also set client's snaps value to the valuse set in sv_fps on the server automatically.  
   NOTE!!!: Increaing this number may make your server run better (smoother), but be warned it will also DRAMATICLY increase the CPU demand on the server.
+: Added "scr_remove_killtriggers" dvar which removes MOST of the killtriggers added by Infinity Ward (the game's developer).
C: Changed the dvar enforcer - r_polygonOffsetBias and r_polygonOffsetScale have been removed from de_remove_exploits dvar and given thier own enforcer dvar called "de_stock_polygonOffset".
+: Added dvar to prevent killing a 100% healthy player with a single pistol shot (scr_no_oneshot_pistol_kills)
+: Added dvar to prevent killing a 100% healthy player with a single ppsh shot (scr_no_oneshot_ppsh_kills)
+: Added dvar to help balance the ppsh by reducing the damage distance to be the same as the Thompson (scr_balance_ppsh_distance)
+: Added dvars for optional scoring in S&D and CTF (scr_sd_plant_points, scr_sd_defuse_points, scr_ctf_capture_points, scr_ctf_return_points)
+: Added dvar for an additional gameplay option in CTF that will force all dead players to immediately spawn when someone captures a flag (scr_ctf_respawn_on_capture)
+: Added a deterant for smoke nade glitching which makes the exploit harder to do and much easier to catch.  Smoke nades now have a fuse.
C: Lots and lots and lots of rule changes.
COD2RconUninst COD2RconUninst Tuesday 15th 2608 August 2017 | 4,0 kB

Uninstaller für Cod2rcon Commander von http://www.rabidservers.com

Call of Duty2 Patch 1.3 Call of Duty2 Patch 1.3 Tuesday 15th 2608 August 2017 | 38.277,2 kB
=-=-=-=-=-=-
PATCH NOTES
=-=-=-=-=-=-
INTRODUCTION & IMPORTANT NOTES

This document details additions, fixes, and changes to Call of Duty 2 in the 1.3 patch.

The Call of Duty 2 1.3 patch is an all-inclusive installation, containing all of the previous
updates from the 1.2 patch and the 1.01 patch. Information about updates included from
the earlier 1.2 and 1.01 patch can be found further down this document.

IMPORTANT NOTE: Use of the in-game console is not supported by Activision(r).
Please do not contact Activision Customer Support with issues that arise from using
console commands in-game.


NOTES FOR MOD USERS:
- It is recommended that any user modifications
that have been installed to the Call of Duty 2 directory be removed before installing this patch.
These modifications are not supported by Activision and may not be compatible with some
of the new features that are included.
- Call of Duty 2 does not support mods that have spaces in the mod's folder name.
Be sure that the folder that contains your mod does not have spaces;
otherwise users will not be able to download the files.
For example, a mod in a folder called "My Mod" would be invalid, whereas "MyMod" or "My_Mod" would work.

MULTIPLAYER FIXES
-Raised the gamestate from 16k to 128k
-Added loading bars to maps mp_harbor and mp_rhine
-Addressed the PB GUID issue where players were not being assigned PB GUID's
of exactly 32 characters.


mp_rhine map changes:
-Fixed player getting on top of broken wall and seeing through second story of
bombed out building.

mp_harbor map changes:
-Reduced overall fog density
-Fixed missing water texture
-Fixed player not being able to shoot through lower portion of the first gap in a railing found on east side of map.
-Fixed player not being able to shoot through lower portion of railing found on east edge of map.
-Fixed a partially floating crate and a couple holes in sandbags.

NOTE - When benchmarking Call of Duty 2 using "timedemo <demoname>", the first few frames are
artificially slow. You will get more accurate results by using a spreadsheet program to
process the values in "main/demos/timedemo_<mapname>_mode_<modenumber>.csv".
The first column is the frame number, and the second column is the number of
milliseconds spent in that frame. Just ignore the first ten or so rows.
The average framerate is 1000 divided by the average of the remaining rows.






NOTES FROM 1.2 PATCH

This document details numerous additions, fixes, and changes to Call of Duty 2 in the 1.2 patch.

The Call of Duty 2 1.2 patch is an all-inclusive installation, containing all of the previous updates from the 1.01 patch.
Information about updates included from the earlier 1.01 patch can be found further
down this document.

IMPORTANT NOTE: Use of the in-game console is not supported by Activision(r).
Please do not contact Activision Customer Support with issues that arise from using
console commands in-game.


NOTES FOR MOD USERS:
- It is recommended that any user modifications that have been installed to the
Call of Duty 2 directory be removed before installing this patch.
These modifications are not supported by Activision and may not be compatible
with some of the new features that are included.
- Call of Duty 2 does not support mods that have spaces in the mod's folder name.
Be sure that the folder that contains your mod does not have spaces;
otherwise users will not be able to download the files.
For example, a mod in a folder called "My Mod" would be invalid, whereas "MyMod" or "My_Mod" would work.

PUNKBUSTER(tm)

Call of Duty 2 now includes PunkBuster Anti-Cheat software technology.
PunkBuster Anti-Cheat software technology and services combat online
cheating in Call of Duty 2 Internet play.

The use of PunkBuster Anti-Cheat software is optional and is provided without
direct cost to our users. For more information about PunkBuster or for
PunkBuster support, please visit http://www.evenbalance.com/.

Note for server administrators, please note the following ways you can launch
PunkBuster:

1. Launch COD2 MP executable, enable PunkBuster in the Settings.
a. Click Start New Server
b. Click Punkbuster to Yes (default is No)
c. Click Start
d. Once the server has started, to execute a config file from the console type "exec [name].cfg"

2. Launch through the command line:
a. In Windows, Start > Run >
b. Type "C:\Program Files\Activision\Call of Duty 2\CoD2MP.exe +set sv_punkbuster 1
c. Once Call of Duty 2 has started, to execute a config file from the console type "exec [name].cfg"v
3. Add "set sv_punkbuster 1" to the "config_mp.cfg" file to initialize PunkBuster.
This file can be found by going to the "Call of Duty 2\main\players" folder and looking
inside the folder named after your profile. If the "sv_punkbuster" command already exists in
your config file, you can simply change the value to "1".


NEW FEATURES:

- New PunkBuster functionality included (as described above).
- Added a "PunkBuster" filter under the "Filters" section of the "Join Server" screen.
- Added a "PunkBuster" display column on the "Join Server" screen.

- Added HTTP redirection for Servers running Mods or custom maps.
To enable redirection on the server, set sv_wwwDownload to 1. Set sv_wwwBaseURL
to the base directory where the files are stored. For example,
if the server had a file named 'myfile' meant to be stored locally at \Call of Duty\Main,
sv_wwwBaseURL should be set to "http://samplewebpage1.com/".
The file should be stored at http://samplewebpage1.com/Main/myfile.
To prevent clients from taking up a slot on the server while downloading,
set sv_wwwDlDisconnected to 1. This will free up a slot for the duration of the
download and the client will attempt to autoconnect when the download is complete.
Set cl_wwwDownload to 1 to enable redirection downloading on the client.

- Added a new Multiplayer welcome screen when joining a server that details the Map objectives and victory conditions.
- Added a "Message of the Day" for Multiplayer servers that will appear on the player's
welcome screen upon joining.
Server admins can control this text by setting the "\scr_motd" dvar to whatever text is desired.

- Added Multiplayer spawning logic that will reduce instances of players spawning in front of enemy players.

GENERAL FIXES
- Corrected an issue that occurred on certain systems using AMD(R)
Dual-Core processors where player health would not replenish at the intended speed.

MULTIPLAYER FIXES

- Fixed a potential exploit where players could get outside the map boundaries.
- Corrected an exploit that caused some servers to shut down unexpectedly.
- Please note that all "Message of the Day" text needs to be less than 1000 characters total.
- Hovering over an enemy player no longer causes the crosshairs to highlight in red.
This change does not affect teammates and crosshairs pointed at a friendly player will still
highlight green.

Headquarters Changes
- Adjusted the objective timers to ensure that the objective respawns more quickly once destroyed.
- Removed compass icons for potential objective locations before the objective has spawned.

Capture the Flag Changes
- Added HUD icons to show the flag post location when the flag is missing.
- Players in possession of the flag are now identified as flag carriers on the scoreboard.
- When an Allied player picks up the flag, fellow teammates will now see the flag carrier's position
displayed on the compass.

NEW CONTENT (Maps)


- Added two new multiplayer maps. These maps support all current game types:

mp_harbor (Rostov, Russia)

An important shipping port in southern Russia, Rostov fell to the Germans in November 1941.
The Soviet 37th army quickly counterattacked and punched through the overextended
and winter-weary German lines to the north, forcing the 1st Panzer Army out.
The Battle of Rostov resulted in the first major German withdrawal of the war.

Call of Duty veterans will recognize this location as an updated version of the original
Harbor map. In addition to the graphical and performance updates, several new structures
and flanking paths have also been added.

mp_rhine (Wallendar, Germany)

The 2nd Rangers crossed the Rhine on March 24, 1945 at Wallendar,
Germany in pursuit of retreating German forces.
German forces harassed the advancing Allied units while withdrawing.

Decimated by 5 years of war, the streets of Wallendar are covered with rubble and
impact craters creating intense battle over difficult terrain with blown-out buildings
providing cover. The Americans are attempting to take the German city on this map of urban combat.

NOTES FROM 1.01 PATCH

Call of Duty(R) 2 Intel(R) Dual-Core Optimization Update README

This update for Call of Duty 2 adds optimization, specifically to take advantage of
Hyper-Threading technology in Intel processors.
These optimizations will increase performance in both Single and Multiplayer modes.
While significant performance gains will be seen on Single-Core processors which support
Hyper-Threading, the greatest increase will be realized on Dual-Core processors.

HOW TO TELL IF YOU HAVE A SUPPORTED PROCESSOR:
1. Hit Ctrl + Alt + Delete.
2. Select 'Task Manager'.
3. Select the 'Performance' tab.
4. Select View CPU History One Graph Per CPU
5. More than one graph side by side below the 'CPU Usage History'
label indicates you have a Dual Core processor or a processor
with Hyper-Threading technology.

AUTODETECT: Call of Duty 2 yeahwill automatically enable these optimizations
if it detects that you have a supported processor.
Enthält Patch 1.1, &  1.2 
Minircon Minircon Tuesday 15th 2608 August 2017 | 3.093,5 kB

Funktionen:

Administrieren von Call of Duty 1, 1:UO, 2, 2 v1.2 Servern
Joinen von Servern direkt mit Doppelklick
Serverliste
Multiping-Chart
Selbstdefinierbare Variablenliste (z.b. für Mods)


FAQ:

- Falls irgendwo guids von 0 angezeigt werden, ist dies ein BUG im Servercode von COD2 1.0 - nicht im rconTool
- Falls das Bannen nicht funktioniert, ist warscheinlich dann die guid=0 gewesen. Somit ist ein bannen auch nicht möglich.
- Falls ein Tempban nicht funktioniert, *dürfte* das ein BUG im Servercode sein.
- Falls Einstellungen nicht übernommen werden, liegt ein Schreibschutz auf den Dateien bzw auf dem übergeordneten Ordner, in dem die rcon.exe drin liegt!

Version 1.04, aber schaut besser bei http://www.xenon-clan.de nach der aktuellsten!


Call of Duty2 Patch 1.2 Linux Call of Duty2 Patch 1.2 Linux Tuesday 15th 2608 August 2017 | 31.040,0 kB
Call Of Duty 2(tm)
Linux Multiplayer Server Code
Version 1.2c
Readme
Last update: 2006-04-13
=============================

!! IMPORTANT !!
 Call of Duty 2(tm) Linux Server is NOT SUPPORTED by Activision(r) Customer
 Support. Please do not call with any questions related to this free beta
 product. There are other channels to aid you listed at the bottom of this
 document.


===============================================

TABLE OF CONTENTS

1. Introduction
2. Upgrading from 1.0 or 1.0a to Linux 1.2
3. Installation From Scratch
4. Support Channels
5. FreeBSD Note
6. Revision History
===============================================


1. Introduction

 This document explains how to install the Call of Duty 2(tm) Linux server
 version 1.0. Installation from scratch and upgrading an existing installation
 are both covered.

 Usage is very similar to Call of Duty(tm) and United Offensive(tm)... many
 of the console commands, command lines, and cvars are identical, so if you
 are comfortable maintaining dedicated servers for those games, you will find
 this process familiar.

 MOD USERS: PLEASE READ...
  It is recommended that any user modifications that have been
  installed to the Call of Duty 2(tm) directory be removed before
  installing this package. These modifications are not supported
  by Activision(r) and may not be compatible with some of the new
  features that are included. When installing or upgrading a server,
  if problems or unexpected behavior arise, your first step in
  troubleshooting should be to do a clean install with the original
  data files.

 IF YOU HAVE A PROBLEM WITH "LIBSTDC++.SO.5" ...
  (This is a frequent-enough problem to merit discussion in the introduction.)

  If you are reading this, it's probably because you tried to start your Linux
   server and saw this message:

    ./cod2_lnxded: error while loading shared libraries: libstdc++.so.5:
     cannot open shared object file: No such file or directory

  COD2 is a C++ program built with gcc 3.3.6, which means it needs a
  system library specific to gcc 3.3. Older Linux systems won't have
  this installed, and we're starting to see newer Linux distributions that
  don't have this either, since they are supplying an incompatible
  gcc 3.4 version. The good news is that you can drop the needed library
  into your system without breaking anything else.

  Here is the library you need, if your Linux distribution doesn't supply it:
    http://icculus.org/updates/cod/gcc3-libs.tar.bz2

  You want to unpack that somewhere that the dynamic linker will see it
  (if you are sure it won't overwrite any files, you can even use /lib).

  The brave can put it in the same directory as the game and run the server
  like this:
     LD_LIBRARY_PATH=$LD_LIBRARY_PATH:. ./cod2_lnxded

  Now the server will start.

2. Upgrading from 1.0 or 1.0a to Linux 1.2.

 Stop the game server, unpack this archive so that it overwrites cod2_lnxded
  on your server and adds files to the "main" directory. A "pb" directory will
  also be added. Now restart the game server. If you have any problems, please
  remove any installed mods before reporting bugs to verify that this is in
  fact an issue in the game itself.


3. Installation From Scratch

 - Get the retail Call of Duty 2(tm) disc(s) (there may be multiple discs
   depending on what edition of the game you have obtained, or perhaps a
   single DVD-ROM disc).
 - Copy the contents of Disc One's "Setup/Data" directory to wherever you
   want to install the Call of Duty 2(tm) Linux server. There should be a
   "localization.txt" file in the root of this directory, and a "Main"
   Subdirectory.  Each additional disc should be opened and the contents of
   each "Data" folder should be copied over to the existing Main folder. When
   you have copied everything, the final installation size is around 3.5
   gigabytes.
 - Alternately, you may install on Windows(r) and copy the installed game to
   your Linux system, but many will opt to skip this step since the data
   files are uncompressed and easily accessible on the discs. Final
   installation size is around 3.5 gigabytes.
 - Unpack this archive in the root of the newly-copied tree, so
   "cod2_lnxded" is in the same directory as "localization.txt". Unlike the
   original Call of Duty(tm), there are not seperate .so files like
   "game.mp.i386.so", so don't be concerned when you don't see them.
 - Now, run the server:
     cd /where/i/copied/callofduty2
     ./cod2_lnxded

 - When you see "--- Common Initialization Complete ---", the game
   server has started, but you need to start a map before the server will
   accept connections. At this point, type:

     map mp_leningrad

   ("mp_leningrad" being a given map's name).

 - Now you should see your server in the in-game browser. You will now want to
   customize your server, but that is beyond the scope of this document.


4. Support Channels

 There are a LOT of knobs you can tweak to customize and automate your server,
 but it is beyond the scope of this documentation. Please refer to the
 admin manuals for any Quake 3(tm) based Multiplayer game (including Quake 3
 Arena(tm), Return to Castle Wolfenstein(tm), the original Call of Duty(tm)
 and United Offensive(tm), etc) for specifics.

 There is a mailing list for discussion and support of Linux servers for all
 of the Call of Duty(tm) games and expansion packs. Hundreds of experienced
 server admins and even some of the game's developers monitor this list, and
 are eager to help with politely-asked questions. Send a blank email to
 cod-subscribe@icculus.org to get on the list, and list archives can be seen
 at:

   http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?38

 Bug reports should NOT be sent to the list. We have a web-based
 bugtracking system for this. If you don't report bugs there, we don't
 promise to even be aware of them, let alone fix them! You can find the bug
 tracker here:

   https://bugzilla.icculus.org/


 Also, http://callofduty.com/ and http://infinityward.com/ may direct you to
 important information, documentation and current news about Call of Duty(tm)
 titles.


5.  FreeBSD users

 This server is known to work on FreeBSD with the Linux binary compatibility
 layer. If it doesn't, we consider it a bug and appreciate the report since we
 won't necessarily be testing on FreeBSD ourselves. Please note that the
 game server requires that you use at least the linux_base-8 package for
 binary compatibility (it has a C++ runtime library we now need that previous
 linux_base packages don't supply...alternately, see notes about libstdc++ in
 this document's introduction if you can't or won't update linux_base).

6.  Revision history

  • 04-10-2006: (1.2)  apparently leaked version.
  • 04-13-2006: (1.2a) Fixed BG_IndexForString crash, other memory access bugs.
  • 04-19-2006: (1.2b) Fixed mods with localized strings.
  • 04-19-2006: (1.2c) Fixed crash on disconnect.
// end of README.linux ...

Call of Duty2 Patch 1.2 Windows Call of Duty2 Patch 1.2 Windows Tuesday 15th 2608 August 2017 | 33.359,4 kB
his Call of Duty® 2 Multiplayer 1.2 Upgrade will bring all supported versions of Call of Duty® 2 up to version 1.2, and includes the multi-core processor optimizations contained in the 1.01 upgrade.

This update supports US/UK English, French, German, Spanish, Italian, Polish, Russian, Czech, Japanese, Chinese Traditional, Chinese Simplified, and Korean language versions of Call of Duty 2 only.

FEATURES:

The Call of Duty® 2 Multiplayer 1.2 Upgrade adds the following features... - Optional PunkBuster™ anti-cheat technology for online play! - HTTP Redirect functionality for servers running Mods or custom maps. - "Message Of The Day" functionality for multiplayer server messages which will appear on the client's Welcome Screen. - Improved multiplayer spawning on all maps designed to reduce the likelihood of spawning near enemy players. - Two new multiplayer maps: Harbor, and Rhine!

FIXES:

- Rare AMD dual-core bug in single player that stopped health regeneration. - Client exploit that could cause multiplayer servers to crash. - Numerous multiplayer exploit fixes.
Additional Information can be found <readme>
File name: CallofDuty2Patchv1_2.exe
File size: 33.0MB
Patch 1.3 LINUX Patch 1.3 LINUX Tuesday 15th 2608 August 2017 | 31.790,0 kB
cod2-lnxded-1.3-06232006
Call Of Duty 2(tm)
Linux Multiplayer Server Code
Version 1.3
Readme
Last update: 2006-06-14
=============================

!! IMPORTANT !!
 Call of Duty 2(tm) Linux Server is NOT SUPPORTED by Activision(r) Customer
 Support. Please do not call with any questions related to this free beta
 product. There are other channels to aid you listed at the bottom of this
 document.


===============================================

TABLE OF CONTENTS

1. Introduction
2. Upgrading to 1.3.
3. Installation From Scratch
4. Support Channels
5. FreeBSD Note

===============================================


1. Introduction

 This document explains how to install the Call of Duty 2(tm) Linux server
 version 1.3. Installation from scratch and upgrading an existing installation
 are both covered.

 Usage is very similar to Call of Duty(tm) and United Offensive(tm)... many
 of the console commands, command lines, and cvars are identical, so if you
 are comfortable maintaining dedicated servers for those games, you will find
 this process familiar.

 MOD USERS: PLEASE READ...
  It is recommended that any user modifications that have been
  installed to the Call of Duty 2(tm) directory be removed before
  installing this package. These modifications are not supported
  by Activision(r) and may not be compatible with some of the new
  features that are included. When installing or upgrading a server,
  if problems or unexpected behavior arise, your first step in
  troubleshooting should be to do a clean install with the original
  data files.

 IF YOU HAVE A PROBLEM WITH "LIBSTDC++.SO.5" ...
  (This is a frequent-enough problem to merit discussion in the introduction.)

  If you are reading this, it's probably because you tried to start your Linux
   server and saw this message:

    ./cod2_lnxded: error while loading shared libraries: libstdc++.so.5:
     cannot open shared object file: No such file or directory

  COD2 is a C++ program built with gcc 3.3.4, which means it needs a
  system library specific to gcc 3.3. Older Linux systems won't have
  this installed, and we're starting to see newer Linux distributions that
  don't have this either, since they are supplying an incompatible
  gcc 3.4 version. The good news is that you can drop the needed library
  into your system without breaking anything else.

  Here is the library you need, if your Linux distribution doesn't supply it:
    http://icculus.org/updates/cod/gcc3-libs.tar.bz2

  You want to unpack that somewhere that the dynamic linker will see it
  (if you are sure it won't overwrite any files, you can even use /lib).

  The brave can put it in the same directory as the game and run the server
  like this:
     LD_LIBRARY_PATH=$LD_LIBRARY_PATH:. ./cod2_lnxded

  Now the server will start.

2. Upgrading to 1.3

 Just stop the game server, replace cod2_lnxded, etc on your server with the
  files included in this package, and restart the game server.


3. Installation From Scratch

 - Get the retail Call of Duty 2(tm) disc(s) (there may be multiple discs
   depending on what edition of the game you have obtained, or perhaps a
   single DVD-ROM disc).
 - Copy the contents of disc ones "Setup/Data" directory to wherever you
   want to install the Call of Duty 2(tm) Linux server. There should be a
   "localization.txt" file in the root of this directory, and a "Main"
   Subdirectory.  Each additional disc should be opened and the contents of
   each "Data" folder should be copied over to the existing Main folder. When
   you have copied everything, the final installation size is around 3.5
   gigabytes.
 - Alternately, you may install on Windows(r) and copy the installed game to
   your Linux system, but many will opt to skip this step since the data
   files are uncompressed and easily accessible on the discs. Final
   installation size is around 3.5 gigabytes.
 - Unpack this archive in the root of the newly-copied tree, so
   "cod2_lnxded" is in the same directory as "localization.txt". Unlike the
   original Call of Duty(tm), there are not seperate .so files like
   "game.mp.i386.so", so don't be concerned when you don't see them.
 - Now, run the server:
     cd /where/i/copied/callofduty2
     ./cod2_lnxded

 - When you see "--- Common Initialization Complete ---", the game
   server has started, but you need to start a map before the server will
   accept connections. At this point, type:

     map mp_leningrad

   ("mp_leningrad" being a given map's name).

 - Now you should see your server in the in-game browser. You will now want to
   customize your server, but that is beyond the scope of this document.


4. Support Channels

 There are a LOT of knobs you can tweak to customize and automate your server,
 but it is beyond the scope of this documentation. Please refer to the
 admin manuals for any Quake 3(tm) based Multiplayer game (including Quake 3
 Arena(tm), Return to Castle Wolfenstein(tm), the original Call of Duty(tm)
 and United Offensive(tm), etc) for specifics.

 There is a mailing list for discussion and support of Linux servers for all
 of the Call of Duty(tm) games and expansion packs. Hundreds of experienced
 server admins and even some of the game's developers monitor this list, and
 are eager to help with politely asked questions. Send a blank email to
 cod-subscribe@icculus.org to get on the list, and list archives can be seen
 at:

   http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?38

 Bug reports should NOT be sent to the list. We have a web-based
 bugtracking system for this. If you don't report bugs there, we don't
 promise to even be aware of them, let alone fix them! You can find the bug
 tracker here:

   https://bugzilla.icculus.org/


 Also, http://callofduty.com/ and http://infinityward.com/ may direct you to
 important information, documentation and current news about Call of Duty(tm)
 titles.


5.  FreeBSD users

 This server is known to work on FreeBSD with the Linux binary compatibility
 layer. If it doesn't, we consider it a bug and appreciate the report since we
 won't necessarily be testing on FreeBSD ourselves. Please note that the
 game server requires that you use at least the linux_base-8 package for
 binary compatibility (it has a C++ runtime library we now need that previous
 linux_base packages don't supply...alternately, see notes about libstdc++ in
 this document's introduction if you can't or won't update linux_base).

// end of README.linux ...