Unstable startup of HB, not attacking on more than one instance.

[kawaki]

Since a patch or a few patches befoure v2.5.6296.463 HB starts up well, on the first account, but if I starts up another one, it can't detect the other instances of wow, I have tried all kinda things, but it just feels more like luck if it works.

I assume you must have some code inplace to detect if another hb is running, and what instance of wow that is connected to, so we dont end up with well more bots connecting to the same instance, but can this core realy be that unstable? would gradly take a look at that part of the code, but i'm quite sure you won't hand that out ,but i assume you are using some inter app protocolle... maybe you are even just using the session thing online for this, and that would even make it harder to understand why its not working stable.

btw. not trying to sound like an ass, just want to find a solution thats permanent.

 

[kawaki]

Even just a clarefication of how the main login process works up untill the population of the wow instances drop down, would get a long way, to get an idea, where the problems might be.

If its all comming from the session(s), server(s) well then it might be a issue there, or on our route to that host from time to time.

 

[Tony]

are you ok now?

 

[kawaki]

are you ok now?

Well after I posted yesterday, I got two of 3 instances up and running, for a few hours, then closed down and when't to bed, now im trying again, and only one will connect, and finds wow instances to connect to.

So must answer "no" to your question, and its kinda sad, this is the first time I have had this problem in any of the development builds, I have been reading others had this problem, but never seen it my self, other than when I ran the client as 64bit, but then that was a quick fix by reading thrue the actual error message of HB =p

But am I correct in the assumption that the bot starts up, collects the pid's of the wow instances, sendt the license key + available pid's to the session server, and then the session server returns what pid's that are not already a HB connected to? Well just very crude explaination, cause it feels like this could be the problem, but I also understands why its done this way if im correct on my assumtions

 

[kawaki]

Ok I have tested a few things, and i can reproduce the error here:

I can get all 3 bots online if I follow the steps below:
1) Start wow - Log character in.
2) Start HB - it will auto connect.

3) Start new wow - Log character in.
4) Start HB - it will auto connect.

5) Start new wow - Log character in.
6) Start HB - it will auto connect.

If I then trys to close ALL HB's leave wow running on all 3 characters, checks BuddyAuth that no sessions are running.

And then Start 1 instance of HB, connect to an Instance of wow, that is fine, but the next HB i start WILL NOT, I REPEAT WILL NOT get to the Drop Down box for the other two instance of wow to connect to!

 

[kawaki]

To shorten it up alittle...

Working example: Start wow, login, start hb, start wow, login, start hb, start wow, login, start hb.

Not working: Start wow, login, Start wow, login, Start wow, login, Start HB (this is working), Start HB (this will fail), Start HB(this will also fail)

 

[yjkimmy]

I too have the same problem and like kawaki said, wow+hb works but wows+hb doesn't after recent patch.