Your bot lost. Do you know why?

Why hello Reader,

I watched my bot lose a game last week. Stared at the score screen. Knew something went wrong around the three-minute mark but couldn’t tell you what.

Sound familiar?

Telemetry replaces the guesswork. When your bot loses, terminal print outs tell you what happened during 1 game, telemetry tells you what happened over many.

I built a dashboard that layers my bot’s decision data on top of replay analysis. Battle sim confidence over time, army value curves, worker counts, resource divergence, all plotted so I can see the exact moment things went south. This week on PostBots, I walked through how it works.

The stack is lightweight: STDERR and STDOUT logs piped into DuckDB, visualized with Streamlit. You can also use JSONL locally if you don’t want the database overhead. Organized events you can query instead of scrolling through raw print output.

This came out of our PostBots session on Stop Guessing Why Your Bot Lost With a Telemetry Dashboard.

Open your bot’s logs this week and add one structured event — what your bot was thinking at a decision point. Just one. You’ll see the difference immediately.

​[Come join us for the next one ->]​

Talk soon,

Drekken