stuck

[54sgdg4d6s]

Exilebuddy 9608 2014-07-20 01.46.txt
2014-07-19 20:14:18,473 [43] DEBUG HandleDangerousArea (null) - [ShouldExplore] MapItemDropQuantityPosPct => 16
2014-07-19 20:14:18,474 [43] DEBUG HandleDangerousArea (null) - [ShouldExplore] MapMonstersPoisonOnHit => 1

 

[54sgdg4d6s]

conflict between take_corrupted_area and explore

 

[pushedx]

Was there an object blocking the "Restricted Gallery" area transition in the Library? Or what was the bot doing, just running back and forth?

 

[54sgdg4d6s]

just running back and forth

yea. Send additional video for u.

 

[54sgdg4d6s]

start 08:19:02
Exilebuddy 13212 2014-07-20 11.16.txt

Possible to do runtime limit like b4 ?

 

[pushedx]

Yes, I'll add a plugin for the runtime limit and integration into Exilebuddybot soon.

The actual problem is the old explorer. It's the only reason why the bot still does that, but it is going to be replaced.

 

[54sgdg4d6s]

Can u do additional timer, if bot dont change poi for 10 min relogin character?

 

[pushedx]

Can u do additional timer, if bot dont change poi for 10 min relogin character?

That sounds doable. That way, it can also detect if it's switching POIs back and forth for too long as well, I think. I'll add that to the todo list for this week.

 

[54sgdg4d6s]

View attachment 136441
2014-07-23 16:54:11,337
View attachment 136442
2014-07-23 15:47:07,198 2014-07-23 16:47:02,387
still stucking

 

[54sgdg4d6s]

View attachment 136460 one more log
2014-07-23 22:39:58,782

What about runtimer?

 

[pushedx]

View attachment 136460 one more log
2014-07-23 22:39:58,782

What about runtimer?

What I did for the StuckDetection plugin is simply make it log info about various cases. It doesn't actually do anything yet when a stuck is encountered.

You can change the plugin to actually do something, such as logout by making a few simple additions.

Near the bottom of the StuckDetection.cs file, you'll see this code:

            Log.DebugFormat("TimeInInstance: {0}", AreaStateCache.Current.TimeInInstance);
            if (!LokiPoe.Me.IsInTown && AreaStateCache.Current.TimeInInstance.TotalMinutes > 10)
            {
                Log.InfoFormat("[PoiManagerOnOnMetricsComplete] We have been in the current instance for too long.");

                // TODO //
            }

To logout when the timer is reached, all you have add is: LokiPoe.Gui.Logout();

above the // TODO // line and your plugin will now logout when it's in the instance for too long.

The plan is to add some options and configuration to the StuckDetection plugin, but this first release was just to test the logging info.

 

[54sgdg4d6s]

Like

            Log.DebugFormat("TimeInInstance: {0}", AreaStateCache.Current.TimeInInstance);
            if (!LokiPoe.Me.IsInTown && AreaStateCache.Current.TimeInInstance.TotalMinutes > 10)
            {
                Log.InfoFormat("[PoiManagerOnOnMetricsComplete] We have been in the current instance for too long.");
		LokiPoe.Gui.Logout();
                // TODO //
            }

?

Possible to do trigger of "Complete Exploration" button?

 

[pushedx]

Yea that should work fine.

If you want to Complete Exploration instead, all you need to do is call: Explorer.Complete();

If you need a namespace for that, it's: using Loki.Bot.Logic.Bots.ExilebuddyBot.Exploration;

 

[54sgdg4d6s]

thank you, works well !

 

[pushedx]

StuckDetection now has configurable settings for various things.