random Steamhammer notes
A few unrelated notes about Steamhammer:
The bug that causes Steamhammer to drop commands is due to a missing &
in an inconspicuous declaration, causing a data structure to be copied instead of referred to. Updates are made to the copy instead of the correct data, then the copy is thrown away. Even after I deduced that something was being copied behind the scenes, it was tricky to nail the exact mistake.
I developed an opening that I feel I can properly call Fried Liverpool. Like the Fried Liver Attack from chess, mentioned in a comment, it’s crazy sharp and can put on tremendous pressure. Steamhammer can’t play it yet; it needs a couple new features. I tried it by hand and found it is effective against unprepared opponents. Maybe I’ll get it working in time for version 2.2.1 or thereabouts (the one after the upcoming 2.2).
Steamhammer just lost a game against the cannon bot Jakub Trancik. I don’t remember another loss against Jakub Trancik since early last year (maybe I have a bad memory). During the tournament I can’t log in to fetch the game records, but I assume it is the first game against this opponent since version 2.0. It takes a long time to collect enough game records. I’m glad I fixed the proxy recognition bug, or Steamhammer might have lost the next game too.
Comments
Jay Scott on :
Dan on :
PurpleWave used to not pull workers to defend against proxies that far away. But I extended the range to answer BananaBrain proxying Gateways in my natural, and that has resulted in the weakness you see here.
I'm checking every day whether krasi0p's likely to face someone who can take it out -- fortunately, for the moment, that's Steamhammer.
Ironically, I worked on making CherryPi's cannon rush defense safe against late discovery (it doesn't pull workers for cannons in range of completed cannons, but does keep workers fighting cannons as cannons in range of them finish), but never ported that logic back to PurpleWave as I was working up to the deadline on trying to beat Locutus/BananaBrain more reliably. There's never enough time.
Barcode on :
Seems like cannonrushing is still a valid approach in 2018-2019 (happy new year btw!).
Jay Scott on :
Joseph Huang on :
Thomas on :
Jay Scott on :
Dan on :
Jay Scott on :
Jay Scott on :
Thomas on :
Jay Scott on :
tolmar on :
McRave on :
Jay Scott on :