Experiments in engine, systems, and iteration
About this project → · Everything on the site
Currently on: Core loop, Data-driven content, Room generation
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…
The run has a beginning now. You start in a stone room, walk to an arch, press A, and the screen digitizes into the clearing with the first room dealt. That is the whole of it, and it took most of a night, but almost non…
I sat down to run one performance measurement and got up fourteen hours later with a sword that hurts things, a campfire you build a log at a time, and a panel that floats a note in front of me so I don't have to take th…
The first generated room put 174 pieces of ground cover inside a 29 m circle, every one drawn from a uniform distribution over the disc. I put the headset on and it read as confetti. Nothing was wrong with any individual…
I spent a day putting the headset on, looking at the clearing, and writing down what was wrong. Six defects came out of it. Not one of them could have been found any other way, and that's the part worth writing up. What …