archive by month
Skip to content

ForceBot as a 5 pooler

As its opponents have long since noticed, ForceBot has become a 5 pooler. It does an economic followup, so there is some interest.

The picture shows Oyvind Johannessen’s base from ForceBot versus Oyvind Johannessen. Random Oyvind Johannessen ended up zerg, and was ready for the rush. Unfortunately, the defending zerglings chose to follow a circling overlord, so Oyvind lost its opportunity to return the pressure.

zerglings follow an overlord

ForceBot is trying to catch up in workers. As you can see in the minimap, it is 3 bases versus 2. Although it was ZvZ, neither side played aggressively, and the game went on for 45 minutes. It was fun, for a low-level bot game.

Oyvind barely defended itself while the zerglings were suffering from overlord fascination, and ForceBot started to dominate. ForceBot went hydra-lurker and took the map, rather a change from the 5 pool opener.

Oyvind has defended successfully

Oyvind understood how to hold on in a desperate situation. See all the blood? ForceBot could not coordinate an attack to climb the ramp. Oyvind is long-distance mining its natural and eventually retook it, while ForceBot went passive and sat around with its maxed army. The game ended when Oyvind mined out its natural and crashed. I expect that ForceBot would have won on points after the game time ran out.

This version of ForceBot seems to play similarly against all races: 5 pool, try to build an economy, lair, hydra-lurker. It’s quite different from the AIIDE 2017 ForceBot. It seems to have some added defensive smarts; it doesn’t appear to make pre-emptive sunkens willy-nilly any more, at least not often.

Trackbacks

No Trackbacks

Comments

Tom Peeters on :

I'm amused that you took notice that fast. This was actually just a mistake, where I accidentally left in a debug line that forced it to use a 5-pool build. Before that the 5-pool build was actually really bugged and it did a bunch of weird stuff, so I did some tests to smoothen it out. I was rather amused by the results though, as it won most of its matches while this mistake was in effect. Also, I'd like to point out that AIIDE 2017 ForceBot had a critical bug that prevented it from gathering gas (a result of having to switch from 3.7.5 to 3.7.4 for AIIDE), unfortunately it wasn't noticed until after the tournament completed. I don't expect it to have performed that much better though, probably something like 23rd or 24th, it's a tough tournament for a new bot after all. I'm certainly still updating ForceBot anyway, it's nice to see it get some attention here ;) Most of it's sunkens are indeed dynamic now, with only a single being enforced on certain builds.

Add Comment

E-Mail addresses will not be displayed and will only be used for E-Mail notifications.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA

Form options

Submitted comments will be subject to moderation before being displayed.