FEATURE-23 · Hive defenders
Local tactical-colony revision; design/hive-raids.md. Explicit reactive priority tree: Queen absent -> disengage; boundary -> return; assigned pair protects threatened Forager; other pairs screen/intercept; relocation -> moving escort; otherwise patrol. Queen coordinates shared threats and roles rather than each fighter chasing the last shooter. Two standing patrol defenders, food permitting. Continuously moving 3D patrols with base radii115-151m, plus smooth per-defender phase variation and +/-12% radius variation, separation18m, escort80m, dedicated worker-guard orbit70m with260m target radius. Owner-approved wider hard Queen boundary460m replaces260m. Existing0.33x size,30 hull,78m/s, staged projectile fire, six-active/twelve-launch budgets remain. Deliveries fund births48initial/cap240, worker8/defender3, replacement worker reserve preserved; Foragers60 capacity/180m work/90s maximum sortie and situational partial returns. Distant fire causes Queen screening and worker recall, not unlimited pursuit. Tactics, live raid, colony, natural sortie and host/three-client regression tests pass. Render inspected. Human swarm feel, routing and group balance remain for playtest; protocol25 now required for Queen impact replication, with matched updated builds. Nothing deployed. Forager pause correction: unloading under recall previously switched to SEEK, then RETURN every frame, stopping repeatedly inside delivery range. Empty recalled workers now move in escort within rally range, pause their sortie clock and resume work when recall clears. No eligible work also falls back to moving escort. Obstructed mining targets are skipped for five seconds and depleted targets discarded. tests/forager_recall_trial.gd covers the real blocked mining ray, escort movement, single delivery and resumption; colony and natural sortie/interception/replacement/rematch pass. Protocol25 unchanged; no release.
Feature · 1 blitzer supportedOpen item