"Instance manager didn't open!"

[j19]

I've died to this in hardcore a few times and I'm trying to figure out what could be causing it so I could avoid it in the future.
Here's the log before waking up in Lioneye's Watch in Standard:

2014-03-14 12:17:17,356 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-14 12:17:19,850 [Main Bot Thread] DEBUG Poi (null) - Cleared POI: AreaTransition
2014-03-14 12:17:19,850 [Main Bot Thread] DEBUG Poi (null) - POI set to Type: None, Location: {0, 0}, Distance: 0, Name: None, Hash Code: 823561111
2014-03-14 12:17:20,131 [Main Bot Thread] DEBUG Poi (null) - POI set to Type: AreaTransition, Location: {272, 281}, Distance: 37, Name: AreaTransition, Hash Code: 478585556
2014-03-14 12:17:21,739 [Main Bot Thread] DEBUG Navigator (null) - MoveToCoroutine moving to {272, 281}. Reason: Interacting with POI: AreaTransition
2014-03-14 12:17:21,739 [Main Bot Thread] DEBUG Navigator (null) - Navigation path index moved to 1
2014-03-14 12:17:21,819 [Main Bot Thread] DEBUG Navigator (null) - There's something under the mouse, extending the click distance to 20
2014-03-14 12:17:21,899 [Main Bot Thread] DEBUG Navigator (null) - There's something under the mouse, extending the click distance to 25
2014-03-14 12:17:21,901 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-14 12:17:22,200 [Main Bot Thread] DEBUG Navigator (null) - There's something under the mouse, extending the click distance to 20
2014-03-14 12:17:22,288 [Main Bot Thread] DEBUG Navigator (null) - There's something under the mouse, extending the click distance to 25
2014-03-14 12:17:22,289 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-14 12:17:22,626 [Main Bot Thread] DEBUG Navigator (null) - There's something under the mouse, extending the click distance to 20
2014-03-14 12:17:22,716 [Main Bot Thread] DEBUG Navigator (null) - There's something under the mouse, extending the click distance to 25
2014-03-14 12:17:30,515 [Main Bot Thread] DEBUG BotMain (null) - Stopping the bot. Reason: Instance manager didn't open! Something has gone terribly wrong here...
2014-03-14 12:17:30,516 [Main Bot Thread] DEBUG TreeHooks (null) - Removed hook [BotBehavior] 4b563ae0-571a-4a2b-9cd1-b8f442ea2cf5
2014-03-14 12:17:30,516 [Main Bot Thread] DEBUG Poi (null) - Cleared POI: AreaTransition
2014-03-14 12:17:30,518 [Main Bot Thread] DEBUG Poi (null) - POI set to Type: None, Location: {0, 0}, Distance: 0, Name: None, Hash Code: 159064661
2014-03-14 12:17:30,519 [Main Bot Thread] DEBUG BotMain (null) - Removing memory patches.

"Stopping the bot. Reason: Instance manager didn't open! Something has gone terribly wrong here...".
This is in the transition area for the Ledge (the Climb).
No errors were reported.
What could be causing the stop and these deaths?

EDIT:
Also, am I correct in think that this is what happens: The bot can't open the instance manager for some reason when wanting to create a new ledge. After failing for a while the bot gives up and shuts down. Eventually some lone skeleton walks up and beats our hero to death with a stick.
If so, is it possible to force the bot to chicken out / alt-f4 before stopping?

Thanks for any assistance!

 

[pushedx]

I think it would indeed be a better idea to logout rather than stop the bot and leave it where it's at if it fails to interact with the area transition properly. This set of logic is pretty old, and at the time, it made sense to just stop the bot.

The next bot version contains a change already that might help prevent this, but it's still a weird case when it messes up. I think it's just because of the input/movement logic not working correctly. A lot of the bugs the bot has is related to that currently. I'll change that logic to logout though, since we probably shouldn't just leave the bot stopped in an instance in any event. There might be a few other places in the bot where Stop is called, but we'll have to go through and just check them out.

I've done 100s of Ledge runs though, for testing the area to area logic when I added it, but I've never been able to reproduce this specific issue. I think the map generation RNG is to blame for that.

 

[j19]

Sounds like a good solution. Thanks for the quick response!

 

[zaizaiwang]

I think it would indeed be a better idea to logout rather than stop the bot and leave it where it's at if it fails to interact with the area transition properly. This set of logic is pretty old, and at the time, it made sense to just stop the bot.

The next bot version contains a change already that might help prevent this, but it's still a weird case when it messes up. I think it's just because of the input/movement logic not working correctly. A lot of the bugs the bot has is related to that currently. I'll change that logic to logout though, since we probably shouldn't just leave the bot stopped in an instance in any event. There might be a few other places in the bot where Stop is called, but we'll have to go through and just check them out.

I've done 100s of Ledge runs though, for testing the area to area logic when I added it, but I've never been able to reproduce this specific issue. I think the map generation RNG is to blame for that.

yes ,,i think so!!!!!!