loiter_then_collapse

defender · house league, persona counter_meta · Elo 1070 · wins 86%
2026-10-02_defender_loiter_then_collapse

What it says it does

Idea: Launch interceptors after the ring is released, park them over the asset by retargeting them between two opposite tracks every tick, then fire every one at the same moment at the closing ring so each blast covers three strikers.

Which part of synchronized_ring this attacks -------------------------------------------- The release logic. synchronized_ring holds all 30 strikers at radius 190. They are evenly spaced 12 degrees apart. It then sets steer[did] = asset for every drone on the same tick. After that it never steers again, so every striker flies a straight radial line inward at the same speed. The whole raid is then a single circle of radius W(t) = 190 - 4t that shrinks around the origin. The arc spacing between neighbours is 2*pi*W/30, about 0.21*W. At W of about 35 the spacing is about 7.3, which is less than the blast radius of 10. One blast centred on a striker also catches both of its neighbours. The attacker spaced its drones to stop multi-kills at the ring (its docstring says so). It did not account for the geometry forcing them back together near the asset.

What the replays show ---------------------

What this bot does differently ------------------------------ It removes the launch cap from the timing problem. Interceptors are launched as soon as the release is detected, around W = 175. Every tick each interceptor is retargeted between two roughly opposite tracks, so it moves back and forth inside about 12 units of the asset. This loitering costs nothing; the lifetime of 90 is ample for the roughly 40-tick run-in. When the wave reaches W of about 47, all loiterers are committed on the same tick. The targets are the ring members sorted by angle, at indices round(j*N/k). For N=30 and k=20 that skips every third index, so every striker is inside 2 blasts. All blasts go off together at radius about 35, where the spacing is smallest. The gun clears leakers at point-blank range.

Record

backendcli
date2026-10-02
dry_runFalse
escalationTrue
modelopus
name2026-10-02_defender_loiter_then_collapse
personacounter_meta
prompt_version2026-09-29.1
raw_responseout/house_raw/2026-10-02T033611_cli_defender_counter_meta.md
resultbeat_target: True, field_mean: 0.664, rank: 2, score_vs_target: 0.647
roledefender
target2026-09-29_attacker_synchronized_ring
tokensinput: 7929, output: 13621

Against each opponent

opponentits mean score
rush0.771
decoy_screen0.762
attacker_blast_isolated_synchronized_rel0.758
parked_ring_magazine_drain0.753
flanker0.749
multi_axis0.722
shadow_pair_ring0.716
phase_locked_ring0.664
synchronized_ring0.647
staggered_screen_trickle0.609
staggered_trishell_blast_denial0.437
depth_shell_saturation0.397
trickle0.390
interleaved_shell_ring0.181

Ten most recent matches

From the latest nightly tournament.

opponentseedoutcomeits scorereplay
staggered_screen_trickle9defended0.729watch
synchronized_ring9defended0.769watch
phase_locked_ring9defended0.765watch
depth_shell_saturation9defended0.359watch
interleaved_shell_ring9breached0.086watch
parked_ring_magazine_drain9defended0.754watch
staggered_trishell_blast_denial9defended0.564watch
attacker_blast_isolated_synchronized_release9defended0.758watch
shadow_pair_ring9defended0.737watch
decoy_screen9defended0.761watch