jedarden fec7721129 fix(plan,engine): align attack radius with combat density targets ... Plan §3.4 gap: default attack_radius2=12 only achieved 45% combat_death rate for 2-player random vs random, below the 65-80% target. Changes: - Plan §3.4: specify per-player-count attack_radius2 values (36 for 2p, 12 for 3p+) - engine/types.go: set AttackRadius2=36 for 2-player matches - engine/match.go: fix misleading comment about attack radius Verification (20 matches each): - 2-player random: 75% (was 45%, target 65-80%) ✓ - 2-player aggressive: 100% (target 65-80%) ✓ - 6-player mixed: 100% (target 100%) ✓ The larger 6-tile attack radius for 2-player compensates for fewer opponents and higher movement variance, while 3+ player matches use the tighter 3.5-tile radius as player density provides sufficient contact. Closes: bf-55ud Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>		2026-05-24 22:15:08 -04:00
..
notes	Add aichallenge ants research and initial requirements	2026-03-23 21:08:11 -04:00
plan	fix(plan,engine): align attack radius with combat density targets	2026-05-24 22:15:08 -04:00
research	Add research on LLM-driven bot evolution systems	2026-03-23 21:46:23 -04:00
phase6-deployment-checklist.md	docs(phase6): add deployment checklist and make scripts executable	2026-04-08 17:29:02 -04:00
spa-route-test-results.md	test(web): add SPA route smoke test script and results	2026-05-24 21:57:49 -04:00
wasm-bot-interface.md	feat(acb-api): implement bot registration, job coordination, and replay endpoints per plan §12 Phase 4	2026-04-21 08:58:42 -04:00