Too far away to click portal

[Kilgore]

Every dozen or so runs, my cyclone using character casts a portal while desynced and then the character syncs up and is too far from the portal to click it. At least I think that's what's happening. I return to the computer to find a bit of distance between the portal and my character and the following text in the bot window:

We have finished full exploration in this area. Stopping the run!
Cleared POI: Explore
POI set to Type: None, Location: {0, 0}, Distance: 1277, Name: None, Hash Code: -190085533
POI set to Type: PortalToTown, Location: {0, 0}, Distance: 1277, Name: PortalToTown, Hash Code: -346316918
Opening a portal home, using the Portal ability!
Taking portal back home!
MoveToCoroutine moving to {332, 1245}. Reason: Interaction
Movement cancelled, cancellation callback returned true.
GetInRangeOfAndStop returned a value of type Loki.Bot.Navigation.MoveResult
Error: OutsideClientSpace
Stopping the bot. Reason: Failed to interact with target.
Removed hook [BotBehavior] dd16e5d3-91c9-4549-a638-cb22785ca994
Cleared POI: PortalToTown
POI set to Type: None, Location: {0, 0}, Distance: 1277, Name: None, Hash Code: -849771924
Removing memory patches.


If you can come up with a nifty fix for this situation, that would be dandy.
THX

 

[pushedx]

Thanks for reporting, we'll have to change up some of the logic to handle this better. Based on what we're seeing, we need to go through and adjust quite a few similar issues with the logic to recover from errors better.

It used to do this more often, but then we made it stop before casting and it (should have) fixed it.

However, the way we have the logic setup right now, it's not re-evaluating things to recover like it used to (behavior trees), but rather following the function logic through (via coroutines).

Right now, it tries to interact, fails, and stops the bot, whereas it should fail, we handle the error, and try to recover.

 

[imdivesmaintank]

I just had this happen, but for a different reason. It cast the portal, then ran off to attack a mob, and when the mob was dead it tried interacting with the portal, which was half a screen away.

 

[Kilgore]

I had a similar thing happen. I've ditched the portal gem, because I have less problems using scrolls. But last night, the bot cast--attacked a mob---cast--attacked a mob--cast again. If this kept up, I could run out of scrolls fairly quickly.

 

[pushedx]

I've seen that once or twice before, and I think the logic we want to rewrite should address it.

Basically, the bot thinks it's done, something else comes into view that might have been blacklisted or inactive previously, then the logic gets incorrectly re-executed. We have a short range portal check, which could be larger to counter the bot getting dragged past it to do other things, so that's something we'll check into as well.