Code: Terraform sends you to a frozen alien world and hands you a programming environment. Apparently humanity surveyed the available solutions and chose homework with weather. You write scripts to survey, mine, move resources and manage infrastructure, using a Python-like language rather than drag-and-drop blocks. It is not a promise of unrestricted Python compatibility. The appeal is turning separate machines into a coordinated operation, while a terminal-delivered mystery interrupts the work. If naming variables already sounds like an unreasonable holiday activity, the planet is unlikely to change your mind.
Early Access began on September 9, 2026. The game remains unfinished.
Reasons to look closer
The learning proposition is less severe than the storefront's lingering claim of no tutorials suggests. The September Code Lab expansion supplies 49 short Concepts lessons with runnable examples, while the first eight practice lessons start from a worked outline. That is a useful distinction: an example you can execute gives a mistaken assumption somewhere concrete to collide with reality. These are not 49 new campaign levels, nor a guarantee that learning will be effortless. They do mean the game has more teaching material than its stern recruitment poster admits.
The surrounding tools take the same work seriously. Documentation, console and editor can open in separate windows, and external-editor support includes VS Code, PyCharm and Zed. Enums, custom exceptions and richer custom panels extend how you organize code and interact with it. The attraction is not simply writing more elaborate instructions for a machine. It is making those instructions intelligible enough to maintain tomorrow, when today's brilliant shortcut has become an archaeological mystery. For players who enjoy refining a workflow, arranging the workspace can be part of the pleasure rather than an obstacle between them and the game.
A factory with a memory
Industrial upgrades give that organizational effort something tangible to serve. Mk II smelters and fabricators double processing speed for one and a half times the power; Mk III reaches four times the original speed for three times the power. More throughput is attractive, but the electricity bill still attends the meeting. Upgraded machines retain recipes, connections, scripts and stored goods, so improving production does not require pretending the factory was just invented again.
Seismic Sonar opens deeper oil opportunities, while the Battery Charger lets a parked Pioneer exchange depleted batteries for charged ones. Replenishment becomes part of expansion. Meanwhile, machine-independent Automations continue running regardless of power, separating supervisory scripts from the hardware they oversee. Your management layer can remain on duty even when the machinery has developed strong opinions about electricity.
That separation also raises the value of readable status information. Script status messages and conflict handling for changes made in both internal and external editors support a colony whose dependencies you must understand. The satisfying ambition is not more windows for their own sake, but fewer mysteries about which part of your own plan stopped cooperating.
Keep the keyboard responsive
There is a practical caveat behind that ambition. AppsMafia attributed major Linux map and typing problems to the earlier renderer and moved both desktop versions to Electron in October. The developer reports improved responsiveness, not a result to assume on every machine. In a game about typing instructions, the keyboard should not need its own queue management script.
Saved colonies, settings and scripts carry across that migration, but earlier unsaved edits held for recovery do not. That distinction is worth respecting: a functioning factory and the clever line you had not saved are different possessions. Save the clever line. It has no mining robot to defend itself.
Less uranium, more understandable menus
Late-game atmosphere machines now produce substantially more oxygen, pressure and heat, reducing the equipment and uranium needed for the final stretch. That is a useful direction for an automation game: greater scale need not always mean asking the player to order the same contraption until the horizon files a complaint. Library corrections also restart dependent scripts stopped by their errors, connecting repair with recovery rather than leaving every affected worker awaiting a separate invitation.
The current localization reaches 19 languages while leaving script code unchanged. Menus, documentation and lessons can change language without splitting shared code into separate dialects. The translations are AI-assisted, and the developer still requests corrections, so coverage is not a certificate of flawless wording. For this particular game, understandable documentation is part of the machinery. A planet run by code is quite enough responsibility without having to debug the manual as well.