DEVLOG | May 3, 2026

Combat event log and use revised asset bundle

implementation

This was an implementation day: less about ceremony, more about tightening the shape of the thing until it behaved a little more like itself. 17 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 issue, map, asset, bundle.

What moved

implementation moved through use revised local asset bundle, add auth join smoke, zoom external cameras closer, add account browser handoffs, add postgres persistence backend, add session event log, add combat event log, and stabilize primary fire cadence.

What I learned

The visual effects work keeps coming back to timing and restraint. Smoke reads best when it behaves like consequence: brief enough to belong to the event, persistent enough to tell you what just happened.

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.