WHAT A STAMP COLLECTOR WANTS

The first one worked, and that was the problem

By one measure SCS1 was a success. Four out of five people who signed up actually played it. For a hobby project with no marketing, that is a real number.

Here is the rest of the table.

Nobody stayed. Nobody paid. Nobody said a word to each other. That last one stung the most, because a chat channel with zero messages in it is not a quiet room. It is an empty one.

The diagnosis took a while to accept, because it meant throwing away working code. The theme tested fine. People liked the concept; they liked the aesthetic; they came back to look at it. What they did not like was that the game never asked them anything. You set something in motion and then you watched a progress bar honour the commitment. The player was an observer of their own strategy.

A game that you watch is a game you can stop watching.

The tie-breaker

SCS2 is a sequel in theme only. The concept survived. The genre did not.

Every design argument on this project now gets settled by one question, and it is deliberately blunt:

Waiting loses. It loses even when waiting would be more realistic, more balanced, or easier to build. Timers that exist to pace you, resources that accumulate whether you are paying attention or not, animations you cannot interrupt, upgrades that are simply better than the thing they replace — all of it is the SCS1 failure wearing a new hat.

The corollaries fall out quickly. Unit losses are permanent within a session, because a loss you can undo is not a decision you had to make. Encounters are built around a small number of genuinely uncomfortable choices rather than a long tail of obvious ones. And the target is not "hard" — it is legible. The player should always understand what happened and why. Complexity is welcome. Confusion is not.

What is actually settled

I want to be honest about the state of this thing, because devlogs have a habit of presenting a finished design as though it arrived fully formed.

The original SCS2 prototype was turn-based, grid-based and card-driven. All three are cut. The grid, the pathfinding, the isometric view, the room generator and the card system have been deleted from the project. They are in the git history if I am ever proved wrong, and I might be.

What replaced them:

• Top-down and real-time. No turns, no action points, no cards.
• You directly control an agent. Movement is on the keys, under your hand, all the time. Apollo is the one you start with.
• Units move freely, off the grid. Terrain and buildings snap to 32 pixels because that is how you author a readable level and draw consistent art. It is never a constraint on where a unit can stand.
• Maps are hand-made. No generator. A generated map is an average map, and an average map has nothing to say.
• Crisp pixel art at 32x32, on Godot 4 with C#, targeting Steam.

What is not settled is the shape of the moment-to-moment game. There is a world, a character you drive around it, things you can walk up to and use, and units that navigate on their own. There is not yet a loop I would defend in an argument. Finding it is the work.

Ruined marble, not neon

The obvious look for an AI game is cyberpunk: black, neon, rain, screens. SCS1 was that, and it was fine, and it was also identical to a thousand other things.

SCS2 is Olympian. Ruined Greek marble platforms floating in a teal void. Gold inlay running through the floor like circuit traces, converging on a sun rosette. Teal light bleeding up through the cracks, because the data layer is underneath everything and it is getting out. No enclosed rooms — an open platform over nothing, with cover made of fallen columns and broken walls.

Apollo is a sun god, so the player is gold. Gold belongs to the player and to nothing else. Teal is the world's data. Azure is the interface talking to you, and never appears in the world itself. Three colours, three meanings, no overlap. If you can see it and it is gold, it is yours.

The camera looks straight down, which sounds like a small decision and is not. Nothing can show its side. A standing column is a circle. A toppled one is a cylinder seen from above. Height is communicated with a single lit pixel along one edge and a shadow offset two pixels down and to the right, on every object in the game without exception. Break that consistency anywhere and the scene stops reading as a place.

More on the art in a later post, including the colour-theory argument that killed matrix green.

Where this is going

Prototype MVP through the back half of this year. Steam Early Access in 2027, single-player. 1.0 in 2028.

Next post: the systems that already exist, and what it feels like to walk Apollo around a platform that does not yet know what it wants from him.