First of all, welcome to the Wolfpack community.

If you find yourself with problems, don't hesitate in asking for help. There are many ways to get help, including IRC (irc://irc.freenode.net/wolfpack) support, forums (http://www.hoogi.de/wolfpack/forum/) and IM.

There are a few different ways to get the binaries and script packages you will need to install wolfpack. Windows users have the luxury of an all-in-one install package, in addition to snapshots of binaries. Linux users unfortunally need to do a bit more of manual labor, by compiling a binary and downloading scripts.

You can access the svn repository via http://developer.berlios.de/svn/?group_id=2490 http://www.hoogi.de/websvn/listing.php?repname=wolfpack with your browser.

The easiest way to get the current development version ist to directly check it out from the svn. Open a console and go to the preferred location in yor filesystem hierarchy. Then

svn checkout svn://www.hoogi.de/wolfpack/trunk/server wolfpack

This copies all required files for the server(!) out of the svn repository to the directory wolfpack. Follow the instructions below on this page to get a executable.

You find all definitions and scripts in the release folder. You dont need to download them somewhere else.

Having a running server, the next step is to customize your world. Have fun!

The binary snapshots are avaliable at ftp://ftp.berlios.de/pub/wolfpack/

These zip files contains only precompiled exe and required dlls. The scripts have to be downloaded from the SVN repository.

see also Compile Instructions

You can get the latest development version from the svn repository:

svn checkout svn://svn.berlios.de/wolfpack/trunk/server wpserver

cd wpserver/build
./configure.py
cd ../boost
qmake
make
cd ../build
qmake
make

After successful building the project, change to the ../release folder. There your brand new wolfpack executable resides.

Start the server with ./wolfpack. You will get some error messages, but a new configuration file wolfpack.xml is created. Adjust the file to match your wishes, set LoginServer, MulPath etc..

You should use locations according to the Filesystem Hierarchy Standard. Because you compiled the package on your own, be sure always use the local hierarchy.

Now you need some UO-Files. You could copy them to e.g. /usr/local/share/games/UO. At least the following files are required (total 158M):

map0.mul (86M)
map2.mul (11M)
map3.mul (16M)
map4.mul (6,2M)
mapdif0.mul (269K)
mapdif1.mul (1,6M)
mapdif2.mul (52K)
mapdifl0.mul (5,5K)
mapdifl1.mul (32K)
mapdifl2.mul (1,1K)
multi.idx (96K)
multi.mul (579K)
stadif0.mul (144K)
stadif1.mul (1,1M)
stadif2.mul (189K)
stadifi0.mul (22K)
stadifi1.mul (129K)
stadifi2.mul (3,2K)
stadifl0.mul (7,1K)
stadifl1.mul (43K)
stadifl2.mul (1,1K)
staidx0.mul (5,3M)
staidx2.mul (675K)
staidx3.mul (960K)
staidx4.mul (384K)
statics0.mul (22M)
statics2.mul (2,5M)
statics3.mul (2,2M)
statics4.mul (1,2M)
tiledata.mul (1012K)

At the moment (svn rev 6789) the daemon-mode seems not to work. You can start the server with the screen command (you need to install the debian package with the same name):

screen ./wolfpack

After the startup you can detach from the terminal with CTRL-A D.

If you logout and relogin anytime later you can reattach to the wolfpack server. You can list the screens with screen -list. Assuming there ist only one screen running, you can easily reattach with

screen -R

This complete procedure works very fine for an remote server.

• QT4
• python
• libboost-python

In Debian there exists a user/group called games/games, so your server and files should be chowned to that user/group.

For the ongoing .deb-package here is a list of files and places in the filesystem (according to FHS 2.3):

• executable: /usr/games/wolfpack
• configuration: /etc/wolfpack.xml
• sysv-script: /etc/init.d/wolfpack
• documentation (AUTHORS, README, …): /usr/share/doc/wolfpack/
• scripts: /usr/share/wolfpack/scripts/
• definitions: /usr/share/wolfpack/definitions/
• variable data (accounts.db, world.*): /var/games/wolfpack/
• logfiles: /var/log/wolfpack/ (no manual rotation needed, this is done by Debian)