#002 · March 28, 2026
The first version of Noctus was real-time. It lasted three weeks before I understood it was a mistake. Not an execution mistake — a concept mistake. Real-time turned a decision game into a flow management game. You watched bars fill up. You tapped buttons to keep things from overflowing. It was fine. It wasn't Noctus.
I stopped everything and went back to the central question: what do I want the player to feel? The answer: the tension of someone who made a decision and is waiting to see if it was right.
Real-time favors reaction. Turn-based favors reflection. But neither captured what I was looking for: the feeling of a boss who gives orders, lets go, and discovers the results. A boss doesn't run every operation in real-time. He plans, delegates, and owns the consequences.
The weekly loop simulates that. You have a planning window — the beginning of the in-game week. You distribute your teams, set objectives, allocate the budget. Once orders are sent, you can no longer intervene. The week unfolds. And on Friday, you read the report.
This is the densest moment in the game. You have your map — territories you control, ones you're targeting, ones where you need to defend. You have your teams — their skills, their condition, their weekly cost. And you have a limited budget that forces you to choose.
The game never tells you what to do. It gives you information — rumors, surveillance reports, rival faction movements — and you decide. You can be aggressive, discreet, defensive. You can bluff a presence on one territory to secure another. You can sacrifice a team to protect a critical resource. Every decision is a bet on what others will do while you're not watching.
The weekly report is my favorite moment in the game — and the hardest to balance. It needs to be informative without being exhaustive. It needs to tell what happened without explaining everything. Some things remain unclear, because in the criminal world, information is always incomplete.
Consequences are long-lasting. A lost territory stays fragile for several weeks. An arrested crew member might talk — or not, depending on their loyalty. A betrayed alliance remembers. The game resets nothing. Every week is built on the weeks before.
The main challenge is simulating rival factions during the player's week of absence. They need to act coherently, reactively, and unpredictably enough that the player can't anticipate everything. No generative AI here — simple rule systems with enough random variables to create surprise without creating arbitrariness.
The other challenge: the report's readability. I tested several formats — tables, lists, free text. The fictional newspaper you see in the screenshots is the solution I landed on. It's slower to read, but it maintains immersion. And in Noctus, immersion is everything.
The weekly loop creates something rare in mobile gaming: anticipation. You think about your next session before it starts. You wonder what happened. You mentally review your decisions from the week before. The game exists in your head even when you're not playing.
That's exactly where I wanted to go.