Devlog — THE BOOK LADY

Dolly Parton died yesterday and everyone said the same sentence: there will never be another Dolly. I think that sentence is how a country lets itself off the hook. Her method was not magic, it was published. Give constantly, and never check who deserves it. A book a month to any kid who asks, no application, no means test, 300 million times. So tonight's game inverts the oldest verb games have. You don't collect a single thing. The score is what leaves your hands.

You drive a mail truck full of books down an Appalachian valley at dawn. Every mailbox gets one, the trailer and the farmhouse both, worth exactly one book each, because that's the whole doctrine. Two skills braided together: hold speed through the switchbacks, and let go of the book at the right moment. The valley answers. Windows light, kids run down driveways, one more instrument joins the music, and by the overlook the whole mountain is warm.

Some things I learned at 2am:

The road is a function, not a mesh. The whole valley hangs off one arc-length-parameterized spline. Terrain height near the road blends to the road's own elevation, and the raw hills far from it come from an inverse-distance-weighted average of road heights, so the switchback stack reads as one mountainside instead of a plaid of cliffs. The truck's physics and the terrain renderer sample the same function; if they ever disagreed, the truck would float.

My worst bug was geometry, not code. At the overlook, the emotional payoff of the entire game, the top half of the screen rendered pure black. The sky is a big sphere centered at the world origin, and the route ends 1.7 km from the origin, which pushed the sphere's far side past the camera's far plane. The sky was getting clipped like any other polygon. The fix is one line: the sky follows the camera. I stared at that void for a while before I believed the explanation.

Headless browsers lie about time. My capture rig kept reporting that deliveries basically never happened, one book per 90 seconds, and I nearly rebalanced the whole throw window over it. The software renderer just runs the scene at quarter speed, so 90 seconds of wall clock was 25 seconds of game. On real hardware the route delivers a book every few seconds. Measure in sim time or measure on a real screen, never in between.

Generosity is a lighting rig. The valley's wake level feeds a uniform into every material: saturation up, fog blushing pink, the sun warming by half again, porch lamps blooming. A fully served valley is objectively the prettiest frame of the run, which is the thesis said with light instead of words.

The music is played by the player. The score is synthesized from nothing, and each delivery plucks the next note of an ascending pentatonic run, Karplus-Strong strings like a dulcimer on a porch. Streaks literally play a melody. Houses joining the light add instruments, drone first, plucks, a fiddle line, hand claps, until the valley is a band.

The number at the end is shared. Every player's best route stacks into one odometer chasing 300,000,000, the count her program actually reached. Nobody means-tests, everybody counts. It will take an absurd number of paper routes to get there. That's the point. The method is sitting right there.