Everything posted across every project, newest first.
Currently on: Core loop, Data-driven content, Room generation
I spent a day measuring one number three times. Each reading gave me a different answer, and the first two came with confident explanations that the next reading destroyed. The number is how far from your head a mage's b…
I set out to measure what one particle effect cost. Twelve hours later I have a walkable game. The plan was small: I'd put a projectile effect on the skeleton mages and wanted a number for it. That means a device build a…
I added a projectile effect to the skeleton mages and wanted to know what it cost. The answer, after a detour I've written about separately, is: nothing at all, most of the time, and about ten milliseconds whenever you c…
I spent an evening unable to walk. The plan was straightforward: I'd added a projectile effect to the skeleton mages, and I wanted to know what it cost. That means a device build and a frame-cost sweep — nine phases, one…
Six times into the headset today, all of it on the run loop rather than on how anything looks. The short version is that a run can now be survived, and what you carry home is kept somewhere you can see it and take it bac…
I spent a long session building the economy — coin that drops and banks, a fountain that sells health, items you carry and lose — and the thing I'll actually remember is a mistake I made twice, in the same file, about tw…
Today the run got a fail state. Enemies walk at you, telegraph, and hit; health falls; the screen builds red; and dying digitizes you back to the hub with your unlocks intact. That was the largest gap in the project and …
I spent nine trips into the headset today on the sound a sword makes when it hits a skeleton. That is an absurd number, and almost none of it was the sound. It was me asking the wrong question, nine different ways, and s…