Authentication issues - something has to be done

[RayVanHalen]

Everyone is aware of "Authentication failed!" issues occurring after relogs, but for most people it's just a nuisance. For me, it makes my whole damn life hell.

I have multiple bots that use the following looped schedule:

Log on character A, do things - 15 minutes
Log on character B, do things - 15 minutes
Log on character C, do things - 15 minutes

With an one session key, after A logs off, authentication fails for about five minutes. When character B finally gets in, the schedule gets messed up, since he only gets 10 minutes out of intended 15. Same happens for character C (and A as well when the cycle is repeated). If I leave the schedule as it is, everything goes to goddamn hell, before the task those characters are supposed to get done in 15 minutes can't be done in 10. If I extend each of their uptimes by 5 minutes, I lose quite some efficiency for no good reason. At this moment of time, I am forced to use three session keys for each of these bots to keep things going the way they need to be.

I am well aware of the fact that I am able to kill sessions on Buddyauth, but this is not a solution as I am not monitoring my bots enough to prevent the problem from happening. I believe there is absolutely no reason to keep the things the way they are - the system is flawed and needs a change. Even such a simple solution as (optional via Buddyauth) auto-killing current session in case if another login is being attempted would solve my and everyone else's problems. Seeing as absolutely no improvement had been done in this direction over the course of last years, I can't help but wonder why.

 

[braatenj]

Everyone is aware of "Authentication failed!" issues occurring after relogs, but for most people it's just a nuisance. For me, it makes my whole damn life hell.

I have multiple bots that use the following looped schedule:

Log on character A, do things - 15 minutes
Log on character B, do things - 15 minutes
Log on character C, do things - 15 minutes

With an one session key, after A logs off, authentication fails for about five minutes. When character B finally gets in, the schedule gets messed up, since he only gets 10 minutes out of intended 15. Same happens for character C (and A as well when the cycle is repeated). If I leave the schedule as it is, everything goes to goddamn hell, before the task those characters are supposed to get done in 15 minutes can't be done in 10. If I extend each of their uptimes by 5 minutes, I lose quite some efficiency for no good reason. At this moment of time, I am forced to use three session keys for each of these bots to keep things going the way they need to be.

I am well aware of the fact that I am able to kill sessions on Buddyauth, but this is not a solution as I am not monitoring my bots enough to prevent the problem from happening. I believe there is absolutely no reason to keep the things the way they are - the system is flawed and needs a change. Even such a simple solution as (optional via Buddyauth) auto-killing current session in case if another login is being attempted would solve my and everyone else's problems. Seeing as absolutely no improvement had been done in this direction over the course of last years, I can't help but wonder why.

This really isn't an issue with HB. Its with the relogger forcing HB to close instead of allowing it to close properly and correctly end the session. The method you propose is not really a good option for everyone because for instance in my case (and i presume, many others) I use 3 session keys to run 3 separate accounts and if one of my HB's gets closed due to being stuck to long or something of that nature, then when it restarts HB its going to end up kicking off one of my other 2 accounts... and then it will cascade because that account will force HB to restart and so on and so forth...

What really would help the most is if there was a way for the relogger to close down HB appropriately allowing it to terminate its session and not having to wait for it to timeout.

 

[RayVanHalen]

This really isn't an issue with HB. Its with the relogger forcing HB to close instead of allowing it to close properly and correctly end the session.

Well, I did experience this issue even when I was restarting HB manually. The issue is occurring with both ARelog and HBRelog, so I don't see any way out of the infinite loop of "Max sessions!". Although, I don't honestly understand why do they need to force killing both WoW and HB the way they do, especially since there's no option for soft exit.

The solution I have proposed was just something off the top of my head, since I have absolutely no idea about authentication servers' mechanisms so whatever I'd have suggested might not be adequate due to technical reasons. Nonetheless, I do believe that there has room for so much needed improvement.

 

[soulravager]

Well, I did experience this issue even when I was restarting HB manually. The issue is occurring with both ARelog and HBRelog, so I don't see any way out of the infinite loop of "Max sessions!". Although, I don't honestly understand why do they need to force killing both WoW and HB the way they do, especially since there's no option for soft exit.

The solution I have proposed was just something off the top of my head, since I have absolutely no idea about authentication servers' mechanisms so whatever I'd have suggested might not be adequate due to technical reasons. Nonetheless, I do believe that there has room for so much needed improvement.

If you give HB like 1 minute it'll see the session is dead and will remove 1 session used, if you restart it too fast it will say max sessions until next update check

 

[Tony]

for those with problems,use support issues section including your log

closed