apparent latency compensation bug
The just played Simplicity vs BananaBrain is a fine game by Simplicity. The early defense against zealots was especially well done, and Simplicity’s tech and attack decisions were good. Recommended.
In the meantime, I’ve hit a bug that’s slowing me down. I found a reproducible case where production fails because it tries to use the same larva to produce two drones. It looks like slippage in BWAPI’s latency compensation: The production system picks a larva to produce a drone. Ask the type during the same frame after giving the morph order, and you get egg; that is latency comp at work. Ask again a couple frames later, and the egg has turned back into a larva; the production system picks it a second time, and the second morph can only fail. I think it should be easy to work around, but can it be fixed? Latency compensation is not expected to be perfect.
It makes me wonder what other slippages may be hiding under the rug.
Comments
MicroDK on :
McRave reported a similar bug about ZergBirth: https://github.com/bwapi/bwapi/issues/850
I will suggest to report this bug on GitHub. It might be related to what McRave reported.
MarcoDBAA on :
Bananabrain often gets in trouble, when it is on the back foot and or has to deal with harassment. It likes to either rush or overwhelm with strong macro, both in many different ways. But it likes to be in the offense. Failing to do any real damage with the zealot runbys, and Simplicity converting the advantage into a lead by sacking the natural, BB had to play a game it does not like too much.
Jay Scott on :