Copyright (c) 2003-2026 by Kronosaur Productions, LLC.
https://transcendence.kronosaur.com
This repo contains the source code for building the Transcendence.exe client, which is used to run any Transcendence adventure, including Stars of the Pilgrim from the Domina & Oracus saga.
Note that there are several other repositories that are relevant to this project but are not necessary for building it from scratch.
Art Assets: TransArt
Official community content and tools: Registered Developer Github Organization
You can choose to clone this repo with git and built from source, or download a prebuilt binary.
Prebuilt binaries can be obtained from Kronosaur Productions for free. These versions are able to access the Kronosaur Multiverse, and download expansions and mods from the Multiverse.
This is the latest stable version of the game.
These are alpha/beta/release candidate releases. If none is available, the download will simply provide the latest stable version of the game.
Transdata is a tool for performing various functionality such as decompiling .tdb files, running diagnostics, running stats/balance tools, and running tlisp scripts
Summarized changelogs are available in the appropriate version's announcement thread on the Kronosaur Productions forums.
You may build your own copies of the game from source. These versions will not have the code to access the Kronosaur Multiverse however, but you can still use one of the Kronosaur-provided binaries to access the multiverse.
You can setup a development environment in two ways:
- A full engine development environment with Visual Studios
- A game data only development environment using prebuilt binaries
See this article for more information:
Development Environment Setup & Build Instructions
Please see the contribution guidelines for information about best practices and style guides.
General Contribution Guidelines
Style & Contribution Guidelines:
- C++ Style Guide
- TLisp Style Guide
- XML Style Guide
- Markdown (Documentation) Style Guide
- In-game Text Style Guide
- Asset Style Guide
Please submit pull requests against the appropriate branch - if you have made an
API change, ensure that your pull request is against the appropriate API branch.
For example, if you add a new tlisp function or a new XML attribute field, this
would be considered a new API version, and you should use the appropriate
integration/API## branch as the merge target, where API## is the next highest
API number after the current API version in the alpha/beta branches.
If your Pull Request is not ready for merge, please mark it as a draft, this will reduce unnecessary confusion when reviewing pull requests.
It is recommended to split up multiple unrelated (or extremely large) changes into multiple PRs to make it easier to review. We have a limited amount of time each week to review PRs, so oversized PRs may take multiple weeks to review or outright rejected as too big to review.