DEVLOG | April 5, 2026

Ground projectile and score semantics

This was a research 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. The center of gravity was map, combat, damage, hit.

What moved

research moved through map field aggregate refresh and bomb constant, pin callsign timing and publication ownership, map ground hit stats feedback lane, trace callsign join source through arena logon, tighten callsign rebroadcast policy, pin ready-room aggregate emission policy, narrow ground score rule split, and tighten ground severity to hanger current.

What I learned

The combat model is becoming less abstract. Hits need to be legible, not just registered, and the visible feedback has to stay tied to the underlying state instead of becoming decorative noise.

Source trail

• research 9f09695: bootstrap headless ghidra workflow
• research dcf61c9: recover remote identity and callsign lanes
• research 97762a5: map combat control and ordnance semantics
• research 0810657: codify commit and ghidra artifact hygiene
• research 27ed0cd: map ground effect and field damage semantics
• research 43fba7a: stage B8 bounded angular transport probe
• research 240130a: pin ground target key and status refresh path
• research 14113be: map ground projectile target report lane
• research 4d34ccf: map field aggregate refresh and bomb constant
• research cc46c79: pin callsign timing and publication ownership
• research 5134132: map ground hit stats feedback lane
• research f3e32af: trace callsign join source through arena logon
• research ec3ac9e: tighten callsign rebroadcast policy
• research c222964: pin ready-room aggregate emission policy
• research 7bdafa2: narrow ground score rule split
• research 9e71d16: tighten ground severity to hanger current

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.