Break handler isn’t working on mirror mode. Bot just doesnt take breaks as if breaks are disabled.

I've found this happen to me on the odd occasion, best options are to restart both the OSRS client and OSBot - That generally works for me.

Okay will do, thanks.

3 hours ago, UncleHard said:

Okay will do, thanks.

Does it work when you restart? 

2 hours ago, Aguero said:

Does it work when you restart? 

No.

When it does take breaks it will say the remember username option is enabled and shut down when it isnt. 

I have the same problem. Sometimes it breaks and sometimes it doesnt its like 50/50

@Patrick

Could you please take a look at this? It really sucks not being able to take automated breaks

4 hours ago, Maxlaxen said:

@Patrick

Could you please take a look at this? It really sucks not being able to take automated breaks

Hmm I don't really see why it wouldn't work on mirror, but maybe I can debug it

3 hours ago, Patrick said:

Hmm I don't really see why it wouldn't work on mirror, but maybe I can debug it

I don't know much about programming, but I've been talking to FrostBug about some bugs when using FrostBarrows. When the bot is about to loot the chest it can get stuck between "looting chest/in combat". And as I understood it, the MessageListener is bugging alot, and it affects the login handler/break handler too. That may be the reason it usually works, but it can get bugged. Correct me if im wrong @FrostBug

19 hours ago, Maxlaxen said:

I don't know much about programming, but I've been talking to FrostBug about some bugs when using FrostBarrows. When the bot is about to loot the chest it can get stuck between "looting chest/in combat". And as I understood it, the MessageListener is bugging alot, and it affects the login handler/break handler too. That may be the reason it usually works, but it can get bugged. Correct me if im wrong @FrostBug

What I've observed is that any error thrown in or by any listener or eventhandler will cause all listeners and event handlers to be disabled until client restart. Though supposedly Zach fixed this in a listener/eventhandler stability update a few client versions back.
Would be worth verifying, though.

@Patrick