README

one change and your bot is useless

Drekken

It was 2 a.m. and I was completely exhausted. Honestly, I was mad at myself.

The ladder pool had just updated. My hardcoded wall-off was completely broken. I sat there manually pulling X and Y coordinates for every new natural, paying down technical debt I swore I would fix last season. I put it off thinking I had more time, and the map changes forced my hand.

You probably have code just like this hiding in your codebase right now. A piece of logic that only works because you explicitly told it where things are.

I mentioned this exact struggle in my Zerg Rush defense video.

White Puma reached my DMs: “I see your problem, and I have the solution.”

He came to PostBots and showed how he killed this technical debt without touching the map editor.

He taught his bot, Arty to feel the terrain.

Shifting from absolute coordinates to relative sensing gives your bot actual perception. White Puma’s ray-casting wall-off works on a three-step sensory loop:

1. Anchor to a dynamic known. Arpy starts the calculation at the natural expansion, a point that reliably exists on every map.

2. Sweep for the boundary. Arpy casts rays 100 degrees from the natural toward the map center, sweeping the terrain.

3. Measure the delta. Arpy hunts for the math. It finds the sudden jump in distance where the terrain drops off. That delta is the choke point.

Arpy handles narrow ramps, wide ramps, and flat ground equally well. The bot simply feels the space around it.

Seeing White Puma’s process reminded me why we stick to these principles. His first bot was completely hardcoded, and he is aggressively undoing that to make it dynamic.

We are building autonomous agents. Bots are like children. When we give them the answers, we deprive them of the learning. We strip away their ability to engage with their environment, making them dependent on us. That’s not autonomy.

Building sensory loops immunizes your code against ladder updates. You solve for the space itself.

Watch White Puma break down the exact ray-casting math👇🏾

⌨️ Next Commit

Find one hardcoded value in your bot that breaks when the map changes, and replace it with a system that can figure the answer out on its own. If it’s a set of coordinates, try ray-casting. Teach your bot to find the answer dynamically.

Be honest. Do you have hardcoded logic in there? Put up your hand ✋🏾 if you do. I did, and I still do, but I am committed to getting it out. I want to hear what you have. Tell me about it.

May the Bugs Be Ever In your Favour🪲

Email Preference:
Unsubscribe | Update your profile | 600 1st Ave, Ste 330 PMB 92768, Seattle, WA 98104-2246