View attachment 143934
Bot did A4 and A3 run, found key, then proceeded to act 1. After running around for about 10-20 seconds logged that Run is finished and left game. I'm guessing this is the part where it tries to keep key count close to each other, but why start another act instead of compiling key count and leaving after 4+3 were done? good chance of dying when trying to take portal to town surrounded by enemies.
Second run he did the same thing, this time it went to act 1, actually found keywarden very quickly, and once again stated run is finished and left game. I stopped the bot before it left and killed the keywarden.
<!-- Balance key counts by skipping act with highest key count -->
<When condition="HighestKeyCountId == 364697" immediate="true">
<UseStop id="A4" />
</When>
<When condition="HighestKeyCountId == 364696" immediate="true">
<UseStop id="A3" />
</When>
<When condition="HighestKeyCountId == 364695" immediate="true">
<UseStop id="A2" />
</When>
<When condition="HighestKeyCountId == 364694" immediate="true">
<UseStop id="A1" />
</When>
is this zerg ran?
This is the version I have modified.
View attachment 144093
It is working for me pretty good. I use Demon hunter sentry build.
Owner will certainly modify the main one.
you can set your trinity misc combat setting by making trash mob max.is this zerg ran?