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.<br><br>Best regards,<br>
Damien<br><br><br><div class="gmail_quote">2009/2/21 James Landi <span dir="ltr"><<a href="mailto:jim@landi.net">jim@landi.net</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Joker is uploading the files as I write this and will have his usual fast mirrors up ASAP.<br>
<br>
I wanted to pass along the readme and file size<br>
<br>
File is 415.9MB<br>
<br>
Readme:<br>
<br>
Call Of Duty: World at War(tm)<br>
Linux Multiplayer Server Code<br>
Version 1.2<br>
Readme<br>
Last update: 2009-02-08<br>
=============================<br>
<br>
!! IMPORTANT !!<br>
Call of Duty: World at War(tm) Linux Server is NOT SUPPORTED by Activision(r)<br>
Customer Support. Please do not call with any questions related to this free<br>
beta product. There are other channels to aid you listed at the bottom of this<br>
document.<br>
<br>
===============================================<br>
<br>
TABLE OF CONTENTS<br>
<br>
1. Introduction<br>
2. Installation From Scratch<br>
3. Note for localized versions of the game<br>
4. Support Channels<br>
5. FreeBSD Note<br>
<br>
===============================================<br>
<br>
<br>
1. Introduction<br>
<br>
This document explains how to install the Call of Duty: World at War(tm)<br>
Linux server version 1.2. Installation from scratch and upgrading an existing<br>
installation are both covered.<br>
<br>
Usage is very similar to other Call of Duty(tm) titles ... many<br>
of the console commands, command lines, and cvars are identical, so if you<br>
are comfortable maintaining dedicated servers for those games, you will find<br>
this process familiar.<br>
<br>
MOD USERS: PLEASE READ...<br>
It is recommended that any user modifications that have been<br>
installed to the Call of Duty: World at War(tm) directory be removed before<br>
installing this package. These modifications are not supported<br>
by Activision(r) and may not be compatible with some of the new<br>
features that are included. When installing or upgrading a server,<br>
if problems or unexpected behavior arise, your first step in<br>
troubleshooting should be to do a clean install with the original<br>
data files.<br>
<br>
2. Installation From Scratch<br>
<br>
- Get the retail Call of Duty: World at War(tm) disc(s) (there may be<br>
multiple discs depending on what edition of the game you have obtained, or<br>
perhaps a single DVD-ROM disc). You may also use the data files from a copy<br>
of the game purchased via Steam(tm).<br>
- Install the game on Windows.<br>
- Copy the installed game to your Linux system. Final installation size is<br>
around 6.8 gigabytes.<br>
- Please make sure you transfer the data as BINARY and not TEXT or ASCII if<br>
you use the FTP protocol to upload the files!<br>
- Unpack this archive in the root of the newly-copied tree, so<br>
"codwaw_lnxded" is in the same directory as "localization.txt". Unlike the<br>
original Call of Duty(tm), there are not seperate .so files like<br>
"<a href="http://game.mp.i386.so" target="_blank">game.mp.i386.so</a>", so don't be concerned when you don't see them.<br>
Files such as main/iw_12.iwd need to go into the correct subdirectories;<br>
make sure they don't lose the path information and all copy into the base<br>
directory!<br>
<br>
- OPTIONAL: Install PunkBuster:<br>
<br>
mkdir -p ~/.codwaw<br>
./pbsetup.run -e<br>
./pbsetup.run --add-game=waw --add-game-path=~/.codwaw<br>
./pbsetup.run -u<br>
<br>
You will need to agree to the PunkBuster license before you may install it.<br>
This will download the latest version of the Punkbuster software to your<br>
Linux server, so you need an Internet connection.<br>
<br>
- Now, run the server:<br>
cd /where/i/copied/codwaw<br>
./codwaw_lnxded<br>
<br>
- When you see "--- Common Initialization Complete ---", the game<br>
server has started, but you need to start a map before the server will<br>
accept connections. At this point, type:<br>
<br>
map mp_castle<br>
<br>
("mp_castle" being a given map's name).<br>
<br>
- Now you should see your server in the in-game browser. You will now want to<br>
customize your server, including writing config files and command lines<br>
that don't require human interaction, but that is beyond the scope of this<br>
document.<br>
<br>
<br>
3. Note for localized versions of the game<br>
<br>
If you have a copy of the game that does not include the English translations,<br>
you will need to explicitly set the game's language or the server will not<br>
be able to find its data files. If you have, for example, the French data<br>
files, you must add this to your server's command line:<br>
<br>
./codwaw_lnxded +set loc_language 1<br>
<br>
This is a list of values for various languages. English installations can<br>
ignore this.<br>
<br>
English (default): +set loc_language 0<br>
French: +set loc_language 1<br>
German: +set loc_language 2<br>
Italian: +set loc_language 3<br>
Spanish: +set loc_language 4<br>
<br>
<br>
4. Support Channels<br>
<br>
There are a LOT of knobs you can tweak to customize and automate your server,<br>
but it is beyond the scope of this documentation. Please refer to the<br>
admin manuals for any Quake 3(tm) based Multiplayer game (including Quake 3<br>
Arena(tm), Return to Castle Wolfenstein(tm), the original Call of Duty(tm)<br>
and United Offensive(tm), etc) for specifics.<br>
<br>
There is a mailing list for discussion and support of Linux servers for all<br>
of the Call of Duty(tm) games and expansion packs. Hundreds of experienced<br>
server admins and even some of the game's developers monitor this list, and<br>
are eager to help with politely-asked questions. Send a blank email to<br>
<a href="mailto:cod-subscribe@icculus.org" target="_blank">cod-subscribe@icculus.org</a> to get on the list, and list archives can be seen<br>
at:<br>
<br>
<a href="http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?38" target="_blank">http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?38</a><br>
<br>
Bug reports should NOT be sent to the list. We have a web-based<br>
bugtracking system for this. If you don't report bugs there, we don't<br>
promise to even be aware of them, let alone fix them! You can find the bug<br>
tracker here:<br>
<br>
<a href="https://bugzilla.icculus.org/" target="_blank">https://bugzilla.icculus.org/</a><br>
<br>
<br>
Also, <a href="http://callofduty.com/" target="_blank">http://callofduty.com/</a> and <a href="http://activision.com/" target="_blank">http://activision.com/</a> may direct you to<br>
important information, documentation and current news about Call of Duty(tm)<br>
titles.<br>
<br>
<br>
5. FreeBSD Note<br>
<br>
This server is known to work on FreeBSD with the Linux binary compatibility<br>
layer. If it doesn't, we consider it a bug and appreciate the report since we<br>
won't necessarily be testing on FreeBSD ourselves.<br>
<br>
// end of README.linux ...<br>
<br>
Jim Landi<br>
Rudedog<br>
FPSadmin.com<br>
Microsoft MVP, Games for Windows<br>
<br>
---<br>
To unsubscribe, send a blank email to <a href="mailto:cod-unsubscribe@icculus.org" target="_blank">cod-unsubscribe@icculus.org</a><br>
Mailing list archives: <a href="http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?38" target="_blank">http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?38</a><br>
<br>
<br>
</blockquote></div><br>