How it works
A persistent strategy MMO you play by writing Python that runs on the server. The full technical description of Logiston — what it does, what it is made of, and what state it is in.
The premise
Take the idea behind Screeps — a persistent world you program with code instead of clicks — and move its centre of gravity from abstract combat stats to logistics. You write Python that runs on the server around the clock, building and optimising supply networks.
You beat rivals by out-supplying them: combat outcomes are a deterministic and deliberately boring function of supply. No fuel, no movement. The repository holds the design and build documentation, structured so an agent loop can build it ticket by ticket.
What is included
Player-authored Python executing server-side on a persistent world tick
Combat as a deterministic function of logistics rather than a separate stat system
Design and build documentation structured for incremental agent execution
How it is built
Logiston is built on Python, Specification and Game design.
It carries 111 commits since Jun 2026, most recently changed in Jun 2026.
The method behind it
Every project here starts as a written specification, and the specification stays authoritative once code exists. The repository keeps a build plan with live status, an append-only decision log recording where the implementation departed from the plan, and a handoff document describing the true current state — including the parts that are not finished.
That is why a portfolio this wide is not a shallow one, and it is why this page can describe the product without overstating it.
Current state
Specified. Designed in full, build not started.
The source is private. What this page claims is checkable against the product itself, not the repository.
Next
Build Logiston
The design is finished. Ask about implementing it, funding it, or taking it somewhere else.