In development · one person · one ship
Build a ship on a grid. Crew it with people who have jobs to do and needs to meet. Mine the rocks that drift past, grow the food, keep the power balanced, and get everybody through the next sector alive.
Scroll
A person looks at their duty list and their needs and does the single most urgent thing available. That is the whole brain.
So you can always answer "why is he doing that?" in one sentence. Nobody has a hidden mood, a secret timer or a state machine you cannot see. When the engineer walks past a burning generator to go to bed, there is a number that says why.
You place hull in the vacuum, cut rooms into it, lay floors, and bolt everything else on top. Every piece attaches to something, and taking that something away is refused to your face.
Nothing is instant. Order a plate of skin and an engineer flies out through the airlock, hangs in the dark beside it and builds it.
Asteroid fields come past on their own schedule. Point the cursor and every mining laser on the hull points with you; a beam that stops in mid-air is that laser telling you it cannot reach.
What is inside a rock is inside it already. A worthless one looks exactly like a rich one, and finding out costs a whole unit of cutting.
I am building this on my own, and I write down what happens: the systems that turned out to be one system, the meshes that came out upside down for three months, the arguments with my AI pair, the days the whole design was wrong.
No roadmap theatre and no announcements about announcements. Just what I did this week and what broke.
Unidentified vessel · range 0.4 AU
Captain, this game is about to take off. What do you want to do?
A wishlist is the only thing that tells Steam a game exists.