search

bsaffel / benchmarker

macro trainer | build optimizer | practice tool
10 stars 0 forks source link

Cursor did not update correctly after failed step #311

Closed bsaffel closed 9 years ago

bsaffel commented 9 years ago

Therefore, a later failed step (Zergling Speed) did not actually fail the build.

screenshot2014-10-19 23_36_50

bsaffel commented 9 years ago

At first the 2x Overlord failed because of a timer expiration. Then it failed because of Zergling speed. Then it failed because of 3rd Hatchery. All updated the same failed step.

bsaffel commented 9 years ago

screenshot2014-10-19 23_59_19

It appears as though the logic is failing because it thinks a current or previous step has not been satisfied.

bsaffel commented 9 years ago

Best guess is that the build order offset is being updated in the cycle method before the cursor is being updated. Probably need to nest the cursor update before the offset is incremented.