Skip to content
Snippets Groups Projects
To learn more about this project, read the wiki.
README.md 4.50 KiB

Trosnoth Source Repository

Quick Intro

Trosnoth is a multiplayer 2D platform sidescroller, where you control a single soldier. With your team, you must capture all the territory in the entire map before your enemy does.

See http://trosnoth.org/ for the game website.

The game is licensed under GPLv2.

To run the game from the repository, you can use run-trosnoth.py.

Repository Branch Structure

This repository has a number of active branches:

  • default - this is used for development on the next minor release of Trosnoth. This may include new features, but they must be network-compatible with the current latest Trosnoth release. You should always be able to play Trosnoth from default and connect to a Trosnoth server running the latest release, or run a Trosnoth server from default and have clients on the latest release connect.
  • unstable - this is used for development on the next major release. Changes might not be network-compatible with the current latest Trosnoth release. It is always safe to merge default into unstable, but unstable should only ever be merged into default as part of the release of a new major version.
  • camp-stable - Trosnoth is used on Ubertweak camps, with a number of minor changes to facilitate LAN-only play. Mainly this involves automatically logging on to the Trosnoth server using the machine's login details, and displaying the current username prominently on the title screen. The camp-stable branch should be the latest stable Trosnoth release plus these changes. It should be safe to run this version on camp even if you don't have a Trosnoth developer on camp to debug any issues.
  • camp - this is the version to use for Ubertweak if you have a Trosnoth developer on your leadership team. It may include changes that haven't been properly play-tested. Isn't that what camp is for? Changes made on camp should generally be made in the default or unstable branches and merged forwards into camp, or should be made directly on camp and later transplanted back to the appropriate branch. You should never merge from camp or camp-stable into default or unstable.

Directory Structure