Skip to content
A reimplementation of BioWare's Aurora engine (and derivatives). Pre-pre-alpha :P
C++ C Other
Find file
Latest commit 797fe6c @DrMcCoy DrMcCoy DIST: Remove iconv autotools files from .gitignore
They're checked in, after all.
Failed to load latest commit information.
build-aux BUILD: Use aux directory to store autogenerated files
cmake BUILD: Add GPLv3+ license header to CMake files
dists RELEASE: This is version 0.0.4
doc DOCS: Add a note about xoreos.conf encoding, with example
gitstamp BUILD: Add short description to each directory's
glew BUILD: Add short description to each directory's
lua DOCS: Add full Lua license text
m4 BUILD: Update the iconv autotools macro files
man DOCS: Rewrite manpage to use semantic -mdoc macros
src GRAPHICS: Fix manual decompression of NPOT DXT data
utf8cpp BUILD: Add short description to each directory's
.gitignore DIST: Remove iconv autotools files from .gitignore
.travis.yml BUILD: Roll back the conversion to the new Travis CI infrastructure BUILD Try the new Coverity Scan Travis upload URL
.uncrustifyrc CLEANUP: Don't force all if branches to same brace style
AUTHORS DOCS: Add a paragraph about Nintendo DS formats to AUTHORS DOCS: Fix required MAD version in the file
CMakeLists.txt RELEASE: This is version 0.0.4 DOCS: Update Code of Conduct to Contributor Coventant 1.4.0 DOCS: Add a Code of Conduct
COPYING ALL: Relicense eos from GPLv2+ to GPLv3+
COPYING.Arev DOCS: Add full Bitstream Vera license texts
COPYING.Bitstream DOCS: Add full Bitstream Vera license texts
COPYING.GPLv2 DOCS: Add full GPLv2 license text
COPYING.LGPLv2.1 DOCS: Add full LGPLv2.1 license text
ChangeLog RELEASE: This is version 0.0.4
Doxyfile RELEASE: This is version 0.0.4 DOCS: Expand the toolset FAQ entry a bit DOCS: Add full LGPLv2.1 license text
Makefile.common BUILD: Make autotools build system specify the C/C++ standard RELEASE: This is version 0.0.4 DOCS: Link the doxygen documentation from the
TODO DOCS: The TODO moved to our wiki BUILD: Add GPLv3+ license header to autotools files RELEASE: This is version 0.0.4

xoreos README

xoreos is an open source implementation of BioWare's Aurora engine and its derivatives, licensed under the terms of the GNU General Public License version 3 (or later). The goal is to have all games using this engines working in a portable manner, starting from Neverwinter Nights and ending with Dragon Age II.


The following games are valid targets for xoreos:

Status Build Status Coverity Status

Currently, the "foundation" work of managing resources, reading many basic file formats, displaying graphics and playing sounds has been done. All targeted games show partial ingame graphics, such as the area geometry and objects, letting you fly around in a "spectator mode". Some games show partial menus, and something resembling a starting point for a script system is there.

No actual "normal" gameplay is implemented yet, though.

For further information about the status of specific games, please visit our wiki.

Note: We are always looking for people to join our efforts in reimplementing those games. If you'd like to help, feel free to contact us! Please also read over our for some guidelines. Thanks.

Getting xoreos

You can get xoreos in multiple ways:

You can download an archive with a binary of the latest release from our downloads page. This includes binaries for Microsoft Windows, Mac OS X and GNU/Linux, as well as packages for various GNU/Linux distributions. All of them are available for both 32- and 64-bit x86 architectures.

Or, if you're running Arch Linux, you can install xoreos directly from the AUR.

Lastly, you can compile xoreos yourself; either from a release source package, found on our downloads page, or a fresh repository checkout. For details on how to compile xoreos on various operating system, please read the Compiling xoreos page on our wiki.

Running xoreos

First, you need to fully install and/or copy the game you want to play with xoreos onto your hard disk. How you do this depends on the game, your operating system and where/how you have bought the game.

xoreos does not yet have a launcher GUI or anything like this. You need to start it from the command line. Run xoreos with the command line option "--help" (without the quotes) to get a help text about further command line options.

The quickest way to start a game in path /path/to/game/ would be to call

xoreos -p/path/to/game/

If you're on Windows and the path is, say, D:\Path\To\Game\, call

xoreos -pD:\\Path\\To\\Game\\

For a more in-depth documentation on how to run xoreos, please also read the Running xoreos page on our wiki.

Config file

In general, xoreos can read the configuration which game to run from either the command line, a config file or both. Additionally, when you first specify a new game on the command line, xoreos will add a related entry in the config file (creating it first, if necessary).

To accurately identify a specific instance of an installed game, xoreos uses the concept of a "target". Each target has a separate section in the config file, and each of their options apply only to that target. The special target "xoreos" is a global section applying to all games, although the same option in a game target overrides the global option.

For example:



You can then start the game with the target "nwn" with

xoreos nwn

and xoreos will do the rest. This will start the game in the path /home/drmccoy/games/nwn/, running it in fullscreen at 1024x768.

As you can see with the volume options, xoreos also saves settings you made in the game' actual GUI into the target's section of the config file.

The place where xoreos expects the config file depends on your operating system:

  • On GNU/Linux, the place is $XDG_CONFIG_HOME/xoreos/xoreos.conf. $XDG_CONFIG_HOME defaults to $HOME/.config/
  • On Mac OS X, the place is $HOME/Library/Preferences/xoreos/xoreos.conf
  • On Windows, xoreos.conf is in the subdirectory xoreos in either $APPDATA or $USERPROFILE, depending on your Windows version

For a more elaborate example with more in-depth explanations, please see xoreos.conf.example in the doc directory, or the Running xoreos page on our wiki.



To contact us, please either write to mailing list, or join our IRC channel #xoreos on Freenode.

Something went wrong with that request. Please try again.