merge j160-ramfloor: the energy-reserve FIRING FLOOR + ENEMY-EXHAUSTION ram trigger (default off)
TR_RAM_FLOOR_ENERGY and TR_RAM_ENEMY_ENERGY, both default 0.0, plus common_libs/movements/ram_decision.nim, the fire gate in ModularBot.nim, two offline measure_* tools and the A/B record. The j163 A/B (450 runs/arm, 0 env mis-set) is a clean negative: round-win 40.30% -> 39.70%, sign-flip p=0.7676, MDE 4.73 pp. DO NOT ADOPT; TR_RAM_FLOOR_ENERGY stays 0.0. The mechanism barely fired (0.04% of ticks, not the 9.6% the offline ruler predicted), so the null does not prove the knob inert. # Conflicts: # common_libs/tests/test_tfil_commit_env.nim
This commit is contained in:
@@ -98,6 +98,8 @@ TR_RAM_PLAN=off # the change-of-plan trigger (enemy outguns us while
|
||||
TR_RAM_PLAN_DIST=250.0 # px; max range at which the plan trigger may fire
|
||||
TR_RAM_PLAN_MARGIN=20.0 # energy advantage the plan trigger needs
|
||||
TR_RAM_PLAN_HITRATE=0.05 # pooled virtual hit rate below which the gun duel counts as failing
|
||||
TR_RAM_FLOOR_ENERGY=0.0 # j160 firing floor: at/below this self energy stop firing (0 = off)
|
||||
TR_RAM_ENEMY_ENERGY=0.0 # j160 exhaustion: last-scanned enemy energy <= this -> ram (0 = off)
|
||||
|
||||
# ── movement internals: tfil (the floor-is-lava field) ──────────────────────
|
||||
TR_TFIL_RANGE_LO=100.0 # px; lower edge of the range band the ring mover prefers
|
||||
|
||||
Reference in New Issue
Block a user