OpenRCT2: what the re-implementation of RollerCoaster Tycoon 2 actually changes

The problem OpenRCT2 solves for people who still own RCT2

RollerCoaster Tycoon 2 was written by Chris Sawyer in x86 assembly, and that choice is why the game is awkward to run today: the binary is tied to an architecture and an era of Windows APIs. OpenRCT2 is a re-implementation of that engine in C++, not an emulator and not a patch. The README describes it as attempting to provide everything from RCT2 plus improvements, and it names the specific additions: support for modern platforms, an improved interface, improved guest and staff AI, more editing tools, increased limits, and cooperative multiplayer.

The audience is narrow and specific. You need the original game data to play, so this is not a project for someone looking for a free amusement park sim. It is for the person who bought RCT2 years ago, still has the disc or a Steam or GOG copy, and wants scenario play or sandbox play without fighting compatibility layers. The README points to Steam and GOG as places to buy the game, and notes that owners of the original RollerCoaster Tycoon and its expansion packs can point OpenRCT2 at those files to play the RCT1 scenarios, which is a real draw for people whose nostalgia sits with the first game rather than the second.

How the re-implementation is structured and what data flows through it

The repository is a C++ project built with CMake, with an MSBuild path alongside it: the top level holds CMakeLists.txt, CMakeLists_mingw.txt, CMakeSettings.json, openrct2.sln and openrct2.proj. The src/ tree holds the engine, data/ and resources/ hold game assets and metadata, and assets.json sits at the root as an asset manifest. There is a test/ directory, and the project ships .clang-format and .clang-tidy, which tells you the codebase is expected to be formatted and linted consistently by contributors.

The important architectural fact is the split between code and content. OpenRCT2 supplies the logic, the rendering and the interface, while the original RCT2 files supply the graphics, sounds and object data. That is why the README can offer portable builds and installers for the master and develop branches, and why those builds are useless on their own. The project also has an emscripten/ directory, which indicates the codebase is built for more than one target, and topics on the repository list SDL2 and OpenGL, which are the windowing and rendering layers the desktop builds sit on.

On top of the engine sits a plugin surface and a multiplayer mode. The topics list includes discord, multiplayer and server, and the README's chat section points plugin and asset work at dedicated Discord channels. The plugin system is the extension point for people who want to change behaviour without rebuilding the engine, and multiplayer is the feature that has no equivalent in the original game.

Installing OpenRCT2 and pointing it at your RollerCoaster Tycoon 2 files

The README does not document a source build as the normal path. It sends you to the download page for portable builds and installers of the master and develop branches, and to a separate launcher for Windows, macOS and Linux that updates your build automatically. On Linux it recommends the Flatpak release, and it lists native packages for Arch (openrct2 in extra, plus openrct2-git in the AUR), Gentoo (games-simulation/openrct2), NixOS, openSUSE and an Ubuntu nightly PPA, and games/openrct2 on FreeBSD.

After installing, the game still needs the original data. The README says OpenRCT2 requires original files of RollerCoaster Tycoon 2 to play, sold on Steam and GOG. The usual shape of that step is telling the game where those files live; the README does not print the exact prompt or config key, so follow the in-game path it offers rather than guessing a flag. If you own the first RollerCoaster Tycoon and its expansions, the README links a wiki page, Loading RCT1 scenarios and data, that covers pointing OpenRCT2 at those files.

For a source build, the README does not inline the steps. It links wiki pages for Linux, macOS with CMake, and Windows, and those pages are the authority on dependencies and configure flags. The repository is on GitHub at OpenRCT2/OpenRCT2 with develop as the default branch, so that is the branch a clone gives you by default, and the wiki pages are where the actual build commands live.

Multiplayer, plugins and the limits of the documentation

Cooperative multiplayer is the feature that most distinguishes OpenRCT2 from the game it re-implements, and the repository topics list a server component alongside it. What the README does not give you is a walkthrough: there is no section explaining how a host starts a session, what port is used, or how clients join. The FAQ below can only say what the repository supports, which is that the feature exists and that the community coordinates on Discord. If you are choosing OpenRCT2 specifically for multiplayer, plan to read the in-game UI and ask in the help channel rather than expecting a documented setup procedure in the repository.

The same gap applies to plugins. The README's chat table has a dedicated asset replacement channel and the topics mention mods and plugins, but the repository's own documentation does not describe the plugin API, the file layout a plugin needs, or the install path. This is a project where the codebase is the specification. That is workable for a C++ developer who is comfortable reading src/ and assets.json, and frustrating for someone who wants a documented extension contract.

One thing the README does make explicit is the contribution surface. It separates bug fixes, new features, translation, graphics, audio and scenarios, and it runs localisation and asset replacement through their own Discord channels. If your interest in OpenRCT2 is as a contributor rather than a player, that split tells you where your work would land.

Where OpenRCT2 is the wrong tool

The hard limitation is the one the README states plainly: original RollerCoaster Tycoon 2 files are required. There is no bundled free asset set, so a user who does not own the game cannot play OpenRCT2 at all. That also means OpenRCT2 is not a way to avoid paying for RCT2, and anyone framing it as such is describing something the project does not offer.

The second limitation is provenance. RCT2 is proprietary, and OpenRCT2 is an independent re-implementation distributed under GPL-3.0. The README's contents include a licence section, a code signing policy and a privacy policy, and the repository carries licence.txt, but the README does not walk through the legal reasoning behind re-implementing a commercial game. If your organisation has a policy about reverse engineering or about mixing GPL-3.0 code with proprietary assets, that question is not answered here and the README is silent on it.

The third is build cost. This is a substantial C++ program with CMake, MSBuild and MinGW build paths, clang-format and clang-tidy configuration, and platform-specific wiki instructions. Building it from source is a real task, not a five-minute clone. If you only want to play, take a pre-built release or the launcher; if you want to modify the engine, budget for the toolchain.

Finally, the release cadence cuts both ways. Releases arrive regularly (v0.5.3 on 2026-07-05, v0.5.4 on 2026-08-02, v0.5.5 on 2026-09-06), and the develop branch moves constantly. That is good for fixes and bad for anyone who needs a frozen, long-supported build. There is no long-term support branch described in the README.

OpenRCT2 against OpenTTD, and against running the original game

The most useful comparison is the one the README makes itself. RCT2's engine was based on Transport Tycoon, and the README points to OpenTTD as the equivalent open-source project for that game. The two share a philosophy: re-implement a proprietary engine, require the original data, and then extend well past what the original did. The difference is scope. OpenTTD has been around long enough that its tooling and documentation are broad; OpenRCT2's README is a download page plus links to wiki build guides, Discord channels and a contribution guide. If you have used OpenTTD and expect the same depth of written documentation, adjust the expectation.

The other alternative is not another project at all. It is running the original RCT2 through a compatibility layer or on period-appropriate hardware. That path gives you the exact original behaviour, including the limits OpenRCT2 raises, and it avoids the GPL-3.0 codebase entirely. What it costs you is everything in the OpenRCT2 feature list: modern platform support, the improved interface, the guest and staff AI changes, the extra editing tools, the higher limits, and multiplayer. The README also notes that OpenRCT2 re-introduces mechanics from the first RollerCoaster Tycoon that were absent from the sequel, including the mountain tool in-game, the have fun objective, launched coasters that do not pass through the station, and several toolbar buttons. If those specific mechanics are why you are here, the original RCT2 binary will not give them to you.

Licence, upgrade cost and what to check before you commit

OpenRCT2 is licensed GPL-3.0, and the repository carries licence.txt plus a licence section in the README. The practical consequence, stated as a fact about how the licence works rather than as legal advice: if you distribute a modified OpenRCT2, the GPL-3.0 obligations attach to that distribution. The game data you supply is a separate matter entirely, because it comes from a commercial product and is not covered by the project's licence. The README does not address that combination, and anyone planning to redistribute a bundled build should get proper advice rather than inferring an answer from the repository.

Upgrade cost is low for players and moderate for builders. The launcher exists specifically so that your build updates automatically, and the Flatpak route on Linux gives you the latest updates regardless of distribution, per the README. Source builders carry the cost themselves: the develop branch is where work lands, releases are cut roughly monthly, and there is no described backport policy, so a patch you need may only exist on develop. The repository does carry .git-blame-ignore-revs, which is a small but telling detail: the project expects large formatting commits and has tooling to keep blame readable through them.

Before you commit, check three things. Whether your RCT2 copy is one OpenRCT2 can read, since the README points at the Triple Thrill Pack on Steam and at GOG. Whether your platform is covered by an installer, the launcher, Flatpak or a native package. And whether the features you actually want, multiplayer and plugins in particular, have documentation adequate to your needs, because on both the README is thin and the Discord channels are the substitute.

Editorial conclusion

Adopt OpenRCT2 if you already own RollerCoaster Tycoon 2 or its expansions and want the game running on a current machine, with cooperative multiplayer, higher limits and the extra editing tools the project adds. Do not adopt it as a free replacement for RCT2: the README states the original files are required, so there is no path to playing it without a purchase, and it is the wrong tool if you want a game that installs and runs with no external data. Before committing, verify that your copy of the game is the Triple Thrill Pack or another version whose files OpenRCT2 can read, that your platform has a build (the README lists installers, a launcher, Flatpak, and native packages for Arch, Gentoo, NixOS, openSUSE, Ubuntu nightly and FreeBSD), and that the plugins you plan to use match the current release line. The last push to the develop branch was on 2026-09-21, so the codebase is moving quickly and pinned builds will age.

Frequently asked questions

Official sources

1. License: GPL-3.0
2. OpenRCT2/OpenRCT2 on GitHub
3. Project website
4. README
5. Releases