[cod] CoD:World at War 1.2 Linux bits

Fri Feb 20 18:59:19 EST 2009

Thanks guys. One question. I uploaded 1.0 files some time ago and now I'm
uploading linux server. It's all I need or maybe I should upload also some
files from 1.1 or 1.2 client side? Thanks in advance.

Best regards,
Damien

2009/2/21 James Landi <jim at landi.net>

> Joker is uploading the files as I write this and will have his usual fast
> mirrors up ASAP.
>
> I wanted to pass along the readme and file size
>
> File is 415.9MB
>
> Readme:
>
> Call Of Duty: World at War(tm)
> Linux Multiplayer Server Code
> Version 1.2
> Readme
> Last update: 2009-02-08
> =============================
>
> !! IMPORTANT !!
> Call of Duty: World at War(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. Installation From Scratch
> 3. Note for localized versions of the game
> 4. Support Channels
> 5. FreeBSD Note
>
> ===============================================
>
>
> 1. Introduction
>
> This document explains how to install the Call of Duty: World at War(tm)
> Linux server version 1.2. Installation from scratch and upgrading an
> existing
> installation are both covered.
>
> Usage is very similar to other Call of Duty(tm) titles ... 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: World at War(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.
>
> 2. Installation From Scratch
>
> - Get the retail Call of Duty: World at War(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). You may also use the data files from a
> copy
>  of the game purchased via Steam(tm).
> - Install the game on Windows.
> - Copy the installed game to your Linux system. Final installation size is
>  around 6.8 gigabytes.
> - Please make sure you transfer the data as BINARY and not TEXT or ASCII if
>  you use the FTP protocol to upload the files!
> - Unpack this archive in the root of the newly-copied tree, so
>  "codwaw_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.
>  Files such as main/iw_12.iwd need to go into the correct subdirectories;
>  make sure they don't lose the path information and all copy into the base
>  directory!
>
> - OPTIONAL: Install PunkBuster:
>
>    mkdir -p ~/.codwaw
>    ./pbsetup.run -e
>    ./pbsetup.run --add-game=waw --add-game-path=~/.codwaw
>    ./pbsetup.run -u
>
>  You will need to agree to the PunkBuster license before you may install
> it.
>  This will download the latest version of the Punkbuster software to your
>  Linux server, so you need an Internet connection.
>
> - Now, run the server:
>    cd /where/i/copied/codwaw
>    ./codwaw_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_castle
>
>  ("mp_castle" 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, including writing config files and command lines
>  that don't require human interaction, but that is beyond the scope of this
>  document.
>
>
> 3. Note for localized versions of the game
>
> If you have a copy of the game that does not include the English
> translations,
> you will need to explicitly set the game's language or the server will not
> be able to find its data files. If you have, for example, the French data
> files, you must add this to your server's command line:
>
>  ./codwaw_lnxded +set loc_language 1
>
> This is a list of values for various languages. English installations can
> ignore this.
>
>  English (default): +set loc_language 0
>  French: +set loc_language 1
>  German: +set loc_language 2
>  Italian: +set loc_language 3
>  Spanish: +set loc_language 4
>
>
> 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 at 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://activision.com/ may direct you to
> important information, documentation and current news about Call of
> Duty(tm)
> titles.
>
>
> 5.  FreeBSD Note
>
> 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.
>
> // end of README.linux ...
>
> Jim Landi
> Rudedog
> FPSadmin.com
> Microsoft MVP, Games for Windows
>
> ---
> To unsubscribe, send a blank email to cod-unsubscribe at icculus.org
> Mailing list archives: http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?38
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/cod/attachments/20090221/f4ef1d8a/attachment.htm>