There are many new things in Wolfpack 13.x.x
A small list of what's new:

• A new database world save format, SQLite and MySQL.
• A new scripting engine powered by Python 2.3.
• A new XML data storage to replace the old SCP system.
• Latest client support for versions such as Mondain's Legacy.
• Client Encryption Support

For a more verbose changelog:

• http://doc.wpdev.org/ChangeLog.wolfpack

Confirmed supported platforms include:

• Windows
• Linux
• BSD

While this remains currently untested, here are some recommendations.

Minimum:

• 128 MB of RAM.
• A processor of at least 400mhz.
• At least 250 MB of free hard drive space.

Recommended:

• 256 MB of RAM or greater.
• A processor of at least 800mhz.
• At least 500 MB of free hard drive space.

Naturally, the better your hardware the better your server's performance will be.

There are two things you should install and run Wolfpack 13.x.x.

For Windows:

• The latest Python-2.3 or Python-2.4 release.

For Linux/BSD:

• The Latest QT-4.1 Release.
• The latest Python-2.3 or Python-2.4 release.

First you need the latest QT-4.1.x release for your linux distribution.
You will also need the dev package for this version of QT.
Second you need the latest release of Python 2.4 or Python 2.3.
You will also need the dev package for this version of Python.

Distribution Notes

Debian:

• Recommended that you use Debian Unstable for latest packages.
• QT4 Packages: libqt4-core libqt4-debug libqt4-gui libqt4-qt3support qt4-dev-tools
• Python Packages: python2.3 python2.3-dev or python2.4 python2.4-dev
• Recommended Packages: python2.3-mysqldb python2.3-sqlite python2.3-xml libsqlite0 libsqlite0-dev sqlite sqlite-doc
• MySQL Packages: libmysqlclient-dev libmysqlclient12 mysql-client mysql-common mysql-server

Compiling Instructions:

Compiling Instructions:

The simple answer for this is no.

• Wolfpack 13.x.x no longer uses or supports the old WSC save system. This has been replaced with a database save system.
• Wolfpack 13.x.x will use spawn scripts for filling in NPCs and there are commands available for adding missing world objects.

However, if you do wish to try and use it there is an import command which supports WSC/TXT/Sphere save formats. Please note this will NOT import NPCs!
It is recommended that you look into using the decoration command as an alternative to using import.

You can find Wolfpack documentation at: http://doc.wpdev.org/
You can find Python documentation at: http://python.org/doc/2.3.5/ or http://python.org/doc/2.4.1/

This problem should only occur with versions prior to Wolfpack 12.9.8.

This problem is mostly common with Linux/BSD. Python on many distributions comes compiled using UCS4 for Unicode. Wolfpack currently requires that Python-2.3 be compiled with UCS2 for Unicode. If this is the case, you will need to download and manually compile Python and add the `--enable-unicode=ucs2 --enable-shared` to the ./configure arguments. After this you can install the custom Python to your /usr/local/ directory or anywhere else you prefer. Please be sure to put this new python path in the Wolfpack configure.py arguments!

Python Fix / Compiling Instructions:

At this point you need to recompile Wolfpack.
For information reguarding compiling, please check out:

• Linux Compile Guide
• BSD Compile Guide

Before anything, we recommend that you check the bug tracker to see if it has already been reported.
If you find a new bug there are a few things you can do:

• You can report the bug at: http://bugs.wpdev.org/
• You can contact a developer by Email/IRC/IM
• You can check the sourceforge mailing lists.

First of all, we are trying to conform to an OSI like world. So please check that your creation(s) are along those requirements.
If so, then there are a few things you can do:

• You can contact a developer by Email/IRC/IM
• You can check the sourceforge mailing lists.

We try our best to give credit where it is due. If we receive contributions from non developers we will generally include comments about the author. :)

Please visit this page: http://developer.berlios.de/svn/?group_id=2490

The easiest way is to make sure your server settings and client settings are correctly configured.
Please check your login.cfg in your Ultima Online installation directory so that it resembles this.
Now, after you've checked your Client's login configuration, please check your wolfpack.xml file in your Wolfpack director so that it resembles this.
We support the encryption for the latest clients, so using programs like UOGateway, Ignition, UORice, etc. is completely optional and not required.

First of all, please check out "How do I connect to Wolfpack?" to see if that resolves your problem.

If not, then this problem usually occurs when players try to connect to Wolfpack using an outdated client. Due to many packet changes over the years, it has become hard to continue supporting clients below the 4.0.0 value. The Age of Shadows Client is the one we continue to support, and the UO:R client may also work as well. So, if you have this problem, please try running uopatch.exe that is in your Ultima Online Installation to upgrade.
If this fails, you can try finding the free Age of Shadows Demo Using Google.

By default, Wolfpack uses TCP ports 2592 and 2593.
Optionally you can enable TCP port 2594 which is for the remote admin page.

Please Note the following:
To route to a server that's on an internal network, you need to have TCP ports 2592 and 2593 forwarded to the machines internal IP address.
For example, say your server has the Internal address of 192.168.1.101.
Login to your router (most home bought routers can be logged into) and find your forwarding/NAT configuration. Once you do that, you want to configure so that:

For a *nix router using IPTables, you can use something like this:

The simple answer to this is, when they get fixed.

You should also check the bug tracker to see if your problem is reported before asking.

Bugs, features and other issues with Wolfpack will be resolved as soon as humanly possible. But please keep in mind, this work is strictly voluntary. No one is paid for their time working on Wolfpack, and so we do this on our own free time. So please take this into consideration before hassling developers to resolve a bug. We are usually already aware of them, and we will eventually get around to it.

Wolfpack is NOT Sphere.

Wolfpack's scripts are designed to function similar to how an official UO shard would function.

If you want the scripts to function similar to those of Sphere, feel free to modify your shard's scripts to make them do so.
Please do not ask the developers or file bug reports about this!

This is a common problem we see. People need to understand that SVN scripts are meant to be used with a SVN binary. Using the bleeding edge scripts with a standard Wolfpack release will result in errors. This is because with script changes there are usually core changes to follow with them.

Please do not use SVN scripts with a release binary. SVN is for developers or for experienced users and scripters.

By default, spawn scripts are not enabled with the Wolfpack Beta releases. Spawn scripts are incomplete right now, with the exception of most vendors.
However, if you wish to enable them look in:
./definitions/spawnregions/facet_name/index.xml for a list of enabled scripts.

By default, Wolfpack will create a default account with the following properties:
Username: admin
Password: admin

Using this, there are two ways to modify accounts.
The first, and easiest would be to use the Web Admin control panel.
To access Web Admin type in http://127.0.0.1:2594/ into your browser of choice.

Substitue 127.0.0.1 for your shard's IP if it is not on your current system. The rest should be obvious.

The second method would be to login with your UO client, and use the account command to modify accounts.

The definition files, or all the *.xml files you receive with the xmlscripts package are controlled through a tree style system.

The root of the tree is:
-> ./definitions/index.xml

From this file, you will find a list of included files, and in every sub folder there should be another index.xml file that contains the files within that folder.

Example:
-> ./definitions/index.xml
  -> ./definitions/spawnregions/index.xml
    -> ./definitions/spawnregions/trammel/index.xml
      -> ./definitions/spawnregions/trammel/vendors.xml

You can also define the master index file in wolfpack.xml, as well as add custom ones.

Example in wolfpack.xml:

Script files are based off the Python language.
So before tampering with them you may want to understand what you are doing.
Also, please read the Wolfpack Documentation on script events.

However, to manage them, the default active script index is found in:
-> ./definitions/index.xml
  -> ./definitions/scripts.xml

However, all scripts are contained in the ./scripts/ folder.

There is a setting in wolfpack.xml where you can add python search paths. This is for importing scripts.
Example in wolfpack.xml:

Again, things are in a tree style form for organization.

SVN is a version control system much like CVS, but more functional for our needs. You can learn more about SVN at this site.

As for what happened to CVS, the archive still exists at SourceForge but we have moved to BerliOS for our new repository. They're a much faster host, and offer the SVN option we prefer.

Most options can be found in the wolfpack.xml file.
Examples: