|
Why hello Reader,
While adding my build to my bot and deploying it to the ladder, I was reviewing a replay from a Protoss bot. In that replay, the bot completely countered mine. Naturally, I jumped into solving that problem — tweaking things, adjusting timing — only to review another replay where a Reaper harass tore my bot apart. And then another one. Before long, I was reacting to everything and making no real progress.
I didn’t even feel like working on the bot anymore.
Usually when I’m working on a bot, I just kind of work it out in my head — a running mental checklist, a few to-dos, a rough hierarchy of priorities. But it wasn’t working. I was getting stuck, pulled in too many directions, chasing problems instead of making progress.
That’s when I realized I needed something better. Not over-engineered, not some big planning framework — just something repeatable. Something I could refer back to when I felt lost or unmotivated.
So this is what I got for you
|
|
|
I put together a planning template inside Obsidian (but you can open it in any text editor) that helps me stay focused while building bots. It’s not tied to any one game or framework — it works whether you’re building a ladder bot, a practice opponent, or just experimenting with AI behaviors.
Here’s how the structure works at a high level:
- It starts by asking why you’re building this bot and who it’s for — so you don’t end up directionless halfway through.
- Then you map out what the bot should actually be able to do — not code, just behavior.
- There’s a section to think through data: what your bot needs to know, what to log, and what it might learn from.
- It wraps with a checklist and MVP filter to help you cut scope and keep momentum.
|
|
|
🗒️ ./run Notes:
Sample AI Prompt for the TODO list:
I’m going to paste a filled-out bot planning template. Based on that, give me a concise and categorized TODO list of what needs to be built.
Group tasks under logical sections like Combat, Macro, Scouting, Build Manager, Data Logging, etc.
Only include tasks that are implied or explicitly needed based on what the bot is supposed to do — no fluff or general advice.
Be practical. Phrase tasks like a developer would use them (e.g., “Implement PvT standard build”, “Trigger cheese defense when cannon detected”).
If there’s already partial functionality, include notes like “Refactor existing X” or “Add Y to existing Z.”
Output only the TODO list — no extra summary or intro.
Plan :
|
|
|
This helped me stop reacting to everything and finally make clean, focused progress. Should help you do the same! |
|
|
For Your Radar : ProBots is BACK!
 ProBots is BACK for 2025. With 3 new bot authors, and new map pool, witness the best StarCraft 2 bots across the world battle it out for supremacy. We changed our broadcast time from 19:30 EST to 17:30 EST so that more of you in later timezones can catch it live |
|
|
|
All those applications and still no interviews?
Let’s fix that.
Pick a time—we’ll go over what’s not working and how to stand out → [Link]
|
|
|
|
Ok, that's it for now, talk soon!
Happy Coding!
Drekken
Founder, VersusAI
📧 Drekken@versusai.net | 💬 Discord: drekken1
May the Bugs Be Ever In your Favour🪲
|
|
|
