A hero, a wolf, a very patient messenger. And the things that went wrong along the way.
A fictionalised development diary, based on the project’s changelog. The chapter dates, beginning in February 2025, are a literary timeline rather than the recorded build dates.
I keep coming back to a very small idea: a hero walking to the right. He fights something, picks up the remains, sells them and buys a slightly less embarrassing weapon. Then he walks some more. I want to see how much of a game can grow out of that.
There is already one complication. I don’t want the road to end at a castle. I want it to go through history. Start with ferns, finish somewhere people have found a more expensive way to hit each other. Then send the poor man back to the ferns.
I have written “time loop” next to it. That should keep the scope under control.
The first playable prototype - v0.1. A stick, a boar, a long road.Archive image · cropped to remove interface text
Chapter 02 / March 2025
The shop is eating the adventure
The hero has a routine now. Hunt, fill the bag, go to market. It is oddly pleasant to watch. It is also very easy to spend more time watching him sell things than watching him do anything worth selling.
I’m trying to make the ordinary bits feel right before adding more of them. A reward needs to arrive often enough to notice. A better weapon needs to do something. And a character who goes shopping on his own ought to have at least a basic objection to buying rubbish.
The last point is apparently going to require supervision.
Chapter 03 / May 2025
One click, please
I want clicking to help. I don’t want to build a job that requires someone to sit here clicking forever. The Automat is becoming the answer: give the player a way to hand over the repetitive part, then let them step in when they feel like it.
In testing, a click can be a surprisingly complicated object. Sometimes the hero ignores it. A touch can count twice. A window can look closed and still be involved in the argument.
I’ve spent a while persuading one click to mean one hit. On paper this will be a very short change.
Chapter 04 / July 2025
The trousers should count
The numbers say the hero has new equipment. The hero still looks as if he has just climbed out of the same bush. I don’t like that.
Weapons, boots, headgear and armour need to show up on him. His hair and beard should still be his under all of it. As the eras pass, he should get older too. Otherwise all this time is only happening in the interface.
There is something good about sending a slightly bent old adventurer back to the beginning and seeing him young again. I’d like to keep that feeling, even when he is wearing something ridiculous.
Equipment studies: the first three eras. Better gear begins to show on the hero.Archive image · cropped to remove interface text
Chapter 05 / September 2025
It has started raining
The scene is much easier to leave running now that the world has something to do besides wait for a fight. Night arrives. The light changes. Rain comes through, and occasionally the weather brings something less polite with it.
Relics are making the hero harder to explain. A useful item can now leave him with horns, wings or an unexpected glow. I keep looking for combinations just to see what happens to the silhouette.
I have also had to make the sun round again. A small correction to the history of the universe.
Relic experiments - v0.5. The same hero, increasingly difficult to recognise.Archive image · cropped to remove interface text
Chapter 06 / November 2025
Someone needs the scrap
The loop works, but I’m still missing a reason to care about what survives it. A permanent bonus is useful. It doesn’t tell me who is waiting for it.
I’m working on a stranded messenger. His ship is broken, and the pieces have somehow ended up across human history. The hero finds what looks like scrap. Somewhere far away, somebody is very pleased to receive it.
That gives the repetition a different weight. The hero can go back to the start while the repair carries on. I want the messenger to talk about ordinary things as well. He has been waiting a long time.
An early version of the messenger scene, before the move to Titan.Archive image · cropped to remove interface text
2026
Chapter 07 / January 2026
The wolf is running backwards
There is a wolf beside the hero. He follows him, waits at the market and attacks the things that deserve it. I’m already reluctant to remove him from any test scene.
Unfortunately, his legs have other plans. The feet move the wrong way against the ground, so he appears to be running backwards while travelling forwards. I can’t stop seeing it now.
The run needs proper push-off and recovery. The bite needs a little preparation too, instead of the mouth simply appearing on the enemy. These are only a few frames, but they decide whether he feels like a companion or a loose icon.
The old comparison sheet makes the choice fairly clear to me: I want a forest wolf, with some weight in his body and a muzzle I can read at this size. There were cuter and darker proposals too. They would have taken him somewhere else.
The early wolf.Archive image · cropped to remove interface textThe forest-wolf redesign.Archive image · cropped to remove interface textAn archived wolf animation. Play it and watch the paws.Archive image · cropped to remove interface text
Chapter 08 / March 2026
A permanent address
The messenger belongs on Titan. I’ve settled that much. Saturn overhead, an orange haze, a lake that is definitely not water. Salo waits on the shore and watches Earth from much too far away.
His dialogue is getting easier to hear in my head. Patient, a little lonely, capable of having an opinion about a bent plate. He has named a flat rock Bogdan. I’m keeping Bogdan.
The repair is starting to pull the rest of the game toward it. Equipment, portals, bosses: they can all be part of getting something back to Salo. I’d rather discover that through play than explain it in a wall of text.
I’ve kept the rejected designs. One Salo had three legs. Another was a clockwork snail. The Lighthouse Keeper gives me a face I can recognise in a tiny portrait without making him look too human.
Three early Salo candidates: a tripod messenger, a lighthouse keeper and a clockwork snail.Archive image · cropped to remove interface text
Chapter 09 / May 2026
The merchant has been helping himself
I have looked more closely at the money. The hero has been buying equipment he doesn’t need, putting it in the bag and selling it back at a loss. From the merchant’s point of view the system is excellent.
He should compare the offer with what he wears. If nothing is better, the money stays in the purse. That sounds obvious until I look at what it does to every upgrade price around it.
Now I have to rebalance the market. It is worth it. I want returning to the game to feel like checking on an adventurer, not discovering what he has done to the family finances.
Chapter 10 / July 2026
Please don’t punish the holiday
I’m changing what happens while the player is away. Gathering can carry on. The important things should wait. It feels wrong to return and learn that the boss, the next era and the interesting bit all happened without you.
There is a Rested bonus for coming back. I like that better than asking why someone wasn’t here yesterday.
Death needs the same care. It can set the hero back, but time should remember something of the attempt. That is where Echo fits. I’m trying to make failure leave a useful trace without making the defeat itself meaningless.
Chapter 11 / September 2026
Too much help at once
I have added enough systems that a new game is starting to resemble someone emptying a cupboard onto the player. There are useful things in there. That does not make the pile welcoming.
I’m spreading the discoveries out. A hint first, then the thing itself when it has a reason to appear. Salo can introduce some of it. The Journal can keep the explanation after it has left the screen.
I’m also trying to let messages finish being read. A speech bubble that disappears halfway through a sentence isn’t giving the game pace. It is just leaving someone to wonder what the rest said.
The backgrounds have their own small problems. The castle needs ground under it, and an entrance that actually reads as an entrance. Looking at the two versions side by side helps more than another line in the task list.
Before and after: giving the castle a hill and a proper entrance.Archive image · cropped to remove interface text
Chapter 12 / October 2026
A name, and a stone that needs work
ChronoLoops: Salo’s Monolith. The name finally points at the part I keep coming back to.
The white monolith gives the repair a shape I can recognise as it grows. A base, a taller body, cracks closing, symbols waking up. I want to be able to look at it and remember the work, without reading a percentage.
There are more companions now, with different reasons to take them along. The favourite should stay through the loop. I’ve become quite stubborn about that. Starting history again is one thing; telling the wolf he has to remain in the previous version of it is another.
The first boss also went through a few candidates. I keep returning to the Foremother and her nest: there is a reason for her to stand in the way. The dragon has acquired a different kind of reason. His scroll, seal and purse make the tax collection visible before he says anything.
Early first-boss candidates. The Foremother is on the left.Archive image · cropped to remove interface textThe Tithe-Collector Dragon, before and after his paperwork caught up with him.Archive image · cropped to remove interface text
Chapter 13 / November 2026
Let the shore breathe
The title screen has taken several attempts. There was too much going on, and for a while some of it looked as if it belonged to a different game. I’m returning to the image of Titan that made me want to stay there in the first place.
Saturn, wet rocks, the sirens and Salo moving between the beach and his monolith. The small movements matter: a glance, a strand of hair, a plate picked up and fitted. The menu can wait until someone moves the mouse.
I’m cutting the jellyfish out of Saturn’s face as well. They have an entire sky. There is no need to swim across the planet.
Chapter 14 / November 2026
Words that fit in the box
There are five languages in the settings now. That has turned a modest window into a fairly serious negotiation. A label that fits in English can arrive in German with more luggage.
Translating the menu is the easy part. Old equipment names, the Chronicle and messages already waiting to appear all need to follow the chosen language. I don’t want someone switching to English and finding half their adventure still speaking Polish.
The German, Spanish and Portuguese text still needs native review. I’m keeping that visible. I’ve also taken the synthetic narration out of the ending. The music and subtitles have enough room to do the work.
There are still things to fix. I can leave the title screen running now and watch Salo get on with his repairs. That feels like a decent place to stop this entry.
Chapter 15 / November 2026
The letters have to stay sharp
The title on Titan has settled, and the game now speaks five languages. That left a more everyday problem. When the window is no longer a neat multiple of the picture, the pixel letters start to wobble: a stroke is two pixels on one line and three on the next.
I have gone back to scaling in whole steps, so the text stays readable. A large-text option I tried along the way did not earn its place and has been removed.
Controller support is still only partial, but I am building the game with a pad and the Steam Deck in mind, for a Steam release on Windows, macOS and Linux. There is no date yet.