OpenSC2K: a Godot remake of SimCity 2000 that reads your own copy of the game

What OpenSC2K replaces, and what it deliberately does not

SimCity 2000 shipped in 1993 and its Special Edition for Windows 95 in 1996, and the executable has not been maintained since. OpenSC2K is an independently written re-implementation of that simulation, not a patch or a wrapper. The README is explicit that compatibility and simulation behaviour were determined through observation, testing, analysis of game data, publicly available research, and reverse engineering of the original executable. No original source code or assets are included.

The project targets people who already own the 1996 release and want to keep playing it on a modern machine with a different feature set. The README frames the whole thing around that constraint: you provide your own copy of SimCity 2000 Special Edition, and the app imports its graphics, text, sound and music. This is the single most important thing to understand before downloading anything. OpenSC2K is not a free replacement for a game you do not have, and the MIT licence covers the project code only. The README states plainly that the MIT license does not grant rights to the original game or its assets, and that the project is not affiliated with or endorsed by Maxis or Electronic Arts.

So the audience is narrow by design. If you lost your disc, or you only ever played the DOS release, the import step is a wall rather than a speed bump.

How the import and the simulation fit together

The data flow starts at the import prompt. You point the app at SIMCITY.EXE, it checks the supported version, and then it pulls the game files in. Those files supply the original graphics, text, sound and music, which means the remake has no asset pipeline of its own for the base game. Everything visual and audible that is not original comes from optional external packs.

On top of that base, the project layers its extensions. City sizes run from 16, 32 and 64 tiles per side up to 256, 384 and 512, alongside the original 128. The data maps for coverage, land value, pollution and crime are rendered at 1:1 resolution with the map instead of the lower resolution the original used, which is a real change in what you can read off the screen rather than a cosmetic one. The README also mentions a raised ceiling on MicroSims (XMIC) and movable objects (XTHG), a terrain generator with configurable features, new isometric data views including height map, service coverage and transport-trip overlays, more zoom levels and layer controls, and optional dark underground views.

The architecture is a Godot 4.7 project rooted at game/project.godot, written in GDScript, with the engine bundled into the release packages. The README notes that many fixes identified by sc2kfix have been applied or ported here, and that the sc2kfix MIT notice is retained for adapted work, which tells you the codebase inherits behaviour from a separate reverse-engineering effort rather than inventing it all.

Installing OpenSC2K and importing your first city

The README gives two routes. For the packaged route, download a package from GitHub Releases; the installation instructions for Windows, Linux and macOS live in docs/install.md. The packages include the engine, so Godot is not required. The releases list shows v0.1.3 published on 2026-09-28, with v0.1.2 two days earlier and nightly builds in between.

For the source route, you need Godot 4.7 and your own copy of the game. The README gives exactly one command:

# from the repository root, with Godot 4.7 installed
godot --path game

After that command, the app presents an import prompt. Navigate to where your copy of SimCity 2000 is stored and select SIMCITY.EXE. The app checks the supported version and imports the game files. If the version check fails, nothing downstream will work, because the graphics, text, sound and music all come from that import.

If you plan to build or contribute, the README points at game/project.godot to open the project in Godot and gives one validation entry point:

tools/validate_project.sh

The development notes add two constraints that matter if you run the tests yourself. The tests use silent audio, generated city fixtures are committed to the repository, and original-data audits need references/SIMCITY2000 while renderer and media tests can also need imported packs in ext/. In other words, the test suite is not fully self-contained: parts of it need the same retail data the game does.

The .sc2x save split is the sharpest edge in the project

The README draws a hard line: larger cities and per-tile data maps use .sc2x saves, and the original game cannot open these files. Original .sc2 cities keep their separate compatibility mode. That is a one-way door in practice. If you build a 256-tile city in OpenSC2K, you cannot hand that save to SimCity 2000 and keep playing it there. The feature that most justifies using the remake is also the feature that locks the output to the remake.

That is a deliberate trade, and it is worth naming as one. A re-implementation that only ever produced byte-identical .sc2 files would be limited to the original 128-tile grid and the original data-map resolution, which would remove most of the reason to run it. The project chose reach over round-tripping.

The second limitation is the import requirement itself. Without a supported copy of the 1996 Special Edition, the packaged builds have nothing to render. The README does not document a fallback, a demo dataset, or a way to run the app with placeholder assets. Third, the project is developed with the assistance of AI tools, including large language models, for code generation, refactoring, research, documentation, testing and debugging; AI-POLICY.md sets out the policy, and the README states that all architectural decisions, implementations and contributions are reviewed and directed by the project maintainer. That is a disclosure about process, not a defect, but it is relevant if your organisation has rules about how contributed code is produced.

OpenSC2K against LinCity-NG and against decompilation projects

The obvious comparison in the same space is LinCity-NG, which people search for alongside this project. The difference in approach is fundamental. LinCity-NG is an original city simulation with its own art, rules and economy; it owes nothing to Maxis and needs no retail data to run. OpenSC2K is a compatibility project: its reason to exist is reproducing SimCity 2000's behaviour and reading SimCity 2000's files. If you want a free city builder that installs and runs with no strings, LinCity-NG is the cleaner answer. If what you want is SimCity 2000 specifically, with its original graphics and music, LinCity-NG cannot give you that, because it never had those assets.

The other adjacent category is decompilation and source-port work, the territory people reach for when they search for SimCity 4 decompilation. Those efforts typically aim at a faithful rebuild of an existing binary, sometimes with the goal of producing something close to the original. OpenSC2K is not that. It is a re-implementation with extensions: bigger maps, denser data maps, more zoom levels, external asset packs. The README's own wording is that it is an independently written re-implementation, and the extension list makes clear that fidelity to the 1996 feature set is not the only goal. The sc2kfix relationship reinforces the distinction: fixes flow in from that project rather than OpenSC2K trying to become it.

Maintenance, licence and what an upgrade costs you

The repository is not archived, and the last push was on 2026-09-28, the same day v0.1.3 was published. Release cadence is visible in the release list: v0.1.2 on 2026-09-26, v0.1.3 on 2026-09-28, and a nightly build tagged nightly-20260927 between them. Nightly builds are published, which means the project ships something continuously rather than only at versioned milestones. Anyone depending on a stable behaviour should read the release notes for the version they install rather than assume the nightlies match.

Upgrade cost is dominated by the save format, not by the code. Version bumps in the 0.1.x line are close together, and the README does not document a save migration path or a rollback procedure for .sc2x files. If you have invested hours in a large city, the practical question before upgrading is whether the new build still opens it. The README is silent on that point, so treat your save directory as the thing to back up before you switch builds.

On licensing: project code is MIT. Two bundled components keep their own licences, the Rajdhani fonts under game/assets/fonts/rajdhani/OFL.txt and Godot WRY under game/addons/godot_wry/LICENSE. The sc2kfix MIT notice is retained for adapted work. None of that covers the game data you import, and the README states the MIT license does not grant rights to the original game or its assets. If your use case depends on redistributing anything derived from the imported files, that is a question for your own counsel, not something the project's licence answers.

Editorial conclusion

OpenSC2K suits players who still own SimCity 2000 Special Edition for Windows 95 (1996) and want larger maps, per-tile data views and external asset packs without touching the original executable. It is the wrong choice if you want a game that runs without that retail data, if you need cities the original engine can still open, or if you expect an official Android build. Before adopting it, check that your copy imports cleanly at the SIMCITY.EXE prompt and that your existing saves are .sc2 rather than .sc2x, because the compatibility mode is split along exactly that line.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. nicholas-ochoa/OpenSC2K on GitHub
4. README
5. Releases