Fix vacatePos & Fix autoRun() #183
Fix vacatePos & Fix autoRun() #183dev-bittlinger wants to merge 1 commit intobencbartlett:devfrom dev-bittlinger:dev
Conversation
…ead of continue) - causing a role to stop working in a colony if one creep of it's sort is spawning
|
according to so it is used to override blockMovement this is used correctly in goTo: here, the default force is false, meaning, just accept blockMomement, to use the same logic for .move(), then it should be what do u think? |
|
I mean, that's just another way of doing the same thing. We can check for the error first, of course. Because: is the same as: |
Bugfixes
Description:
There was a logic error in the AnyZerg move() method, causing the issue in Movement.vacatePos().
The method vacatePos() sets creep.blockMovement to true, but is meant to override it with force: true. The check in AnyZerg said "!this.blockMovement && !force" Therefore this method was not working, and the creep not moving. Swapped it to "!this.blockMovement || force".
Also fixed an issue where Zergs of a role would stop working if one of their kind was spawning, there was a return instead of an continue, aborting any Zerg actions after it.
Fixed:
Testing checklist:
tsconfigconfiguration