DEVLOG | April 29, 2026

Projectile impacts and joystick input

implementationresearch

This was a research-and-implementation day: less about ceremony, more about tightening the shape of the thing until it behaved a little more like itself. 16 commits landed or were available locally. There was also a decent amount of local conversation around the work, but the useful part is the trail it leaves: questions asked, decisions narrowed, and a few assumptions made explicit. The center of gravity was world, issue, calibration, asset.

What moved

implementation moved through set parked taildragger spawn pitch, add bomb load and controls help, gitignore local headless sqlite database, retune persistent peer takeoff, bank hold, and full throttle, document local server, client, and headless run commands, recalibrate aircraft lod distance bands in mm, tune model display distance, and plan tasks: projectile hull impacts, joystick input.

What I learned

The network side is slowly turning from a research map into an implementation contract. The important bit is keeping the protocol understandable enough that future gameplay work does not have to rediscover it.

Source trail

The research lane stays research, and the implementation lane stays implementation. This post is a narrative summary of local work, not a publication of raw originals.