max sessons

[jds]

There is currently a bug in honorbuddy that is causing the sessions to not be released when you exit. It started yesterday for me. When you close it, or even stop and close it, its not releasing the session. For people like me with a single session we have to login to buddyauth and kill the session to be able to switch characters. Normally this is not necessary.

The message you get when you try to login is: Honorbuddy v2.5.13042.771 started.
Logging in...

Max Sessions
Will try to login again in 30 seconds.


Note, this happens anytime you close it now, whether you intend to switch toons or not, just closing it and trying to load it again will result in this error. The session simply does not close when you close honorbuddy.

When I tried to report this to the support email as I've seen suggested here, I was told to post it here with an attachment of the log. The problem is that this is happening to a lot of people recently and if the team on this read these forums they should be aware of this, however it continues to happen.

Might I suggest a change to how this max sessions things work. How about if I pay for a single session and I logout and it doesn't get killed, you kill it when I login? I don't understand why this isn't the way it is now. It would go something like this:

Logging in, you have a single session which appears to be in use, killing it now... Logging in now

If you pay for more than a single session?

Logging in, you appear to have 3 sessions available, one is in use, using session 2 now. You have one more available. And if it's maxed?

Logging in now, you have 3 sessions available but they are all in use, killing the first session now.

At the very least all of this should be an option that one could enable in their settings.

While having the option to kill a session is nice, its cumbersome when you constantly have to do it because HB locks up, or you need to switch toons. Because it takes a lot longer than a minute for the session to disconnect, contrary to what has been suggested as I have seen here.

You will find two logs attached, one that shows a working session, and the other with what happens when you try to connect after closing it.

 

[Tony]

what you are describing its a normal behavior

 

[jds]

what you are describing its a normal behavior

It's not normal behavior, this behavior just started. Normally I can close HB and restart it without issue. If the normal behavior has been changed so that anytime you close HB or it is closed that it locks the session so it must be unlocked manually then that is bad design and needs to be addressed. And since everyone is complaining about this issue recently, I am going to suggest it is in fact NOT normal behavior. The normal behavior is that when I close HB, it should disconnect and unlock the session, so when I load it, it works without issue.

 

[jds]

Also I feel like I have to take the time to address this. Either this is now intentional which would be the dumbest move ever, or incompetence on the part of the people looking into this. I have now seen dozens of these threads all complaining about the same issue, and the replies are always the same. Kill the session in BuddyAuth.

All of us already know this. We have been doing this. But before this started becoming an issue, the only time you had to manually kill a session in buddyauth was when HB locked up and you had to manually kill the process in Task Manager. That is not the issue. The issue is when you close HB normally like you have done a hundred times before, it would normally restart without a problem. Now it will not close the session when it is closed. This needs to be addressed as a real issue, instead of support coming here and just telling people to manually kill the session. This should only be used as a last resort.

In what world is the normal course of action to support any feature one in which in order to use it, you must exit the application you are using and go elsewhere to fix it? You cannot tell me that it is a feature that HB does not close the session when it is closed, if it has always done that, and that the only way to fix this is to use buddyauth? Really you have designed a standalone application that will not work as a standalone application without first confirming in another application that it can first work?

Acknowledging you have a problem is the first step, and until you do then this will continue to be a problem, and people will continue to complain about it.

If this was purposefully designed this way, you are going to get a lot of complaints and people asking for refunds I'm sure. I use one bot and two toons and it is a HUGE hassle, I cannot imagine the people with 10 toons or something. I mean seriously? Fix the issue.

 

[Tony]

kill your session in buddyauth.com for now,we will check it