
Tiberian Sun, rebuilt: shared-house co-op campaigns — several players, one force.
A fork of OpenTS, the open rebuild of the Command & Conquer: Tiberian Sun engine, with selectable campaign mission variants and a player-by-force control matrix: several players can share a force, and one player can control several.
The Warpzone launcher can stage its network games without port forwarding by tunnelling the game's UDP traffic.
You need: original Tiberian Sun + Firestorm data; Windows (or Wine)
From the project's release notes. Games and the launcher show these after every update.
2026-10-19 · on GitHub
Upstream OpenTS fixes from 19 October 2026, and the menu colors again in lobby-started shared campaigns. This is a preview build of commit f9fd1de.
This build merges 39 upstream OpenTS commits. They fix crashes when the computer plans defenses without a choice and when aircraft unload outside a team, saving games with infantry types that have no animation sequence, and several gameplay rules: guarding units engage each new target, Cloakable=yes works on aircraft, low-power build rates and railgun firepower bonuses take effect, superweapons from switched-off structures arrive suspended, and shift-clicking an object only changes the selection. Upstream also changed SPAWN.INI so that Color names a position in the rules' [Colors] list, as CnCNet launchers write it.
A shared campaign started from the network lobby gives its players the eight menu colors again, in seat order. Seat order, the host's first seat and the session identity are unchanged.
Shared campaigns · Two-machine LAN playtest
VS2022 Win32/x64 Debug/Release builds and CTest passed on this commit, together with Manual CI. The shared campaign has not been played on two real machines before this release; the LAN playtest checklist is that test.
A hand-written SPAWN.INI that gives Color=0 to 7 still starts, but the players get the first eight [Colors] entries instead of the menu colors. 0.11.0 does not list or load saves written by 0.10.0. All players need this exact fork build and the same target platform. Original game assets are required and are not included.
The release workflow attaches separate Win32 and x64 engine packages.
Send bug reports and requests for this fork to <https://ntfy.sh/opents-coop-feedback-496c07> (web page, ntfy app, or curl -d "your message" https://ntfy.sh/opents-coop-feedback-496c07). The channel is public, so leave out personal data.
<!-- opents-release-notes start -->
<!-- opents-release-notes end -->
2026-10-16 · on GitHub
A two-machine LAN playtest checklist, and lobby names with spaces around them. This is a preview build of commit 7aa9720.
Two-machine LAN playtest walks two players through a shared campaign from the network lobby to the second mission: shared play, control groups, waypoints, saving, resuming after a restart and the next-mission transition. Each step says what both players should see and which files to keep when something else happens.
A shared campaign started from the network lobby now ignores spaces and tabs before and after a player's name. Such a name used to stop that player's game at launch and return it to the main menu. Two names that differ only in those spaces count as the same name, so the host cannot start until one player renames.
VS2022 Win32/x64 Debug/Release builds and CTest passed on this commit, together with Manual CI. The shared campaign has not been played on two real machines before this release; the checklist is that test.
0.10.0 does not list or load saves written by 0.9.0. All players need this exact fork build and the same target platform. Original game assets are required and are not included.
The release workflow attaches separate Win32 and x64 engine packages.
Send bug reports and requests for this fork to <https://ntfy.sh/opents-coop-feedback-496c07> (web page, ntfy app, or curl -d "your message" https://ntfy.sh/opents-coop-feedback-496c07). The channel is public, so leave out personal data.
<!-- opents-release-notes start -->
<!-- opents-release-notes end -->
2026-10-16 · on GitHub
Shared control groups in shared campaigns, and game data from the Warpzone launcher. This is a preview build of commit 734eb80.
All players of a shared-house campaign now share its control groups. When one player selects units and presses Ctrl and a number, that number appears on the units on every player's screen, and any player who controls those forces can select the group with the number key. Assigning a number takes it only from objects of the forces the assigning player controls. A shared save keeps the groups. Each player used to keep separate groups that a load cleared. As in a campaign played alone, a control group also sets the object's recruitment group, which mission triggers read.
When the Warpzone launcher passes the folder where it found Tiberian Sun, the game reads its data from there. A folder that does not exist is ignored.
VS2022 Win32/x64 Debug/Release builds and CTest passed on this commit, together with Manual CI. Shared control groups were not tried in a shared campaign on real machines before this release.
0.9.0 does not list or load saves written by 0.8.0. All players need this exact fork build and the same target platform. Original game assets are required and are not included.
The release workflow attaches separate Win32 and x64 engine packages.
Send bug reports and requests for this fork to <https://ntfy.sh/opents-coop-feedback-496c07> (web page, ntfy app, or curl -d "your message" https://ntfy.sh/opents-coop-feedback-496c07). The channel is public, so leave out personal data.
<!-- opents-release-notes start -->
<!-- opents-release-notes end -->
No open rooms right now. Host one from a game or the launcher.
Categories: Maps, Mission variants. Every mod version is reviewed by a moderator before it appears.
No mods published yet.