Myself and @chad dive into the art of recognizing early Zerg rushes, refining scouting loops, and debugging macro transitions that choke a bot’s economy. The pair also analyze Dominion Dog and Negative Zero replays to unpack build-order adjustments, economic thresholds, and reaction heuristics.
Key Takeaways:
Rush heuristics matter: pools starting before 40 seconds, no natural hatchery, or no gas are strong indicators of a Zerg rush.
Early-scout survival is crucial — widen scout paths or use circular “ring” scans to avoid dying in worker lines.
Timing thresholds (e.g., pool started < 40 s → rush likely) and build-progress data help quantify enemy intent.
Enhance rush detection logic to cancel unsafe expansions and reposition bunkers on the high ground when under threat.
Avoid macro choke-ups: delay tech or expansion floods until a third base or ≈ 600 mineral + gas income.
Against Terran, swap full walls for Reaper walls or partial block-offs to reduce tank splash traps.
Balance learning from frameworks (like Ares’s opinionated heuristics) with custom detection tuned to your bot’s playstyle.