The Schemaverse

// About this game

The Schemaverse is best understood as mmo / rts built around code as the main verb, not as a normal game with a small programming minigame attached. The Schemaverse is a competitive space-strategy game that lives entirely inside a PostgreSQL database: you build and command your fleet with raw SQL, and if your PL/pgSQL is strong, you can write stored-procedure AI to run your whole empire automatically. It is the ultimate "the database is the game" experiment. The useful question for a new player is not simply "is it about programming?", but what kind of thinking it asks for: SQL, sql, strategy and open-source, and a willingness to test an idea by letting the simulation run. Released in 2012 by Josh McDougall, it sits in the catalog because the program you write is the thing that actually changes the game state.

The minute-to-minute loop is strategic rather than twitchy: you reason about territory, resource flow, production pressure, scouting and failure recovery, then encode those priorities into a bot that can act without you. The interesting part is not one perfect command; it is whether your system still behaves when the map changes, enemies interfere, or resources run dry. In The Schemaverse, that means the fun is in the gap between an intention and a working implementation. You start with a rough plan, translate it into the tools the game provides, then watch the result expose every missing condition. A direct solution may pass the first level or match, but the better solutions usually come from noticing a pattern: repeated movement, wasted work, poor targeting, bad routing, a race condition, a blocked path, or a decision that should have been stored as state instead of hard-coded.

The language side is centered on SQL, but the transferable skill is broader than syntax. You practice decomposition, debugging, iteration and the habit of reading the rules before blaming the machine. The advanced rating matters because the game rewards players who can structure larger solutions, reason about edge cases and tolerate several failed iterations before the system behaves. Because it is online, the game also has a social or persistent edge: your code has to survive contact with leaderboards, shared state, other players or changing live conditions instead of only beating a frozen puzzle once. The best sessions are usually not the ones where everything works immediately; they are the ones where a failed run gives you a clear hypothesis for the next version. If the game has leaderboards, ratings or community solutions, those become useful mirrors rather than just bragging rights, because they show how many different shapes a correct program can take.

The Schemaverse is strongest for players who like the feeling of making a system slightly smarter each time they touch it. It will be less satisfying if you want fast reflex challenges, cinematic spectacle or a puzzle with only one intended answer. The reward is more specific: seeing your own instructions harvest, fight, route, query, build, solve or survive without your hand on the controls. It is also easy to recommend as a trial because the entry cost is low: you can open it, test whether the programming model clicks, and only then decide how deep you want to go. Taken on its own terms, it is a practical way to turn programming concepts into a visible loop, where every bug is part of the play and every improvement has a concrete effect on the world in front of you.

// What you’ll write

The Schemaverse is played from inside PostgreSQL. You inspect tables, call functions and eventually automate decisions with PL/pgSQL.

SELECT * FROM my_ships;

SELECT move_ship(
  ship_id := 1,
  destination_x := 42,
  destination_y := 17
);

The Schemaverse ↗