Bot constantly pausing

[Lucain]

Ok so I left the bot running over night for the first time and was shocked to find that it had only completed 8 runs in the 4+ hours it was going. Checking the logs and I can see that it effectively got stuck doing something for 2+ hours

2014-03-13 02:54:41,202 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:42,298 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:43,302 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:44,335 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:45,400 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:46,467 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:47,500 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:48,567 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:49,600 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:50,666 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:51,696 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:52,699 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:53,732 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:54,767 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:55,800 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:56,802 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:57,869 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:58,901 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:54:59,967 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.
2014-03-13 02:55:01,034 [Main Bot Thread] DEBUG LokiPoe (null) - Pressing bound movement button.

This continues on for a while...
heres the complete log: View attachment 10620 2014-03-13 01.06.txt

So I ran it again shorlty after and watched it go, it seems to just pause up and sit there randomly. I ended up switching it off after watching it sit motionless for 5 mins which you'll see towards the end of this log: View attachment 5792 2014-03-13 07.20.txt

 

[pushedx]

What area were you botting in?

There's a setting you can use to control how long the bot stays in an instance, to try and help avoid this issue, as it does happen sometimes. Check the "Logout" tab in Settings. The default Max Instance Time is set to 30m, but if you know the bot shouldn't stay more than a much lower time, you can set it lower.

Other than that, there's not much else I think you can change. We're always working on trying to fix the little bugs like this, but due to the way the client works, they still can happen.

 

[Lucain]

It was botting docks, I've ran it in a few other areas without issue so it just seems to a problem with docks. I also had the max instance time set to 15 mins (now 10) but for some reason it didn't kick in as you'll see from the first log.

I've actually just switched off all looting of barrels and chests and its been running perfectly so I'm wondering if that might be it. Also is there some way of having it portal out of an instance at the end of max timer instead of logging out of the character?

 

[pushedx]

Ah, Docks is an area with known issues it seems. A lot of people don't have much luck botting there due to the way the areas are generated. There's not much we can change for now to make Docks perform better.

The bot should blacklist barrels and stuff it can't open, but it's possible it got stuck in a way that caused a long running loop so the bot didn't exit the instance when it should have. When we rewrite the movement stuff, we'll try to make sure that is enforced better.

There's no other option for now for not logging out when the bot is in the instance for too long. That was added a short term fix for the bot staying in the instance for too long, but there's several cases where trying to TP out wouldn't work, which is why only logout is supported. You can be sure the bot will reset with a logout whereas with a TP, it might remain stuck.