DEVELOPER'S JOURNAL
ONE PERSON'S RECORD.
This game is being made by one person. Below are the entries I have written so far, and a timeline from the first day to now.
THE RECORD CONTINUES.
DEVELOPER'S JOURNAL
Entries
Five so far, newest first: stack, scene, combat, characters, verification — including the pitfalls and the parts that aren't done.
- NOTE 00 · HOW IT STARTEDOpening with a picture — P0B dev notesPicture first, code second; how the stack got picked and where AI sits in the workflow; the first phase closed in four days, the holes of the online month, and the honest state after one month.
- NOTE 01 · THE FORESTForest scene struggles — from one style picture to walkable terrainWhy the reference picture can't be swapped, how the terrain is baked, the curtain at the map's edge, and two crashes: the title screen torn down and the guardian statue that read as a shrine.
- NOTE 02 · ONE EXPEDITIONOnline combat pitfalls — server authority, the card pause and the week in TokyoWhy everything is decided on the server, how “you stop, the world doesn't” got settled, the warlord's four moves, weather that only changes the light, and the absurd failures of restarting a server in Tokyo.
- NOTE 03 · FROM A SHEET TO A BODYCharacter pipeline struggles — from sheet to rigid partsWhy asking a model for a 3D character outright crashed, the pipeline that worked instead, characters without skeletons, the goblin's orientation, the vampire's cape and the Evil Minotaur's four versions in a day.
- NOTE 04 · HOW I KNOWEvidence process notes — why not to trust your own screenshotsHow a one-person project keeps from fooling itself: evidence is appended, never rewritten; screenshots aren't proof; metrics are only the pass mark; and the incidents the process actually caught.
TIMELINE
So far
From the first day to the day this page went up. Only things that happened.
Started from four pictures
Picture first, code second. One of four candidates was chosen; the same day, two builds that passed every machine check failed by eye and were redone.
First playtest passed
Leave town, finish a run, come back — the whole line held for the first time. All three languages have been in since this day.
First phase closed
The swordsman and the warlord got their final look. Four days in total.
Title screen torn down
Too far from the reference; the whole line was shelved. A few of its techniques went to the battle scene instead.
The warlord's sixth version passed
Rejected three times in a single day. The fourth version failed on the roar frame.
The title menu finally matched
The reference had no particles. By the third version, only a 2.8-second breath was left.
The Tokyo server did not recover
The remote restore failed; the rollback succeeded. Written down as two separate things.
Site published
This page went up. The game is still being made.
FIELD ARCHIVE
IN DEVELOPMENT
Where everyone waits before leaving and after coming back.
The only dungeon you can enter today. Flagstones, arches, and a fight that has not started yet.
The same field under a different sky. Weather changes the picture, never the rules.
A FEW FRAMES KEPT ALONG THE WAY
Know More About
Opening with a picture — P0B dev notes
Picture first, code second; how the stack got picked and where AI sits in the workflow; the first phase closed in four days, the holes of the online month, and the honest state after one month.
START WITH THE FIRST ENTRY →