Skip to content
C Objective-C M4 Makefile Python C++ Shell
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
data Revert "Failed test" Jul 6, 2019
gfx Revert "Failed test" Jul 6, 2019
locale
mac Added a note about the XCode files not working anymore. Jun 30, 2019
misc Fixed failure to include misc directory in dists. Jul 21, 2019
music Imported a fix of configure.ac. Jul 7, 2019
sound
src Removed unnecessary part Jul 7, 2019
.gitignore
COPYING Added a copy of the GNU GPL. Feb 26, 2015
LICENSES
Makefile.am Fixed a problem with make install on locale folder. Jul 23, 2019
README.txt
configure.ac Fixed make install Jul 7, 2019
starfighter.sh Updated readme, added helper launcher script. 2.0 release. Jul 4, 2019
win32build.sh Updated readme, added helper launcher script. 2.0 release. Jul 4, 2019

README.txt

This file has been dedicated to the public domain, to the extent
possible under applicable law, via CC0. See
http://creativecommons.org/publicdomain/zero/1.0/ for more
information. This file is offered as-is, without any warranty.

========================================================================


Thank you for downloading Project: Starfighter!

Project: Starfighter is a space shoot 'em up game originally developed
by Parallel Realities in 2002, and released in 2003. You assume the role
of Chris Bainfield in his quest to put an end to WEAPCO, the weapons
corporation which has enslaved the galaxy.

If you played one of the versions of Project: Starfighter distributed by
Parallel Realities, you might notice some differences in this version
compared to the original:

* The graphics, sounds, and music are all completely different. This is
  because most of the original media was not properly licensed, and
  therefore needed to be replaced to make the game 100% libre. Most of
  this work was done by the previous project at SourceForge; the current
  project completed that work by adding music and replacing one
  non-libre graphic that got into version 1.2 by mistake.

* There are several gameplay changes. These changes were mostly done to
  balance the game better. However, if you want the original experience,
  "Classic" difficulty emulates it as closely as possible.

* Much of the dialog has been changed. There are various reasons for
  this; some of these include fixing bad writing, making the dialog
  match new music queues, and giving the characters more personality.

* In many places, the interface has been considerably improved. As an
  example, the simplistic target arrow of the original has been replaced
  with a system of several arrows, one for each ship.

* Unicode and gettext translation support have been added.

* Typing "humansdoitbetter" in the title screen no longer enables
  cheats. This is actually because the switch to SDL2 broke the original
  feature, and rather than fixing it, I just replaced it with something
  else. I'll let you figure out what the new method to access the cheat
  menu is. :)

------------------------------------------------------------------------

PLAYING THE GAME

The basic controls are the arrow keys, Ctrl, Space, Shift, and Escape.
Other keys on they keyboard can also be used in case of keyjamming or if
you simply prefer other controls; alternative keys include the keypad,
ZXC, ASD, <>?, and 123. A gamepad or joystick can also be used.

The basic objective of Project: Starfighter is simply to complete all
missions. Exactly what entails completing a mission varies and is
explained in-game.

In the system overview screen, various sections can be accessed by
clicking the icons on the bottom of the screen. You can also use the
keyboard or a gamepad if you prefer (use the arrows to move the cursor
and the fire button to "click" on things).

Other than that, have fun, and good luck!

------------------------------------------------------------------------

COMPILING FROM SOURCE

If you are an end-user, it is easiest to use an existing binary
distribution if possible.  If you want or need to compile yourself,
however, instructions follow.

Note: Developers compiling the source code from the Git repository,
please first see the GENERATING CONFIGURE SCRIPT section below.

Project: Starfighter depends on the following libraries to build:

* SDL2 <http://libsdl.org>
* SDL2_image <http://www.libsdl.org/projects/SDL_image/>
* SDL2_mixer <http://www.libsdl.org/projects/SDL_mixer/>
* SDL2_ttf <http://www.libsdl.org/projects/SDL_ttf/>
* Pango <https://www.pango.org/>

Once you have all dependencies installed,  do the following from the
Project: Starfighter base directory:

    ./configure
    make
    make install

This will perform a system-wide installation, which is recommended for
most users.  For most Linux systems, an icon should be added to your
menu which you can then use to run Starfighter; if not, you can use the
launcher found in the "misc" directory or run the "starfighter" command
manually.

If you would prefer a "run in place" build, you should instead do the
following from the Project: Starfighter base directory:

    export SF_RUN_IN_PLACE=1
    ./configure
    make
    mv src/starfighter .

Run "./configure --help" to see all options for compiling.

------------------------------------------------------------------------

GENERATING CONFIGURE SCRIPT

If you contribute to Project: Starfighter's source code, you will need
to know how to generate a configure script for compiling the program.
NOTE: This is for developers only. End-users simply compiling releases
of Starfighter from source can ignore this section.

The following components are required to generate the configure script:

* Autoconf
* Automake
* pkg-config

Once these dependencies are installed, simply do the following from a
terminal window:

    autoreconf -vif

The arguments are technically optional, but recommended.

If for some reason you need to remove all of these files from your
directory, you can do so via the following command (requires Git):

	git clean -fdx

Note: automatically generated files are listed in .gitignore, so you
generally don't actually have to do this.

You can’t perform that action at this time.