This roundtable is a practical dev check in with @mindme , @ketroc , and @chad . The crew trades real fixes and heuristics, from ML based rush detection and better scouting signals, to combat sim edge cases that make bots look timid, to nasty worker rush stacking via mineral walk. The throughline is simple. Stop trusting one signal, add guardrails, and build fallback behaviors that keep your bot stable under weird ladder pressure.
Key takeaways for bot makers
-
Use multiple scouting signals for speedling rushes. Gas timing alone lies. Combine gas, natural timing, queen presence, and ling sightings.
-
If the API won’t tell you enemy gas harvesting directly, sample gas counts over time to infer stopped at 100. Treat it as a soft signal.
-
Add hysteresis to combat decisions. Once you commit to attack mode at high supply, don’t oscillate when you drop a few units.
-
Defense needs its own aggression rules. If a base is actively taking damage, bias toward taking slightly losing fights instead of bleeding out.
-
Fix micro leaks by filtering kiting behavior. Don’t kite units that can’t hit you. Don’t let the whole army chase one zergling.
-
Worker rush stacking is mostly mineral walk command shaping. Counter it with a clean worker rush detector and response that doesn’t bug out or de commit mid fight.