OpenRCT2 needs RollerCoaster Tycoon 2 to run, and it ships neither the game nor the data

OpenRCT2 ships no game data: it reads the original RCT2 files

OpenRCT2 is an engine, not a game package. It needs RollerCoaster Tycoon 2's original data files, and the README tells you to buy them from Steam or GOG.com before anything else works. Nothing in the repository substitutes for that purchase, and the layout explains why: the top-level entries are source, build files and asset metadata, including assets.json, with no archive of the original game anywhere.

The same limit reaches into the Linux packages. A Flatpak listed on Flathub under the identifier io.openrct2.OpenRCT2, an Arch package, a Gentoo portage entry, none of them can carry data the project has no right to redistribute. You install the client, then point it at a directory you own.

One exception is worth knowing. If you have the original RollerCoaster Tycoon and its expansion packs, the project has a wiki page for pointing OpenRCT2 at those files in order to play the original scenarios. The copy you need may therefore be the first game's rather than the second's, and the README links that page instead of shipping the scenarios.

master holds tagged releases, develop holds everything else

Cloning the repository hands you the wrong tree for playing. OpenRCT2 follows the gitflow workflow, and the README is explicit about the split: master only contains tagged releases and you should never branch off it, while features and fixes go to develop through pull requests. The repository's default branch is develop.

That makes every clone a development snapshot. The tags sit on the other branch: v0.5.7, named Get on with it!, published on 2026-11-01; v0.5.6, named We want... a shrubbery!, published on 2026-10-10; and v0.5.5, named Conquistador Coffee, on 2026-09-06. The last push to the repository was on 2026-11-02.

Read the version numbering with that in mind. The project is still on 0.x while shipping releases roughly every month, which is the numbering you expect from software whose behaviour and save handling can still change between tags. A bug filed from a develop build may already be fixed by the next release, and a bug filed from a release build will be read by people running a different code path than yours.

On Linux, latest means release, git and nightly

The README offers several Linux channels, and they track different things. The Flatpak is the recommended route for most distributions, with the reason stated plainly: you always receive the latest updates regardless of which distribution you use. Arch Linux carries openrct2 in its extra repository, described as the latest release, and openrct2-git in the AUR. NixOS and openSUSE through OBS each have a named package, FreeBSD has games/openrct2, and the Ubuntu PPA is a nightly build of the develop branch.

Choose the same word and get different software. On Arch, extra tracks a release while the AUR tracks git. On Ubuntu the PPA tracks develop nightly, which sits ahead of every tag.

None of these comes with an installation command in the README. It names the packages, links them, and points at a Flathub listing for the Flatpak, so the actual pacman, dnf or apt invocation is left to the distribution's own documentation. That matters when something breaks: which of three channels you installed is the first useful sentence in a bug report, and the issue tracker is where the project says to file bugs.

The launcher updates itself, which takes version pinning away from you

The project website offers portable builds and installers carrying the latest versions of the master and develop branches, plus a launcher for Windows, macOS and Linux that automatically updates your build so that you always have the latest version. That last sentence deserves reading before you install.

An auto-updating launcher removes the ability to stay on a version. If you keep a park you want to reopen later, work through a scenario with a fixed objective, or test anything at all, the launcher replaces the build underneath you at whatever moment the next tag or develop build lands. The README does not say which branch the launcher follows, so the download page alone will not tell you whether you are on a release or on a development tree.

The portable builds and the distribution packages are the way out, because both let you decide when to move. If you take the launcher anyway, take it knowing that staying on a known build is no longer a decision you hold.

Five build paths in the wiki, not one command in the README

Building the game means picking a platform and leaving the README. Building on Linux, on macOS using CMake, on Windows, on the Windows Subsystem for Linux and on MSYS2 MinGW are five links into the project's wiki, and the README carries no configure or build command of its own.

The root directory shows how much surface that covers. There are two CMake entry points, CMakeLists.txt and CMakeLists_mingw.txt, a CMakeSettings.json for Visual Studio, a full Visual Studio solution with its project and targets files, an openrct2.deps.targets for dependency management, an openrct2.common.props shared across projects, an emscripten directory, and debian and distribution directories for packaging.

For a contributor the consequence is concrete: five toolchains to keep building. If you are deciding whether you can carry a local patch, the honest answer from this README is that you will be reading wiki pages for the platform you actually have, and the first build is not reproducible from the README alone.

attempts to provide everything from RCT2, then lists what it changes

The README's phrasing about parity is careful, and so should yours be. OpenRCT2 attempts to provide everything from RCT2 as well as many improvements and additional features, then names them: support for modern platforms, an improved interface, improved guest and staff AI, more editing tools, increased limits and cooperative multiplayer. Attempts to provide is not provides.

The additions change play rather than presentation. Raised limits mean a park can express designs the original could not hold, so a strategy written against the old ceiling no longer applies. Improved guest and staff AI changes what the simulation does without you touching anything. Cooperative multiplayer changes who else can edit the same park.

The comparison worth making is with the game itself. RCT2 was written by Chris Sawyer in x86 assembly as the sequel to RollerCoaster Tycoon, and OpenRCT2 is a C++ re-implementation of it under GPL-3.0 that also reintroduces mechanics from the first game: the mountain tool in-game, the have fun objective, launched coasters that do not pass through the station, and several toolbar buttons. The README also notes that the RCT2 engine was based on Transport Tycoon, which has its own open-source project in OpenTTD. No feature comparison between the three is offered, so the decision rests on which subject you want to simulate.

Sandbox turns finance and the objective off together

Sandbox mode is not a relaxed scenario, it is a different objective. The README splits the two explicitly: a scenario requires completing a certain objective in a set time limit, while sandbox allows a more flexible park with optionally no restrictions or finance.

Switching finance off removes the profit loop the rest of the game is built around, since the stated goal of making a profit while maintaining park reputation and keeping guests happy no longer has anything to weigh against. Switching restrictions off removes the time limit and the target. What remains is a construction tool. That is useful for testing a layout before committing to it, and misleading if you are trying to learn the management game and reach for sandbox first.

For a newcomer the order follows from that. Run a scenario with an objective and a time limit, where the failure conditions teach you what the simulation rewards, and keep sandbox for afterwards.

Editorial conclusion

OpenRCT2 suits someone who already owns RollerCoaster Tycoon 2, wants a client that runs on current operating systems, and is willing to follow the develop branch between releases. It does not suit someone who wants a self-contained download, and it is the wrong tool if you need exact RCT2 behaviour, since the README says the project attempts to provide everything from RCT2 and then lists its own additions on top. Before adopting, install one of the named packages and check which branch it tracks, because a release channel on Arch, the git build in the AUR and a develop nightly in the Ubuntu PPA are three different answers to what version you are running.

Frequently asked questions

Official sources

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