Random Dungeon / Different elevations or wall / Exit Problem

[zippysticks]

Every time I see an exit like this, the bot goes "derp mode" and keep trying to exit because it thinks it is done exploring due to it found the exithash already, even though the exit is on the other side. Any solutions/fixes to blacklist impassable terrain?

 

[Tony]

thx for reporting

 

[zippysticks]

Is a fix currently being worked on? I'm currently trying to knock out bugs for a fully AFK ACT1 profile. I don't want to implement a workaround and tweak out boxSize and boxTolerance for it not to detect the exithash in that scenario (it makes it almost run everywhere). Or should I leave it the way it is and future versions will fix and ignore something like that from happening (detecting exithash when it's on different elevations/other side of walls (not route-able))?

I have a checklist of bugs/fixes and this one gets on my nerves the most due to multiple random dungeons exist and the scenario can happen multiple times.