Holearth · A three-day experiment
I wanted to switch my brain off. So I built Holearth.
A three-day experiment in eating real cities: open map data, satellite imagery, a growing hole, and a game for tired evenings.
Read the storyWhat I’m making, what I’m learning, and what happens along the way.
Plain-text article index · Full text of articles hosted here
Holearth · A three-day experiment
A three-day experiment in eating real cities: open map data, satellite imagery, a growing hole, and a game for tired evenings.
Read the story
Father Tarot · Experiments that stick around
A Notion API experiment, a two-year pause, and a weekend revival. How Father Tarot found a connection with Signailist.
TraceLore · Worlds, connections, and spoilers
From asking AI far too many lore questions to building a connected archive that lets fictional worlds unfold at your own pace.
The Last Hearth
Stronghold meets tower defense, with AI art, stubborn sprite layers, invented voices, and a deadline I set myself.
Personal · Lessons learned
From deleting three days of work to an unexpected cloud bill and a message sent to 500 people: the failures that changed how I build things.
Personal · How I started
An electronics kit for my kids led me to Raspberry Pi, escape rooms, and my first job writing software.
Personal · Engineering & teams
I had one week to learn why a ten-year-old GIS product was moving so slowly. The largest file was only the beginning of the story.
PZ Story Director
Ray missed a window, two NPCs drank a litre each from one bottle, and a tiny command became a state machine. My first steps toward physical NPCs.
Personal · AI & development
Sol builds, Luna tests, Astra untangles the hard parts. How I stretched my weekly limit while building PZ Director.
PZ Story Director
How I filled Kentucky with people behind closed doors: notices, radio calls, quests, and the first encounter with another voice.
PZ Story Director
Red icons in the corner were not enough. How panic, pain, and sadness started changing the picture — and why that needed a Java module.
PZ Story Director
Two mods, an app, and three ways to connect AI. Who does what, and how a line reaches the character.
PZ Story Director
How prepared lines help reactions arrive at the right moment — and how a phrase bank grew into a permanent free offline mode.
PZ Story Director
One line twenty times, rain in the middle of a fight, and a voice that cannot keep up. Why a fitting reaction takes more than good writing.
PZ Story Director
Chickens, jokes with friends, and magical watering. How two small mods led to the idea of giving my character a voice.
Romergo
Why good images drift during revisions, and how GENERAL, Render Eye, directing and quality checks help build coherent stories.
Romergo
How text, HTML, or PDF becomes a coherent visual novel through scene contracts, continuity bibles, two composition modes, MCP assembly, and render review.
Romergo
Romergo does not run arbitrary code inside a quest. Authors build behavior from nodes, variables, conditions, and effects, while HTML and CSS remain a safe presentation layer.
Romergo
How to release a story in parts, update chapters that are already published, and continue play safely after a new version.
Romergo
How separating a simple scene from a smart runtime brought preview, browser play, mobile screens, and synchronized Discord play together.
Romergo
Why Romergo chose an open project archive, offline game builds, and agent-assisted migration instead of locking creators into one editor.
Romergo
How Romergo lets a personal AI agent join a live Builder session, receive context and commands, use MCP tools, and return verified results without hosting the model.
Romergo
How a small prototype called Fibber grew into a distributed platform with collaboration, versioned publishing, and one shared story runtime.
No posts in this category yet.