Method Archer
- Namespace
- GrindFest
- Assembly
- GrindFest.dll
Archer()
The kiting archer - the one probe in this class that has to be won, so its budget is what it fails on.
public IEnumerator Archer()Returns
Remarks
The budget is game seconds, not wall seconds (TryWaitUntil accumulates Time.deltaTime), so the 60f default is 20 s of wall clock at the suite's 3x - which is what "(20,5s)" in the failure line meant.
Measured 2026-09-16, the two builds side by side, same hero (Lv1 STR1/DEX1/INT1, Dmg 6-15, Stick + Plank Shield) and same monster (Skeleton Archer Lv4, 107 HP, Shortbow): editor WON 11,9 s wall = 35,7 game-s, Hits:10 DmgOut:109 DmgIn:10 player run 1 FAIL 60,0 game-s, Hits:4 DmgOut:39 - monster 68/107, 2,9 m, hero 60/62 player run 2 FAIL 61,5 game-s, Hits:7 DmgOut:90 - monster 17/107, 0,7 m, hero 48/62 So the kite is answerable - the hero closes to 0,7 m and lands 90 of the 107 damage - it just cannot always do it inside 60 game seconds, and the cost of chasing a kiter varies by a factor of four between runs and builds (15 game-s per hit in run 1, 8,6 in run 2, 3,6 in the editor). 180 game seconds is ~5x the editor win and still short enough to catch a kite that has genuinely become unanswerable, so this probe measures the fight instead of the budget. Compare a NON-kiting skeleton: WON in 9,6 game-s.