Working Relogger?

[Siiig]

Hey Forum,

HBRelog and ARelog both are causing me problems.

ARelog consistently closes WoW after a handful of minutes with the following:

[3:06:48 PM:950] [PID: 6084] Starting buddy
[3:50:05 PM:257] [PID: {0}] The bot has sent an exit code to no longer run. Terminating monitor.
[3:50:07 PM:701] [PID: 6084] Terminating monitor on request.
[3:50:07 PM:701] All monitors are terminated.

HBRelog does the same thing, but I don't have an error code for it.


Is anyone else having trouble with this? I've used HBRelog in the past, and had it run for days on end, but now both of the reloggers are causing me nothing but trouble. It actually seems like I'd be better off running without a relogger.

 

[PePPeRmix]

u didnt see?
[3:50:05 PM:257] [PID: {0}] The bot has sent an exit code to no longer run. Terminating monitor.
ARelog works well, change config of ur HB...
Without HB log nobody can help.

 

[Siiig]

u didnt see?
[3:50:05 PM:257] [PID: {0}] The bot has sent an exit code to no longer run. Terminating monitor.
ARelog works well, change config of ur HB...
Without HB log nobody can help.

You were definitely right in this case, the bot sent an inactivity time out. But I've found when that happens a huge part of the time, restarting HB will fix the issue (profile getting stuck, and restarting fixes it, that kind of thing).

If the bot shuts down for a valid reason, I would still expect the relogger to log back in?

 

[frosticus]

if your bot shuts down for many reasons. sometimes its a settings, or profile issue. restarting hb won't fix every single issue.

if the bot is shutting down for a legit reason, not because its just afk, then the logger cant fix the issue.