Corrupted area and exploration complete percent question

[roneo1]

For normal areas, I use the basic grind bot exploration complete percent in order to avoid wasted time for backtracking for the last unexplored part of the instance, however this also applies to corrupted areas apparently and the bot never kills the bosses because of it.

How can I make the corrupted areas be exempt from this rule, or any other way of having the bot complete corrupted areas while still keeping an exploration % threshold for non-corrupted areas?

 

[pushedx]

This will be changed in the next beta version. I didn't account for being in Corrupted Areas for the early exploration complete logic. The new behavior will be to never complete exploration early in corrupted areas.

 

[hansmeier]

Does it also open the Vaal Boxes when they are there? :x

Cause most of the time it just ignores them.

 

[roneo1]

This will be changed in the next beta version. I didn't account for being in Corrupted Areas for the early exploration complete logic. The new behavior will be to never complete exploration early in corrupted areas.

Is there any eta on this? Even with exploration set to 100% the bot doesn't kill the boss in corrupted areas most of the times, it just gets to it and tps out lol.

 

[TurboNerd]

Does it also open the Vaal Boxes when they are there? :x

Cause most of the time it just ignores them.

noticed a similar issue, watched mine clear the instance, including the boss, then leave the box unopened, verified it was not set to be ignored but i havn't seen it run another one yet to see if it was a 1 off thing or what.

 

[bcain1787]

This will be changed in the next beta version. I didn't account for being in Corrupted Areas for the early exploration complete logic. The new behavior will be to never complete exploration early in corrupted areas.

Great to hear I have been eagerly awaiting a fix for this thanks pushedx!

 

[hansmeier]

noticed a similar issue, watched mine clear the instance, including the boss, then leave the box unopened, verified it was not set to be ignored but i havn't seen it run another one yet to see if it was a 1 off thing or what.

Jeah, that exactly.