Tech stack
A browser game in TypeScript and Three.js, a Laravel server that keeps the saves, art and sound generated from my own pictures and briefs, and a team of AI agents writing most of the code. Each piece links to the post where it came in.
Brackenmere runs in the browser. There is nothing to install.
Every line of the game. Town code never touches the 3D, so months of village life can run inside a unit test.
G11 The living town, written overnightThe 3D engine: an open world streamed in chunks, with haze, bloom and far tiles for the distance.
G15 Streaming an open world: chunks, paths and hazeBuilds the game and serves it while it is being worked on.
G01 Day one: a canvas greybox called BrackenmereThe interface over the 3D: the HUD, quest cards and storybook panels.
G26 A storybook UI built from research on child readersModels ship as GLB files, and every texture as KTX2, which the graphics card reads while it is still compressed.
G10 Performance by constructionA small backend so a game follows a child from one computer to the next.
Family accounts and saves. A grown-up owns the account, children play under their own names, and the server enforces the economy.
G16 A Laravel backend for familiesHolds every save and its full history: gold, quests, the village and who knows whom.
G16 A Laravel backend for familiesGenerated from my own pictures and briefs, then reviewed before anything ships.
A clean picture of each object to model from, plus textures and the storybook interface, on a capped budget.
G12 Meshy from Nick's own picturesTurns those pictures into 3D models, rigged where they need to move, through its API.
G12 Meshy from Nick's own picturesThe narration for the storybook opening, and a score timed to its pages.
G23 A storybook way in, and a fine first morningI write the briefs and play the builds. AI agents write most of the code.
Most of the building since 22 September, on my Mac and in the cloud, as owners, reviewers and verifiers.
A07 The team takes shape: root, owners and one reviewerThe first week of the build, then independent reviews and a second designer on big decisions.
A08 Three AI designers, one briefThe terminal app the agents run in, with scratchpads any of them can read.
A01 Handoffs, one worktree per feature and standing rulesBrowser tests that play the game, with time stepped by the test instead of waited for.
A02 Tests that step time instead of waitingEvery branch and pull request, so the cloud sessions and my Mac work from one record.
A04 Making the repo agent-ready, then guarding its rules with testsThe site you are reading.
Each post is a markdown file. Livewire pages render them, with no database.
The components and styling.