Using OpenTS

Developer-build setup, local data, configuration, and save-game behavior.

Getting started

Project status, local builds, and required game data.

Command line optionsOptions accepted on the OpenTS command line.

Build and runBuilds the Debug or Release executable for either platform and runs it against a directory of game data.

Game dataA local developer build reads legitimately owned Tiberian Sun data from the repository's Run directory.

Project statusOpenTS provides playable releases and nightly developer builds; campaigns, skirmish, saving, and LAN play are functional.

Configuration

Player and mod configuration files and where they are documented.

Configuration filesOpenTS reads player options, hotkeys, rules, art, media registries, and scenario data from separate files.

Compatibility & migration

How builds, game data, and saved games behave across versions.

Compatibility and save gamesHow OpenTS lists and loads save games, and which save games a build accepts.

Troubleshooting

Supported checks for developer-build and local-data failures.

Crash reportsA crash writes a minidump, a readable report, and the end of that run's debug log into a folder of its own beside the executable.

Debug logs and consoleEvery run writes a timestamped log beside the executable, and the debug console can be opened to watch that output live.

Developer-build troubleshootingChecks the supported toolchain, target architecture, output location, and local game-data tree.

Out-of-sync reportsA network game that goes out of sync writes a checksum report beside the executable, so two players' reports can be compared to find where they diverged.