Behind the journal
Where the pictures
and numbers come from.
Everything in the journal comes from the project itself: its development notes, its code, recorded measurements and captures.
What you are reading
This is an edited account of PixelPunk’s development up to 21 October 2026. It is organised by milestone, so individual iterations are folded together. Chapter four jumps ahead to include the later texture work, because the material story is easier to follow that way.
PixelPunk is a desktop diorama builder made in Godot, with procedural town geometry and a cozy, playful, architectural look. The project notes use Tiny Glade as a reference for interaction and construction; there is no affiliation.
AI tools were used for implementation and review during development, and to write this journal. The project’s creator made the visual decisions.
Choosing the images
The project has thousands of screenshots, many of them taken to prove that some unrelated change left the picture alone. Most of those would add nothing here. The journal uses distinct scenes and close-ups, and shows matched comparisons only where they explain a visible change.
Every in-game image is an existing development capture, converted to WebP for the site. None of them are generated mockups. The lighting views come from different milestones and say so, and the construction playback is a short run of archived frames.
What the numbers mean
Each performance figure comes from a specific recorded experiment named in its chapter. Frame time, input-handler time, release cost and delivered light measure different things, and they can’t be added up into one claim that the game got some percentage faster.
The measurements and test results come from the development records; they were not rerun for this journal. A Windows export is recorded, but a successful export does not establish how the game behaves on Windows.
Where the story stops
The beautify chapters cover the plan’s work up to 10 October: the defect sweep, the night palette stage with its retune, quays, tide marks, painted metal, closing measurements and a corrected frame-time figure, then the fog and smoke stage, the island-edge stage, the skyline, neon bay and golden-hour stage, the stage of small items and the stage that lights the trees from every lantern, each with its closing measurements. The creator signed off the island-edge, skyline, small-items, tree and lived-in town stages; the lived-in town chapter also covers its closing measurements and the later trim of its window-box planting. The motion stage closed in four groups, from a setting for ambient motion to a veil of rain that takes the colour of the lights, and the creator approved all four. The edges and pixels stage closed on 8 October: an ink line that was tried and left off, a cheaper finishing pass and a camera that keeps the pixels fixed to the world, which the creator tried live and kept. Chapters twenty-eight and twenty-nine follow the polish stage, which is complete. Its first round brought the hover change, the new stone, lawns, paving, water shadows and lens blur, and its second the cables, the replanted Harbour, the quay swags, the rainy overcast and the placeable beacon. The third made the art pixels grow with the window and set the interface in a pixel font. The creator approved all three rounds; whether the font’s smaller text and the smaller interface at 2560 by 1440 should stay is still the creator’s call. Chapter thirty starts a new plan for things to place and better controls: fixes to the keys and grips, boats that can be stretched, come in six styles and tie up at the quay, a floating jetty, the boat stage’s closing checks with its first builds, and move and resize arrows drawn sharp at every zoom. Chapter thirty-one follows the tray groups and the ironwork, street life and waterside stages, all closed, with the bike redesign the creator asked for and the waterside pieces that appear by themselves, which the creator kept. Chapter thirty-two covers the first castle stage, the architecture, which the creator approved on 15 October. Chapter thirty-three covers the second castle stage, the grounds, from a crag with a stair wound round it to a castle starter on the loch, with the stage’s closing measurements, its builds and the creator’s answers on its sheet; the changes they asked for are queued, not built. Chapter thirty-four covers three control parts: one map for every key, a turn grip and arrow-key nudging for props, and a reworked camera. The story stops there, on 21 October: selecting several parts at once had begun but was not finished, and gamepad controls are still a plan. Chapter seventeen still describes the plan as it stood on 25 September; its later stages are proposals, not results. Where the project’s creator accepted a shortfall or answered a review question, the text says so, and those answers can still change. Earlier chapters describe the versions shown in their pictures. The recorded game runs were on Mac. Windows builds were exported but not tested on Windows.
Source excerpts
The linked excerpts are the original technical notes behind each chapter. They include source filenames and line numbers from the time they were copied; those may have moved in later versions.