Look up
The seventh and final treetop cutter didn't fall to a smarter fix. It fell to a smarter question: every verification screenshot the loop had ever taken was aimed at the horizon. Plus: the freeze is dead, felled trees stay trees, and the planet gets real regions.
The verification bug behind the rendering bug
Six treetop cutters down, and the report came back a sixth time: still cut off. The temptation was to doubt the reporter. The discipline was to doubt the camera. An audit of the screenshot rig found that every proof shot in the loop's history was taken at pitch zero — eyes level, trees at distance. The player doesn't play that way. The player stands under a tree and looks up. One new environment variable later, the rig could pitch the camera — and the first upward shot at a near crown reproduced the bug instantly.
Cutter number seven lived in one of the renderer's speed-ups, which had been told the crowns were smaller than they really are — so rays skipped straight through the fringe of every crown. Switch the speed-up off and the crown healed. Tell it the truth about crown size and the crown healed with it switched on. Seven mechanisms, one lesson now carved into the loop's process: verify under player conditions, not rig conditions.
The freeze
"The game is freezing a ton as I run around." It was the world catching up around the player as you travel — done all at once, every so often, and felt as a hitch every few seconds at a sprint. That work is now spread out so you never feel it, and the worst frame dropped from 45.6 to 14.4 milliseconds. You can run the length of the heartwood without a single hiccup.
A planet with regions
Until this week, the forest was everywhere and everywhere was the forest. Two attempts to give the world biomes died on cost — working out the terrain type on the fly ate nearly the whole frame. The answer was to stop computing and start remembering: the planet's regions are data now, decided once, and every part of the world knows whether it is forest, field, swamp, desert, or rock.
Even that nearly failed on a GPU quirk, now logged for posterity. Done the right way, the whole feature costs about a millisecond — and open country actually got faster, because empty fields skip tree work entirely. The framerate hit 85 in the plains test. Next up: each biome grows its own trees — squat and wide in the swamp, thin and sparse in the desert.
Odds and ends from fifteen releases
Felled trees no longer collapse into blobs when you walk away — resting logs are pinned in place and survive the chop site. Every creature, player, and corpse casts a grounded soft shadow that fades under cloud. Your target gets a proper frame — name, level, health, and a color that tells you at a glance whether you can take it. A Ghoul walks the night now, converted from the studio’s rig archive by an agent that had to author its attack and death animations from scratch, because the source rig never had them. And the whole thing — regions, shadows, Ghoul and all — is live in the browser at ractr.com/play.
Engine v0.22.23 → v0.22.37, fifteen releases, every one green across the full gauntlet: 45 unit tests, 4 DFD physics gates, a 42-stage two-server bot war, and the 22-millisecond frame gate. The loop keeps turning.