Is anyone's Arelog working as it used to / as it should be working?

[Retsalk]

Hey everyone,

Since a few weeks ago (2 last weeks of MoP until today) my arelog has been giving me the same message from time to time:

[PID: {0}] The bot has sent an exit code to no longer run. Terminating monitor.

[PID: 4180] Terminating monitor on request.

Then it stops, quits WoW and won't relog a damn thing. Isn't that what it's supposed to do as a 'relogger'?

I am wondering, I did fresh installs of WoW, fresh installs of Honorbuddy and fresh installs of Arelog, formatted my pc twice in the meantime and it keeps throwing me off. Does anyone know what to do about it? I am sure it's not intended.

3500+ queue, here I come again!

 

[Tarathiel2]

Use the support section and include a log from the bot itself.

 

[Retsalk]

I am asking if more people have this problem, not yet for a solution mate

 

[Tarathiel2]

Does anyone know what to do about it?

Sounds to me you're asking for a solution.

 

[Naroha]

Nope, working fine for me since I started using it, botting 24/7 with arelog and not a single problem so far

 

[trashmob]

Similar problem here

[18:17:47:165] [PID: 6412] The bot has sent InactivityDetector exit code and will no longer be ran.
[18:17:49:415] [PID: 6412] Terminating monitor on request.

 

[Kaelhoel]

ARelog is working fine for me, and has been for a good while now. Hope you work it out.