Any ETA on a relog feature in HB?

Obviously would be nice and I am sure the devs are working hard to get something like this done.
Though I must point out the only dc I have had is maintenance

 

Have a friend with same exact problem, he keeps asking me to leave my pc on botting both accs ><

pt?

 

What do you devs think about this?

 

I think in Devs opinion there are other priorities - wich is bad because they really should take a couple minutes / recruit one more person to help with development.

We need a relogger cause most of us get random DCs, and don't point your fingers at our crappy connections, a relogger is a MUST.

 

This is a stupid idea great way to get your account stolen...

You should all have authenticators anyways and the bot can't login with that.

What happens if servers are taken down and your bot tries to login 1000 times? Blizz probably has a record of that and would ban you.

 

lol...(filler)

 

http://blog.kynox.org/?p=151

wut?

 

Stay on topic please.
Only reply if you think a relog feature is required! Don't flame others for having a bad connection or saying this is a bad idea; just don't use the feature when it eventually gets implemented.

 

A relogger wuld be really nice i really hope it soon will come to us we are in very very bad need of a relogger ^^

 

as long as you dont go to stupid sites or download things from stupid sites on your botting computer then your botting accounts will be just fine unless there is a neighbor hacking your wifi and then hacking your accts.

i dont use authenticators b/c it can be banned the same day as it hits 80 ... or 10 years down the road, who knows

 

I relog feature is really REALLY necessary! I don't care if my bot wastes a loot or goes a tad slower because of a minor bug, but if i loose an entire night of botting because it get DCed 2 minutes after I went to bed, then it sucks! I hate babysitting my bot...

 

Still waiting for a relog feature or a separate relogger =/

 

if you all cant wait , simply code yourself one..

 

BUMP-de-bumpy-boo!

 

I'm refreshing my C++ atm.
Probably end up coding a multi-relogger myself.

0. It will login all your sessions of GB/HB. Much like SY relog.
1. It will ping Google.com to check if you lost connection every X amount of seconds.
2. If the ping is negative it will close all running HB/GB sessions and WoWs.
3. It will also check if the WoWs specified are 'locked' processes (a.k.a. crashed).
4. It wil then start over and launch all sessions again.

I hope some of you want to contribute to this.

The things I'm still puzzling about is :
- checking wether a proces is locked or not
- logging in HB/GB and telling it to start

 

Telling HB/GB to start seems to be the easier part, since u can pretty much start it and TAB yourself X amount of times and hit enter... it would need 2 modes, 1 for the big version and one for the small version, or just make it require the small version and call it a day. Since the small version can actually login and start on same button.

 

I don't want to hardcode it actually. There should be a way to do it in the background.

 

Would be cool if you could do it the Glider way, using a socket type connection to the bot. Say HB implements it, you could for example access 127.0.0.1 on port 5100 and send packets to it, such as one requesting current status (the lil state text on the bottom, such as "Moving to next hotspot", etc) and have it returned to you, if none was returned in a timeout time then bot was crashed or connection wasnt configured properly. Restart it and wow. Send a packet asking, am i connected to wow? What process am i connected? What is the characters current XP level, etc,etc, etc.

And also, commands like, LOGIN, START, STOP, LOADPROFILE, LOADMESH, etc...

And if truthful with the glider way, only reply if you send a packet with a login password for accessing the bots functions, so that not just any program could connect to it and gather information about it.

But then again, this would need for them to actually introduze that to the bot... not that it is hard to do, depending on the way they structured the access to the functions inside it, it would take them a day or a week to put an effective system like this working for us.


Not only good for reloggers, it is good for other stuff too such as remote control and monitorization. And would also work for eStat type program, not that you need one since eStat already exists.

 

I've decided to just make it in AutoIt.
It's easy to do this basic stuff in it.

So far I've implemented it that it starts up all WoW's and logs them in and it checks whether it can Ping google before it does that.
It pings Google 10 times and if it scores less than 3 it will restart from scratch and relog.

 

pinging google is a poor way to go about it.. my wow d/cs all the time while im running hb and it's not my internet going out.