From 5b6e0a07149b148b0efa327435345f5860def895 Mon Sep 17 00:00:00 2001 From: Stijn Buys Date: Sat, 1 Dec 2012 22:23:48 +0000 Subject: Documentation update. --- doc/attributions.html | 77 ++++--- doc/index.html | 320 +++++++++++++++------------ doc/installation.html | 504 ------------------------------------------ doc/installation_develop.html | 199 +++++++++++------ doc/installation_release.html | 79 ++++--- doc/installation_source.html | 230 +++++++++++-------- doc/osirion.css | 244 ++++++++++---------- doc/starsystem_roadmap.html | 233 ++++++++++--------- doc/storyline.html | 255 ++++++++++++--------- 9 files changed, 946 insertions(+), 1195 deletions(-) delete mode 100644 doc/installation.html (limited to 'doc') diff --git a/doc/attributions.html b/doc/attributions.html index 0949b45..fce1f0d 100644 --- a/doc/attributions.html +++ b/doc/attributions.html @@ -2,7 +2,7 @@ - + Project::OSiRiON - Attributions @@ -20,34 +20,41 @@ - Home . - Downloads . - Documentation . - Forum . - Wiki . - Tracker + News . + Documentation . + Screenshots . + Downloads . + Forum . + Wiki . + Tracker -
+
-

Attributions

-

+

+ +

Attributions

+

The game data is distributed under the terms and conditions of the Create Commons Attribution-Share Alike 3.0 License.

-

+

Sound effects from the Freesound project are distributed under the terms and conditions of the - Creative Commons Sampling Plus 1.0 license. + Creative Commons Sampling Plus 1.0 license. To be replaced

+
+ -

List of data files

-

+

+ +

List of data files

+

A list of game data files in the data/base directory, with their original author and/or source.

@@ -63,8 +70,7 @@ -

Maps

-
+

Maps

@@ -382,8 +388,7 @@ -

Models

-
+

Models

@@ -411,29 +416,28 @@ -

Sounds

-
+

Sounds

sounds/engines loop00.wav - nathanshadow (Freesound) + nathanshadow Freesound sounds/engines loop01.wav - nathanshadow (Freesound) + nathanshadow Freesound sounds/engines loop02.wav - nathanshadow (Freesound) + nathanshadow Freesound @@ -441,7 +445,7 @@ sounds/engines jump_start00.wav - juskiddink (Freesound) + juskiddink Freesound @@ -458,8 +462,7 @@ -

Textures

-
+

Textures

@@ -570,6 +573,13 @@ Duael Designs & Robert Stein III + + + textures/thorn + all files + + Thorn + textures/trak @@ -581,11 +591,15 @@ - +

- + + +
- - + diff --git a/doc/index.html b/doc/index.html index 2a553a4..46fd05b 100644 --- a/doc/index.html +++ b/doc/index.html @@ -20,132 +20,160 @@ - Home . - Downloads . - Documentation . - Forum . - Wiki . - Tracker + News . + Documentation . + Screenshots . + Downloads . + Forum . + Wiki . + Tracker -
+
-
-

About

-

- Project::OSiRiON is a free space trading and combat simulation under development. - Its goal is to create an immersive universe with open gameplay inspired by classic titles such as - Privateer and - Freelancer. -

- -

- The engine is written from scratch in C++ and uses SDL, OpenGL, OpenAL, libjpeg, libpng, zlib - and the Bullet physics library. It is - a work in progress and evolves with the game as required. -

-

- The basic components are already in place: players can start a single-player game, - or join a network server. They can purchase a ship, explore the universe and earn - some cash trading cargo. Other important parts, like weapons and combat features, - are still missing. -

-

- The game aims to be fully customizable. Common and easy to edit file formats - make it trivial to change most of the game settings and world definitions. -

-

+

+ +

About

+ +

+ Project::OSiRiON is a free space trading and combat simulation under + development. Its goal is to create an immersive universe with open + gameplay inspired by classic titles such as Privateer and Freelancer. +

+ The basic components are already in place: players can start + a single-player game, or join a network server. They can purchase a ship, + explore the universe and earn some cash trading cargo. Combat features + are under development. +

+ The game aims to be fully customizable: common and easy to edit file + formats make it trivial to change most of the game settings and world definitions. + Most of the world customization can be done server-side, without the need + for clients to install additional world definitions. Packages of the latest development build are available for windows and linux.

-
- +
+ + + +
-
-

Installation

-
-

Internet

+
-

+

Internet

+ +

The website for Project::OSiRiON can be found at http://osirion.org

-

+

The community forums can be found at http://osirion.org/forum

-

+

+ Documentation can be found on the wiki at + http://osirion.org/wiki +

+

The official IRC channel is #osirion on the FreeNode IRC network.

+
+ -

Development

-

+

+ +

Development

+ +

+ The engine is written from scratch in C++ and uses common libraries + like SDL, OpenGL and OpenAL. Physics simulation is provided by the + Bullet physics library. The engine is a work in progress and evolves + with the game as required.

-

- The repositories can also be viewed online: -

+

+ The latest version of the source code and the game can be downloaded + from the Subversion repositories:

-

+

+

+The repositories can also be viewed online: +

+ + + +

The project development roadmap and an overview of open issues can be found on the - tracker. + tracker. +

+ +
-

Team

-

+

+ +

Team

+

The core team, these people work on the game and decide about its future:

@@ -165,11 +193,17 @@
+

+ +
+ -

Contributors

+
-

+

Contributors

+ +

These people created new content for the game:

@@ -186,90 +220,104 @@ +

+ +
+ -

Credits

+ - +
-

+

+ +

The source code is distributed under the terms and conditions of the GNU General Public License.

-

+

The game data is distributed under the terms and conditions of the Creative Commons Attribution-Share Alike 3.0 License.

-

+

+ See the list of attributions for more information. +

+

Copyright © 2007-2012, Project::OSiRiON

+
+ -

Acknowledgements

+
-

+

Acknowledgements

+ +

This project could not have been possible without the work of others: -

    -
  • Id Software -
  • the GtkRadiant project contributers -
  • The Quake2World community -
  • The Satgnu crew -
  • maci, for the webspace on satgnu -
  • DVSoftware for bandwidth, diskpace and CPU power -
  • NASA for their collection of freely available images -
  • Robert Kuroto for allowing me to use his texture pack -
  • Chance Ragen and Jeremy 'Jestr' Gardner for allowing me to use their planet textures -
  • Your_Face for allowing me to use his Tremulous map 'Trident' -
  • Georges 'TRaK' Grondin for allowing me to use his texture packs -
  • Thanks to bobke and blaze-x -
  • A special thanks to all =KCT= members -

-

+

    +
  • Id Software +
  • the GtkRadiant project contributers +
  • The Quake2World community +
  • The Satgnu crew +
  • maci, for the webspace on satgnu +
  • DVSoftware for bandwidth, diskpace and CPU power +
  • NASA for their collection of freely available images +
  • Robert Kuroto for allowing me to use his texture pack +
  • Chance Ragen and Jeremy 'Jestr' Gardner for allowing me to use their planet textures +
  • Your_Face for allowing me to use his Tremulous map 'Trident' +
  • Georges 'TRaK' Grondin for allowing me to use his texture packs +
  • Thanks to bobke and blaze-x +
  • A special thanks to all =KCT= members +
+

Thanks to: -

    -
  • Josky=KCT= -
  • [mDc]Minisori -
  • Gareth -
  • StalKermit -
  • DVSoftware -

-

+

    +
  • Josky=KCT= +
  • [mDc]Minisori +
  • Gareth +
  • StalKermit +
  • DVSoftware +
+

QUAKE and ID are registered trademarks of Id Software, Inc.
LEGO is a registered trademark of the LEGO Group.

-

+

Project::OSiRiON is an independent, not-for-profit project and is not affiliated with these companies.

+
+ -
+
- - + diff --git a/doc/installation.html b/doc/installation.html deleted file mode 100644 index 20464f1..0000000 --- a/doc/installation.html +++ /dev/null @@ -1,504 +0,0 @@ - - - - - - Project::OSiRiON - Installation Instructions - - - - - - - diff --git a/doc/installation_develop.html b/doc/installation_develop.html index de25f66..70de3a5 100644 --- a/doc/installation_develop.html +++ b/doc/installation_develop.html @@ -20,80 +20,94 @@ - Home . - Downloads . - Documentation . - Forum . - Wiki . - Tracker + News . + Documentation . + Screenshots . + Downloads . + Forum . + Wiki . + Tracker -
+
-

Building the development version

+ -

+

+ +

Building the development version

+ +

The latest release is usually lagging behind current development. If you want to check the latest developments for yourself, you can get the most recent source code and game data from the subversion repository.

-

+

Building the development version is very similar to building from source code. The system requirements still apply. Additionally you will need a subversion client.

- -

+ +

+ +

-

Obtaining the source code

+
-

+

Obtaining the source code

+ +

On linux, you can use the Subversion command line client tool. The following command will create a new subdirectory osirion and download the source code into it.

svn checkout svn://osirion.org/osirion osirion
-

+

On windows, you can use the Turtoisesvn SubVersion client to access the SVN repositories. You can download it here:

-
-

Obtaining the game data

-

+

+ +

Obtaining the game data

+

The game data should be located in the data subdirectory of the main distribution. You can use the game data package from the website or get it from the osirion-data subversion repository: -

+

+ +
+ -

Configuring the source code

-

+

+ +

Configuring the source code

+

Create the configure script:

autoreconf -fi
-

+

Create a build directory, If something goes wrong, or building doesn't work any more after updating, you can just delete the build directory and start over without destorying the working copy. Enter the build directory and configure the source code: @@ -120,77 +140,93 @@ cd build
../configure --with-bullet=/usr/local --enable-static-bullet

-

+

Use the --help option to get a list of all available options:

../configure --help
+

+ +
+ -

Building the binaries

-

+

+ +

Building the binaries

+

Compile the source code:

make -j2
-

+

The -j2 options tells make to use two threads while building, if you have a quad-core cpu, you can use -j4.

-

+

The binaries will be built in the src/ subdirectory of the build directory.

-

+

Important:
make install is not supported. Results are unpredictable.

-

+

Leave the build directory:

cd ..
+

+ +
+ -

Running

-

+

+ +

Running

+

The client and the dedicated server will look for game data in the data subdirectory of the current working directory. Since the binaries are build in the src you will have start them with the src/ prefix.

-

+

To start the client:

./build/src/osirion
-

+

If the client opens a new window and immediatly close it again, it probably could not find the game data and exited. Check your installation.

-

+

To start the dedicated server:

./build/src/osiriond
-

+

If you are using windows, the binaries will be called osirion.exe and osiriond.exe.

+
+ -

Updating

-

+

+ +

Updating

+

Once you downloaded the source code and the game data from the subversion repository, there is no need to re-download the entire distribution when there are updates available. You can update your local copy and rebuild it.

-

+

Update the source code:

@@ -200,7 +236,7 @@ cd ..
svn update
-

+

Update the game data:

@@ -208,7 +244,7 @@ svn update
cd ..
-

+

Rebuild the binaries:

@@ -218,39 +254,51 @@ make -j2
cd ..
+

+ +
-

Source data (optional)

-

+

+ +

Source data (optional)

+ +

There is a seperate repository for files that are used to create the game data, like blender, gimp or vector graphics files. It is not necessary to download these files to play the game, but if you are interested in contributing to the game you might want to get them.

-

+

To download the source data from the subversion repository:

svn checkout svn://osirion.org/osirion-data-src data-src
+

+ +
+ -

Radiant support files (optional)

-

+

+ +

Radiant support files (optional)

+

You can skip this section if you do not intent to create models with netradiant or gtkradiant 1.5. These files probably won't work with other versions. You can find precompiled netradiant packages here: -

+ -

Organization of the distribution

+
+ +

Organization of the distribution

 /doc 					Documentation
@@ -324,11 +376,13 @@
 	/gtkradiant			radiant support files
 
+
+ - + - - + + \ No newline at end of file diff --git a/doc/installation_release.html b/doc/installation_release.html index d8fa5cd..6abacf8 100644 --- a/doc/installation_release.html +++ b/doc/installation_release.html @@ -20,34 +20,41 @@ - Home . - Downloads . - Documentation . - Forum . - Wiki . - Tracker + News . + Documentation . + Screenshots . + Downloads . + Forum . + Wiki . + Tracker -
+
+ +
-

Installing the latest release

-

+

Installing the latest release

+

Before you can run the game, you must have working OpenGL libraries. These are usually installed by the driver package for your videocard.

-

+

You can find the latest release in the downloads section of the website:
http://osirion.org/index.php?page=downloads

+
+ -

Windows

-

+

+ +

Windows

+

Download for 32-bit windows
osirion-latest-win32.zip (32-bit)
This package should work on most windows systems. @@ -55,70 +62,78 @@ Download for 64-bit windows
osirion-latest-win64.zip (64-bit)

-

+

Dowload the game data package:
osirion-latest-data.zip

-

+

Unzip the executables package to an approriate directory. Unzip the game data package in the new directory. For example, if the game was unzipped to D:\Osirion then there should be a directory D:\Osirion\data\base containing the game data.

-

+

Open the game directory in explorer and click on osirion.exe to start the client.

+
+ -

Linux

-

+

+ +

Linux

+

Requirements:
To run the client, tour system will need to have the following packages installed: libSDL, libjpeg, libpng and libz. To run the dedicated server you need libz and ncurses. These are common packages and most systems will already have them installed. You do not need to have the bullet libraries installed.

-

+

Linux download:
osirion-latest-linux.tar.bz2 (32- and 64-bit)
This package contains the linux version of the client and the server.

-

+

Extract the package, a new subdirectory will be created. The actual directory name will depend on the version number. Enter the new subdirectory.

-
+
 tar jxvf osirion-latest-linux.tar.bz2
 cd osirion-linux-875
 
-

+

Dowload the game data package:
osirion-latest-data.zip

-

+

Unzip it:

-
+
 unzip ../osirion-latest-data.zip
 
-

+

To run the 32 bit client:

-
+
 ./osirion.x86
 
-

+

To run the 64 bit client:

-
+
 ./osirion.x86_64
 
- +

- + + +
- + diff --git a/doc/installation_source.html b/doc/installation_source.html index 3dd4c8b..a6d91a9 100644 --- a/doc/installation_source.html +++ b/doc/installation_source.html @@ -20,73 +20,83 @@ - Home . - Downloads . - Documentation . - Forum . - Wiki . - Tracker + News . + Documentation . + Screenshots . + Downloads . + Forum . + Wiki . + Tracker -
+
-

Building from source code

+
-

+

Building from source code

+ +

To build Project::OSiRiON from source code you need a working C++ compiler and have the necessary libraries and header files installed. The official binaries are compiled with gcc on linux, and mingw on windows.

- + + +
-

Requirements

+
-

+

Requirements

+ +

The following packages are required to build the the dedicated server:

-
    -
  • zlib -
  • Bullet physics library -
  • ncurses or pdcurses (optional) + -

    +

    Additionally, the client requires:

    -
      -
    • libjpeg -
    • libpng -
    • libSDL 1.2 -
    • OpenGL -
    • OpenAL or OpenAL Soft -
    • Ogg Vorbis +
        +
      • libjpeg +
      • libpng +
      • libSDL 1.2 +
      • OpenGL +
      • OpenAL or OpenAL Soft +
      • Ogg Vorbis
      -

      +

      You will also need gcc, GNU make, automake and libtool.

      +
-

Building on Ubuntu Linux

+
-

+

Building on Ubuntu Linux

+ +

To build the game on Ubuntu, you can install the required tools and dependencies by running the following commands in a terminal window:

-
+
 sudo su -
 apt-get install autoconf automake libtool subversion
 apt-get install libjpeg8 libjpeg8-dev
@@ -97,62 +107,79 @@ apt-get install libopenal1 libopenal-dev
 apt-get install libsdl1.2debian libsdl1.2-dev
 
+

+ +
+ -

Building on Windows

+
-

+

Building on Windows

+ +

You can build the game on windows using a MinGW/MSYS environment. You can use the instructions in this document to create a complete environment, capable of building the Project::OSiRiON source code.

+

+ Note that the current win32 build environment uses /local32 instead of + /usr/local. Edit the building instructions accordingly. + +

-

Building the Bullet physics library

+
-

+

Building the Bullet physics library

+ +

The engine uses the Bullet Physics Library for physics support. You can download the bullet source code here: -

    -
  • http://code.google.com/p/bullet/downloads/list +

    -

    +

    To download and install the library:

    -
    -wget http://bullet.googlecode.com/files/bullet-2.79-rev2440.tgz
    -tar zxvf bullet-2.79-rev2440.tgz
    -cd bullet-2.79
    +
    +wget http://bullet.googlecode.com/files/bullet-2.81-rev2613.tgz
    +tar zxvf bullet-2.81-rev2613.tgz
    +cd bullet-2.81-rev2613
     ./autogen.sh
     ./configure --prefix=/usr/local --disable-demos
     make
     sudo make install
     cd ..
     
    -

    +

    If you do not want to install bullet in /usr/local, you can edit the --prefix option here. Edit the the --with-bullet option when configuring the Project::OSiRiON source code accordingly.

    -

    +

    It is recommended you use this specific version of the library, physics behaviour could be different in other versions.

    +
+ -

Obtaining the source code

+
-

+

Obtaining the source code

+ +

Download the source package from the website:

-
+ -

Configuring the source code

-

+

+ +

Configuring the source code

+ +

Enter the new directory and configure the source code:

-
+
 ./configure --with-bullet=/usr/local --enable-static-bullet
 
-

+

If you do not need the client and want to build the dedicated server only you can pass the --without-client option to configure:

-
+
 ./configure --with-bullet=/usr/local --enable-static-bullet --without-client
 
-

+

If configure finds ncurses or pdcurses, the dedicated server will use this library and a have a curses console. To disable curses detection, pass the --without-curses option to configure.

-
+
 ./configure --with-bullet=/usr/local --enable-static-bullet --without-client --without-curses
 
-

+

You can use the --help option to get a list of all available options:

-
+
 ./configure --help
 
+

+ +
+ -

Building the binaries

-

+

+ +

Building the binaries

+

Compile the source code:

-
+
 make
 
-

+

The binaries will be built in the src/ subdirectory of the main distribution.

-

+

Important: make install is not supported. Results are unpredictable.

+
+ -

Obtaining the game data

-

+

+ +

Obtaining the game data

+ +

Download the game data package from the website:

-
+ -

Running

-

+

+ +

Running

+ +

The client and the dedicated server will look for game data in the data subdirectory of the current working directory. Since the binaries are build in the src you will have start them with the src/ prefix.

-

+

To start the client:

-
+
 src/osirion
 
-

+

If the client opens a new window and immediatly close it again, it probably could not find the game data and exited. Check your installation.

-

+

To start the dedicated server:

-
+
 src/osiriond
 
-

+

If you are using windows, the binaries will be called osirion.exe and osiriond.exe.

-
- + + +
- + + \ No newline at end of file diff --git a/doc/osirion.css b/doc/osirion.css index e6ce165..f7a7868 100755 --- a/doc/osirion.css +++ b/doc/osirion.css @@ -1,6 +1,6 @@ /* main stylesheet for the Project::OSiRiON website - ingar@telenet.be + ingar@osirion.org */ /* @@ -38,78 +38,19 @@ a:hover text-decoration: underline; } -#content p { - padding-left: 8px; -} - -#content dl { - padding-left: 8px; -} -#content dt { - font-weight: bold; - color: white; -} - -#content dd { - padding-top: 4px; - padding-bottom: 4px; -} - -#content h1 { - color: #ffffff; - font-size: 14pt; - font-weight: bold; -} - -#content h2 { - color: #ffffff; - font-size: 12pt; - font-weight: bold; -} - -#content h3 { - color: #ffffff; - font-size: 12pt; - font-style: italic; -} - -#content table { - padding-left: 8px; -} - -#content td { - padding-right: 16px; - vertical-align: top; -} - -#content hr { - border: 0px; - height: 2px; - background-color: #808080; - color: #808080; -} - -/* from the wiki theme css */ -#content ul { - line-height: 1.5em; - list-style-type: square; - margin: .3em 0 0 1.5em; - padding: 0; - list-style-image: url(images/bullet.png); -} /* global div definitions */ div.floatright { - text-align: center; - vertical-align: middle; - margin-left: auto; - margin-right: 8px; - margin-top: 8px; - margin-bottom: auto; - float: right; + text-align: center; + vertical-align: middle; + margin-left: auto; + margin-right: 8px; + margin-top: 8px; + margin-bottom: auto; + float: right; } div.newsitem { @@ -130,7 +71,7 @@ div.newstext { table.screenshot { text-align: center; - font-family: "Courier New", "Courier", "fixed", "monospace"; +/* font-family: "Courier New", "Courier", "fixed", "monospace";*/ margin-left:auto; margin-right:auto; } @@ -146,6 +87,24 @@ img.screenshot { clear: both; } + +.fullwidth +{ + width: 100%; + vertical-align: top; +} + +.halfwidth +{ + width: 50%; + vertical-align: top; +} + +.quarterwidth +{ + width: 25%; + vertical-align: top; +} /* page structure */ @@ -159,10 +118,31 @@ div#page { width: 84%; padding-left: 0px; padding-right: 0px; - border: 2px solid #505050; } +div#pagecontent +{ + text-align: left; + vertical-align: top; + margin-top: 16px; + margin-bottom: 16px; + margin-left: 16px; + margin-right: 16px; +} + +div#pagefooter +{ + text-align: left; + font-size: 8pt; + padding-top: 0px; + padding-left: 16px; + height: 48px; + border-top: 1px solid #808080; + background-color: #202020; +} + + /* menu */ @@ -209,74 +189,116 @@ img.osirionmenu { } +div.osirionlogo +{ + text-align: center; + vertical-align: center; + margin-bottom: 16px; + margin-left: 16px; + margin-right: 8px; + padding-top: 16px; + padding-bottom: 16px; + padding-left: 16px; + padding-right: 16px; + border: 1px solid #808080; +} /* content */ -div#content { +div.content { text-align: left; - margin-bottom: 32px; + margin-bottom: 8px; + margin-left: 16px; + margin-right: 8px; padding-left: 16px; padding-right: 16px; + background-color: #202020;; + border: 1px solid #808080; } -.fullwidth { - width: 100%; - vertical-align: top; +p.content { + padding-left: 8px; } -.halfwidth { - width: 50%; - vertical-align: top; +dl.content { + padding-left: 8px; } -.quarterwidth { - width: 25%; - vertical-align: top; +dt.content { + font-weight: bold; + color: white; } +dd.content { + padding-top: 4px; + padding-bottom: 4px; +} -/* - misc style elements -*/ +h1.content { + color: #ffffff; + font-size: 14pt; + font-weight: bold; +} -.superscript { - color: #ff0000; - vertical-align: top; - font-size: 8pt; +h2.content { + color: #ffffff; + font-size: 12pt; + font-weight: bold; } -.fixed { - font-family: "Courier New", "Courier", "fixed"; +h3.content { + color: #ffffff; font-size: 12pt; + font-style: italic; } -#content pre, div.fixed { - border-top: 1px solid #808080; - border-bottom: 1px solid #808080; - border-left: 1px solid #808080; - border-right: 1px solid #808080; - background-color: #202020; - margin-left: 48px; - margin-right: 48px; - margin-top: 8px; +table.content +{ + padding-left: 8px; +} + +td.content +{ + padding-right: 16px; + vertical-align: top; +} + +/* from the wiki theme css */ +ul.content +{ +/* line-height: 1.5em; */ + list-style-type: square; + padding-left: 24px; margin-bottom: 8px; - padding: 8px; - font-family: "Courier New", "Courier", "fixed"; - font-size: 12pt; - vertical-align: text-top; + list-style-image: url(images/bullet.png); } /* - footer + misc style elements */ -div#footer { - text-align: left; - font-size: 8pt; - padding-top: 0px; - padding-left: 16px; - height: 48px; - border-top: 1px solid #808080; - background-color: #202020; +.superscript { + color: #ff0000; + vertical-align: top; + font-size: 8pt; +} + +.fixed { + font-family: "Courier New", "Courier", "fixed"; + font-size: 12pt; +} + +pre.content, div.fixed { + border: 1px solid #808080; + color: #ffffff; + background-color: #666666; + margin-left: 48px; + margin-right: 48px; + margin-top: 8px; + margin-bottom: 8px; + padding: 8px; + font-family: "Courier New", "Courier", "fixed"; + font-size: 12pt; + vertical-align: text-top; } diff --git a/doc/starsystem_roadmap.html b/doc/starsystem_roadmap.html index a630e04..ee8cbf9 100644 --- a/doc/starsystem_roadmap.html +++ b/doc/starsystem_roadmap.html @@ -20,21 +20,24 @@ - Home . - Downloads . - Documentation . - Forum . - Wiki . - Tracker + News . + Documentation . + Screenshots . + Downloads . + Forum . + Wiki . + Tracker -
+
-

Starsystem roadmap

+
+ +

Starsystem roadmap

@@ -44,41 +47,52 @@
-

Places and Factions

+

+ +
+ + + +
+ +

Places and Factions

-
-

House Lindblade

+

House Lindblade

+ +

+An old and honorable Great House. +

-
+
Lindblade system
-
    -
  • planet Lindblade +
      +
    • planet Lindblade
Albion system
-
    -
  • planet Albion +
      +
    • planet Albion
Burton system
-
    -
  • planet Burton -
  • Trent outpost -
  • Lindblade shipyards +
      +
    • planet Burton +
    • Trent outpost +
    • Lindblade shipyards
Caledonia system
-
    -
  • planet Caledonia +
      +
    • planet Caledonia
@@ -89,17 +103,16 @@ -
-

House Praetoria

+

House Praetoria

-

+

Protected by the Praetorian Guard.

-
+
Praetoria system
-
    -
  • planet Praetoria +
      +
    • planet Praetoria
Carthagio system
@@ -111,58 +124,57 @@ -
-

House Dagon

+

House Dagon

-
+
Dagon system
-
Ashir-Dan system
-
Zensunni system
+
Ashran system
+
Rasheen system
+
Xibalba system
-
-

Independent Colonies

-

+

Independent Colonies

+

An alliance of systems independent from the central planets, protected by the Colonial Militia.

-
+
Ghant system
-
    -
  • planet Ghant -
  • Alexandria outpost -
  • Battleship custodian +
      +
    • planet Ghant +
    • Alexandria outpost +
    • Battleship custodian -
    • planet Seymour -
    • Regula station +
    • planet Seymour +
    • Regula station
Brogha system
-
    -
  • planet Brogha -
  • Cantor observatory +
      +
    • planet Brogha +
    • Cantor observatory
Antwerp system
-
    -
  • planet Antwerp -
  • starbase Helianthos (guards the border) -
  • Buccaneer's Den pirate base +
      +
    • planet Antwerp +
    • starbase Helianthos (guards the border) +
    • Buccaneer's Den pirate base
Kronenbaden system
-
    -
  • planet Baden -
  • planet Krone +
      +
    • planet Baden +
    • planet Krone
    Khorsand system
    @@ -180,43 +192,46 @@ -
    -

    Neutral Systems

    +

    Neutral Systems

    -
    +
    Finnmark system
    Headquarters of the Joint Miners Association -
      -
    • planet Finnmark -
    • Kvalsund mining operations +
        +
      • planet Finnmark +
      • Kvalsund mining operations
    East End
    -
      -
    • Trident core +
        +
      • Trident core
      +
    +
    Yser system
    +
    +
    +
    Ground system
    +
    -
    -
    -

    Borderworlds

    +

    Borderworlds

    -

    +

    Worlds destroyed during the war, these systems are not claimed by any lawfull faction.

    -
    +
    Kor Telos
    -
      -
    • planet Corthio -
    • planet Andros -
    • battlefield remains +
        +
      • planet Corthio +
      • planet Andros +
      • battlefield remains
    @@ -230,19 +245,18 @@
    Anarian system
    -
      -
    • Anarian nebula -
    • Galileo research station -
    • battlefield remains -
    • Kadriant derelict
    • +
        +
      • Anarian nebula +
      • Galileo research station +
      • battlefield remains
    Karelian system
    -
      -
    • Karelian nebula -
    • border station +
        +
      • Karelian nebula +
      • border station
    @@ -250,39 +264,41 @@ -
    -

    Dragon Eye nebula

    +

    Dragon Eye nebula

    -

    +

    Nebulous area consisting of unclaimed buffer systems between the territories of the Great Houses, generally unsafe area.

    -
    Argos system
    -
    -
    +
    Gibraltar system
    -
    Vasco system
    +
    Argos system
    +
    +
    + +
    Colombus system
    -
      -
    • da Gama station -
    - + +
    Camorra system
    +
    +
    +
    + -
    -

    Southern Rim

    +

    Southern Rim

    -

    +

    Rogue space.

    -
    +
    Muralis system
    @@ -302,14 +318,13 @@ -
    -

    Tsu-Khan Empire

    +

    Tsu-Khan Empire

    -
    +
    Kiana system
    -
      -
    • Kiana Prime +
        +
      • Kiana Prime
    @@ -317,29 +332,32 @@
    Beta Kosiya
    - dissapeared and/or destroyed) +
      +
    • dissapeared and/or destroyed) +
    Gamma Kosiya
    - + -
    -

    Organizations and Corporations

    +

    Organizations and Corporations

    -
    +
    Micron Corporation
    AMTEL Tech Conglomerate
    Joint Miners Association
    +
+ -
+
- + diff --git a/doc/storyline.html b/doc/storyline.html index 743f596..cb467c1 100644 --- a/doc/storyline.html +++ b/doc/storyline.html @@ -20,32 +20,39 @@ - Home . - Downloads . - Documentation . - Forum . - Wiki . - Tracker + News . + Documentation . + Screenshots . + Downloads . + Forum . + Wiki . + Tracker -
+
-

Storyline

+
-

+

Storyline

+ +

The historic files are provided as a point of reference for the game universe and background information for the single player storyline. A real story-driven single player campaign is a long term objective of the project, and in the meanwhile it serves as an aide to place the player in the game universe.

+
+ -

Timeline

+
+ +

Timeline

@@ -63,10 +70,10 @@
-

+

Note to the reader:

-

+

Before the Great War, the systems controlled by the Great Houses were referred to as The Colonies, the term Borderworlds was used to refer to independent systems. @@ -77,30 +84,32 @@ are usually referred to as the Central Planets.

+
-
-

+
+ +

HISTORY OF THE YEAR OF WAR
- from the House Lindblade historical records + from House Lindblade historical records

-

Reaching for the Stars

-

+

Reaching for the Stars

+

History of mankind is a tale mostly written in blood and fire. Although there are few written accounts of the events before the Exodus, it wouldn't be hard to imagine why the Homeworld would have been abandoned in the first place: wars for power, territory and resources would be commonplace for almost five centuries to come.

-

The Year of War

-

+

The Year of War

+

For the Tsu-Khan, this war was no different. About a century ago, The Empire had depleted most of its natural resources and had launched an ambitious project to find a suitable new homeworld.

-

+

At the time, most of the human population was ignorant about the presence of alien lifeforms in their galaxy. The scant pieces of evidence that did exist were kept secret by the political leaders. The Colonies were controlled @@ -108,7 +117,7 @@ None of the House Lords had the motivation to order a thorough investigation into a mad man's testimony of outer world creatures.

-

+

The war came without warning. Near Kor Telos, on the edge of known space and outside the jurisidiction of the great houses, two new colonies had been founded. The settlers were finishing the construction of their @@ -116,7 +125,7 @@ Unfortunatly, the Tsu-Khan Empire had located a suitable planet just a few parsec away.

-

+

The Andros colony was the first to fall. It didn't take the Tsu-Khan battle group very long to destroy the defenceless setlement. By the time they arrived at the Corthio colony, the colony had scrambled @@ -124,7 +133,7 @@ no match for the superior Tsu-Khan ships. In a few hours, the battle was over, and the Corthio colony had been reduced to ashes.

-

+

The story repeated itself across the Borderworlds. These independent worlds were usually inhabited by pacifist who had escaped the turmoil of the central planets or had a mutual understanding with one or more of the great houses. The Tsu-khan @@ -132,14 +141,14 @@ remained was a few primitive settlements scattered across the smoldering remains of the Borderworld planets.

-

+

The relations between the Borderworlds and the Major Houses were strained with conflicts of interest. The central planets usually didn't care unless some economical or strategical advantage was involved. Slowly the Houses got drawn into the the war, and after almost a year of hostilities most of the House Lords found their armies involved in a full-scale war. A war, they realised, they couldn't win.

-

+

With the Borderworlds out of the way, and the Tsu-Khan fleet at the border of every Major House, there wasn't much they could do to oppose the Empire. In this darkest of hours a secret meeting took place that turned the fate of history. On a small, @@ -147,16 +156,16 @@ each ship carrying one of the remaining House Lords.

-

The Alliance

+

The Alliance

-

+

This small planet used to be the stage for the House Council, by then a long forgotten tradition, where the Lords of the Major Houses used to work out their differences with dialog, or discuss current events. In the years before the Great War, this tradition had been neglected and oposing views were usually solved with a friendly border skirmish followed by a royal monetary compensation.

-

+

These times were over. This war wasn't about money, power or territory. It was about survival and it was clear by now that none of the Major Houses possessed sufficient strength to fight the Empire on its own. A new alliance was formed and it @@ -166,7 +175,7 @@ as moderate amongst the House Lords, proposed to assemble a fleet in the Lindblade system to prevent the Empire from gaining a foothold in the Central Systems.

-

+

Within days, the largest fleet in human history had united under one banner. Out of fear, out of hope, but most of all, out of desperation. A news reporter from the era described it as ".. an overwhelming sight of the End of Times, but unlike the descriptions of @@ -175,14 +184,14 @@ a formidable enemy. Battleship after battleship graciously drifted in formation, and everyone on board, from crewman to captain, knew this had to be the final stand.

-

+

When the Empire's vast intelligence informed the Tsu-Khan Emperor of this unexpected turn of events, humanity's fate seemed sealed. The orders where quick and decisive: regroup the fleet and prepare to engage the humans. Once dispatched it would take care of the alliance fleet and end human opposition once and for all. The war would be over soon and the Alliance's systems would under the Empire's control.

-

+

It is said that even the smallest person can change the course of the future, and in this case, it was a lonely scientist in the Anara system. His work involved the meaning of life, the universe and related subjects, and ignoring the dangers @@ -190,7 +199,7 @@ him to pilot a tiny and almost unpowered vessel into the Anarian nebula, where he could conduct measurements of the small variations in the local hyperspace field.

-

+

He was performing another scan of the sector when suddenly his instruments went off the scale. To his amazement he suddenly found himself on the edge of the area where the alien fleet had decided to regroup and refuel before they sneaked into Alliance Territory. @@ -198,7 +207,7 @@ support pod, used the high levels of radiation in the nebula to elude the Tsu-Khan sensors and send a warning message the Alliance Fleet.

-

+

With the help of the detailed scientific information about the nebula, the Alliance managed to jump right on top of the unsuspecting Tsu-Khan fleet. Within minutes, the Imperial Flagship, primary target of the assault, had taken massive damage and was @@ -207,90 +216,124 @@ and the massive rain of high-speed metallic debris behind it. Some managed to retreat to Tsu-Khan space, most fell victim to the united firepower of the Alliance fleet.

-

+

News of the victory spread through the Colonies like fire, and the battle became legendary before the Alliance fleet had even returned home.

+
+ -
-

+
+ +

PROJECT::OSIRION
- Allied Intelligence Network classified documents + from Allied Intelligence Network classified documents

-

Project Osirion

- -

- During the war, many great houses conducted experiments in search for - advanced technologies to aid in defeating the enemy. One of these - experiments was called 'Project Osirion', an experiment involving - a new type of hyperjumpdrive, which could work independent of hyperspace - jumps holes and cross enormous distances in the blink of an eye. -

-

- The requirements on ship design for this experimental drive unit were - outrageous to say the least. But facing imminent defeat, no effort - was spared to gain even the slightest advantage. In less than 6 months - a new ship was constructed and equiped with the experimental drive unit. - - The ship was an impressive sight: several hundred meters of neutronium-enforced - carbosteel, thousands of metric tonnes of superconductors and optronics, - a monument to human ingenuity and an instrument to survival. -

+

The Derelict

+ +

+ A few years prior to the war, a Praetorian deep-space scout had discovered + a remarkable derelict: a massive ship, abandoned for ages, battered by millenia + of meteorite showers and high-energy radiation. Its technology was beyond anything + mankind had ever devised and unfortunatly, far beyond the understanding of even + the brightest of scientist, +

+

+ The ship's propulsion system was of particular interest: while it seemed to operate + on the same basic principles as a standard hyperspace jump drive, the design had + a number of enhancements that challenged the boundries of theoretical physics. + Some advanced models predicted this engine would be capable of almost instantanious + travel across vast distances, without evem the need for hyperspace jump holes. +

+

+ This kind of technology would give anyone a decisive military + advantage over his rivals and Praetorian scientists vigorously attempted to + duplicate the technology. Initially results where promising, + but after a large-scale accident the research was considered + too dangerous and abandoned.

+ +

Project Osirion

+ +

+ The war changed many things, including experiments in search for + advanced technologies to aid in defeating the enemy. In the spirit + of the new found alliance, the experimental jump drive was transfered from its + Praetorian storage to the Lindblade shipyards in the Burton system. +

+

+ While the jumpdrive was stabilized, a ship would be constructed + to carry this miracle technology.The requirements were outrageous to say the least. + But facing imminent defeat, no effort was spared to gain even + the slightest advantage. In less than 6 months a new ship was constructed + and equiped with the experimental drive unit.The ship was an impressive sight: + thousands of meters of neutronium-enforced carbosteel, tens of thousands + of metric tonnes of superconductors and optronics, a monument to human + ingenuity and an instrument to survival. +

+

This ship was christened 'Osirion'.

-

+

The ship's first test flight was a major event. Most secret projects did not generate a lot of attentention, but this flight was a higly anticipated by the top brass from all parties involved: military, political and corporate alike.

-

+

The ship had left the construction yard as planned and had almost arrived at departure point on the edge of the star system when suddenly all communication was lost. Extensive investigations after the incident have never revealed the source of the malfunction, and everything that happened after this point is the result of long-range sensor telemetry.

-

+

Sensors hat detected the ship arriving at the departure point and the flight continued as planned. A few moments later a massive energy discharge was registered, indicating the experimental jump drive was activated. Unfortunatly, the order to return to the point of departure after the initial jump, seems to be a part of the plan that never got executed. The ship had literally vanished into thin air.

-

+

The top brass was very upset.

-

The Karelian Incident

-

The Tsu-Khan Empire

+

The Karelian Incident

-

- PROJECT::OSIRION
+

What really happened to the Osirion

+ +
+ + + +
+ +

+ The Tsu-Khan Empire
Protectorate Top-Secret documents

-

What really happened to the Osirion

+

What really happed after the death of the Tsu-Khan Emperor

-

What really happed after the death of the Tsu-Khan Emperor

+

The Empress and the War Generals

-

Tsu-Khan Empress and the War Generals

+

The Empress' niece

-

The Empress' niece

+
-
-

+
+ +

Single Player Campaign Storyline

-

I. Business

+

I. Business

-

+

Alexandria outpost, jewel of the south, or queen of the wasteland, as some higher placed officials like to call it off-the-record. They were probably right too. The wasteland probably referred to @@ -300,7 +343,7 @@ people you could find here were people doing business and people who needed to dissapear from public appearance. Or both.

-

+

The local custom was to mind your own business, and that was exactly what I was looking for: minding my own business. My life on the central planets had become far more complicated than I had planned for and it @@ -308,7 +351,7 @@ planetary bank and spend it on the aquisition of a small transport vessel.

-

+

The first day of my new life as a spaceship captain. Not the glorious life I had gotten used to, but at least a decent one with its small pleasures once in a while. The small room I rented above the local bar almost felt like @@ -318,14 +361,14 @@ out, I'm great at doing the dishes and I always enjoyed our conversations. That is, until last week, when I ran into Mister Brent.

-

+

Ages ago, we used to work in the same building and he must have recognized me. I was sitting at the bar when he suddenly tapped on my shoulder. My memories of him were vague, but as he sat down, I ordered him a drink. We had some chit-chat, shared a few memories of distant times, but it didn't take hime very long to come to the point.

-

+

Mister Brent was the business type. "The rising star of the Regula mining operations, overseeing all shipments of niobium in the Ghant system", to quote his words. His phrases like "A smart man could make a fortune" sounded rather hollow to me, @@ -333,7 +376,7 @@ Another 1500 more to get myself a ship big enough to hold a small cabin with all the luxuries a simple life would need.

-

+

Repetetive? Boring? Perfect! Add an autopilot and this life could be more relaxing then a luxury vacation on an exotic planet. With this simple business but rock-solid plan laid out in front of me I managed to convince the manager of the local planetary @@ -343,16 +386,16 @@ just big enough to hold a few metric tons of whatever the owner had in mind. All it missed was a pair of blasters to shoot the mosquitos from the windshield.

-

+

That would have added another 50 runs to the price.

-

+

The first two runs went smooth. Nothing unexpected. Pick up supplies at Alexandria, fly all the way to the Regula mining operation station, exchange the supplies for a shipment of karpax ore and head back. I had just hit the impulse drive with the third load in my cargo hold when I noticed something out of place.

-

+

A blip. And a big one too. No civilian vessel had an EM radar signature that powerful. I peered through the windows and as planet Ghant grew bigger on me I could clearly distinguish a second bright spot next to the familiar one Alexandria had become to me. @@ -360,7 +403,7 @@ to come up with an answer. Battleship Custodian. Colonial Militia registration number CM-2542. It must have jumped in when I was docked at Regula.

-

+

Curious. While the Ghant system was officialy under the jurisdiction of the colonies, nobody had any real business here. Niobium was without doubt a valuable commodity, but since there was no real shortage of the oremy guess was that the @@ -368,7 +411,7 @@ I wasn't about to meddle into military affairs and let unfortunate circumstances ruin my life again.

-

+

Nevertheless it was hard to ignore the massive battleship looming over the outpost, but I docked and went straight to the bar. The bartender looked at me as I walked in and pointed me to my regular place at the bar. "I'll be right back", he said, @@ -379,15 +422,15 @@ you got it, but I am sure it is the real deal. No one would get it into his mind to synthesize anything without having an actual market for it."

-

+

As usual, my bartender was right, and that was exactly why I liked this stuff, even if it costed a small fortune. "But then again", he continued and turned has eyes towards the large space window at the other end of the bar, "life can be full of surprises."

-

II. Surprises

+

II. Surprises

-

+

It was hard for him to hide his unsettledness. "I just had a talk with the station supervisor and the commander of that battleship floating out there". "The Custodian", I replied. "I had the ship computer run an ID on it". "You'd better take care of that fancy new ship of yours", @@ -396,7 +439,7 @@ command of the battleship Custodian. They also dropped some kind of communication sattelite in the center of the system. God knows what these guys are up to."

-

+

The military is always involved in business the common man would rather not know about, but I had to admit, it just didn't sound right. A battleship in the Ghant system was curious, but a more permanent presence didn't make any sense at all. I picked up the small metal spoon lying @@ -405,18 +448,18 @@ know these kind of people, if it goes kabooom, they immediately like it." "Besides", I continued, "the system has been quiet for months. I haven't seen a pirate in ages".

-

+

The tone in my voice couldn't hide my longing for more dangerous and exiting times, but those days were over. I had chosen a new path, and I was not about to ruin my plans because of a few curious events. I emptied my cup and wished the bartender good night.

-

+

I couldn't sleep that evening. I didn't know what troubled me more: the prospect of my new life, the memories of the old one, or the strange events of today. When a man is troubled, he has to start walking and with the silence of the night as a blanket, I got out of bed and went out on a stroll.

-

+

2 am standard colonial time. Nights in space are something to get used to: without the sun to rise and set, dusk and dawn become rather hollow definitions and only the clock dictates when it is time to go to sleep. Nevertheless, the atmosphere @@ -424,7 +467,7 @@ the sound of busy peoples voices was replaced by the quiet hum of the electrical installations.

-

+

I wandered aimless through the empty corridors until I reached one of the large space windows on the upper level. It was almost like the vast, empty space behind it was reaching out, trying to stir something in the back of my mind. @@ -433,20 +476,20 @@ tremor going through the station. It was hardly noticable and most people would probably ignore it, but I knew exactly what it was.

-

+

When a ship drops from hyperspace into normal space, it will send a small shockwave into the surrounding area. This is not a shockwave of something traveling through space, but rather a disturbance of the fabric of space itself, with a distinct rythmn an experienced pilot can easily recognize. I could have ignored it too and go back to sleep, but the intoxicating effect of the mystery dragged me back to the window.

-

+

A ship had arrived, and it had to be close. Hyperspace-tremors do not travel very far and it would take one hell of a pilot to make a jump this close to a gravitational well. The slightest miscalulation would have spread out his atoms over the face of planet Ghant. The bright moving spot between the stars had proven he was either very good, or very lucky.

-

+

The design of the ship was unfamiliar. It looked like some kind of a patrol craft, armed to the teeth and ready to defend itself if it were necessary. Fortunatly, it looked like the pilot had a more quiet evening in mind. In a gracious arc, @@ -454,13 +497,13 @@ to the docking bay. A pleasant sight for anyone who could appreciate the finer arts of space flight.

-

+

By now it was almost 3 am and I was almost certain I was going to regret this nightwandering episode when my alarm clock would obnoxiously announce the next morning. Almost, because by now I had also learned that having no regrets and a strong focus on the task at hand was usually the wiser course of action. Right now, the task was finding some sleep.

-

+

I turned around, walked to the elevator at the end of the corridor and pressed the button. After a few seconds the doors opened with a joyfull chime and I stepped inside. "Level 3". The elevator seemed to consider my request when the doors finaly closed and it started @@ -468,31 +511,32 @@ the yawn escaping my mouth while the elevator control panel continued to count down the current level in large friendly letters. "5"... "4"... almost there... "3"... "2"...

-

+

It took a moment for reality to trickle through the veil of sleepyness, but it was quite obvious the elevator had passed my level and continued its journey downwards. There was only one thing down there: the docking bay, and I couldn't shed the awkward feeling it was a place I'd rather avoid at this particular moment. I pressed the emergency stop button on the control panel, to no avail.

-

+

"1"... "0" ..."-1, Docking Bay". The low, humming noise of the elevator ended abruptly and the doors opened again.

-

III. The Docking Bay

-

+

III. The Docking Bay

+

The warm, arid air of the docking bay filled the elevator. Contemporary generator technology tends to ionize the atmosphere and the distinct smell of a recently landed ship was noticably present. Outside the elevator, the corridor leading towards the landing zone stretched out, the docking bay hidden behind the left turn at the end.

- +
+ -

+
- - - + -- cgit v1.2.3