Download

This article describes all aspects of downloading the latest version of PARPG and how to get it running. All of the following steps are mandatory to get PARPG running on your system, therefore none of them can be skipped.

Installing Python & Python-libraries
As PARPG is written in Python, you'll need a working Python interpreter installed to run the game. Furthermore PARPG utilizes the pyyaml Python library and therefore does not run without it.

Linux
For Linux make sure that you install the latest release of the Python 2.5.x or 2.6.x branch. Py3k will NOT work. On most distros this should be the norm: open up a console and type python --version to check.

Instructions for installing PyYAML in linux can be found on the PyYAML wiki. Just download the sources, extract them and run as root:

If you are using a debian based system you can grab it from your repositories with the following command.

Win32

 * 1) Download and install ActivePython 2.6. Note: this is of course only needed if you don't have Python 2.6 installed yet. Python <= 2.5 as well >= 3.0 will NOT work.
 * 2) Once you've installed Python, grab the latest release of PyYaml for Python 2.6 and install it: http://pyyaml.org/download/pyyaml/PyYAML-3.09.win32-py2.6.exe

Getting the game engine
PARPG is based on the open source game engine FIFE. In the current stage of development we're using the latest SVN snapshot of FIFE for PARPG. You'll need a Subversion client to get your hands on the latest version of the engine.

Linux
Firstly you'll need svn, so for Debian and variants (including Ubuntu) firstly:

After that: . This will put the FIFE directory in the current working directory.

Win32

 * 1) If you don't have an SVN client installed yet, download and install TortoiseSVN.
 * 2) Once you got your SVN client installed create a new folder for the game engine (called  from now on) and CD into it. Important: you should avoid non-ASCII characters in the FIFE directory path. The build process is known to be prone to errors caused by unconventional characters in the directory path.
 * 3) Download the latest FIFE version by checking out the content of http://fife.svn.cvsdude.com/engine/trunk/ into .

Getting PARPG
Now we'll grab the PARPG specific code and assets from their Subversion repository. Paths are hardcoded at the moment so you'll need to follow this guide and utilize the folder structure mentioned below. We can reorganize the structure later but for the ease of getting started, we'll work with this structure for now.

Win32

 * 1) CD into /clients/ and create a folder there.
 * 2) Check out the latest version from http://parpg-svn.cvsdude.com/parpg/trunk/game/ into /clients/.

Building the game engine
As PARPG is based on the FIFE game engine, we'll need to build the engine from sourcecode first before we can actually test PARPG. Don't worry: it sounds way more complicated than it is in reality. Simply stick to the following steps, depending on the operating system that you're running.

Linux

 * 1) Install the dependencies listed here: http://wiki.fifengine.de/Build_dependencies
 * 2) CD into  and run:

Mac OS X

 * 1) WARNING: 10.5 (Tiger) only, not the new one
 * 2) use mac ports and scons
 * 3) follow these instructions: http://wiki.fifengine.de/Building:Mac:Scons
 * 4) do not use scons ext=1, just scons to build, use ports to install the libraries (same as linux)

Win32

 * 1) Get the latest version of FIFE Win32 DevKit. The DevKit is a complete package to build FIFE from source on Win32 systems. It contains needed build tools (mingw, scons, swig), all dependencies as precompiled static and dynamic libraries and their corresponding headers. You can grab the latest version here:
 * 2) * 7zip archive version: https://sourceforge.net/projects/fife/files/active/sdks/FIFE_Win32_DevKit_Nov2009.7z/download
 * 3) * Installer version: https://sourceforge.net/projects/fife/files/active/sdks/FIFE_Win32_DevKit_Nov2009.exe/download
 * 4) Unpack / install the Win32 DevKit to \build\win32.
 * 5) Optional step: CD into \build\win32\ and run update_project_files.bat. This step is just needed if you plan to build the engine with a different compiler than mingw.
 * 6) CD into \build\win32\build_environments\scons\ and run logbuild_engine.bat. FIFE will now get built using the mingw compiler that comes with the DevKit. Other compilers and IDEs are supported as well (Code::Blocks, MSVC2005, MSVC2008) but the build process for them is not explained in the detail here. If you would like to build FIFE with a different compiler, check out the build guides at the FIFE wiki: http://wiki.fifengine.de/Guides_%26_tutorials#Win32.
 * 7) Wait until the console window that has popped up after you ran logbuild_engine.bat has closed again. FIFE should have been successfully compiled now. A detailed build report is written to \build\win32\build_environments\scons\engine_build_log.txt.

Starting PARPG
We're ready to start PARPG now! Caution: not much to see at this point as we're still moving towards a first techdemo release; so don't be disappointed due the lack of any gameplay at the moment.

Win32

 * 1) CD into \build\win32 and run update_dlls_mingw.bat. It will copy the needed engine DLLs into the right folder so you can start the game later. Note: this step is only needed when you're running PARPG for the first time or if you've updated the Win32 DevKit or recently built FIFE with a different compiler.
 * 2) CD into \build\win32\binaries\mingw and run oalinst.exe if you're running PARPG for the first time. This will install OpenAL drivers to ensure that the sound is working fine.
 * 3) CD into \clients\ and run the Python script run.py by doubleclicking on it. It should be automatically associated with the Python interpreter of your system in case you're using ActivePython. If you're using a different Python distribution you might need to manually associate Python scripts with the interpreter on your system.