BigSister - A Gatherbuddy / Honorbuddy Restarter and Relogger - Beta Phase

Thanks for the new version

 

Yes it will load the current wtf, and modify some settings in it.

 

Hey, just downloaded the newest version and this is what I got

 

Did you update your settings?

 

Have newest version, entered all my settings and get this spammed over and over.

 

The only thing that im still having problems is with is changing realm lets say i have 3 Characters on realm X and 1 Character on realm Y, it will log in on realm X for character Y

 

3/7/2010 12:29:24 PM Are you running BigSister as admin?
3/7/2010 12:29:24 PM Admin check returns :True
3/7/2010 12:29:24 PM No suitable thread was found for Babysitting, yet Watching = True
3/7/2010 12:29:24 PM Beeing a good sister and hanging up the phone to watch the kids
3/7/2010 12:29:24 PM BabySitting Pally
3/7/2010 12:29:24 PM killAndRestartWowAndBot requested
3/7/2010 12:29:24 PM KillWowAndBot requested
3/7/2010 12:29:24 PM StartFreshWowAndBotSequence requested
3/7/2010 12:29:24 PM Error Starting wow:System.ArgumentException: String cannot be of zero length.
Parameter name: oldValue ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 819, offset:446
--- End of inner exception stack trace ---
at MultiRelogger.BabySitter.(String , String , String )
at MultiRelogger.BabySitter.()
3/7/2010 12:29:24 PM Exception in FSM Do(): System.Threading.ThreadAbortException: Thread was being aborted. ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 810, offset:573
--- End of inner exception stack trace ---
at MultiRelogger.BabySitter.()
at MultiRelogger.BabySitter.()
3/7/2010 12:29:24 PM Error in Watch loopSystem.Threading.ThreadAbortException: Thread was being aborted. ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 809, offset:429 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 808, offset:105 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 807, offset:65
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at MultiRelogger.BabySitter.()
at MultiRelogger.BabySitter.()

 

Is it possible to add some sort of delay between starting them because well gatherbuddy works fine but my honorbuddy goes mental if it goes too fast (switching profiles all the sudden, saying my login wasnt correct)

 

Hmm it shouldnt Oo, settings correct?

 

Starting them? The individual members of the list? It will start them 1 by 1, waiting for each one.

What you mean by changing profiles? Everything should be already setup prior to making the relogger start work.

If you use the same honorbuddy files for all your bots, well you shouldnt. Make 1 separate folder for each, that way, all settings are saved for each one. And since HB isnt that big, its no problem, wow is another history.

 

I ment like when 2 crash (wich happend earlier) it started 2 wow clients at the same time, meaning the honorbuddys started afterwards dindt know wich client they to had connect to

*typo*

 

Haa, ok, nice find, will work on that.

 

After setting up my profile information, I am unable to get BigSister to start, because the admin check keeps returning false, despite me being on my computer's only user account (the admin..) I am running Windows 7, and all of my path files are within the administrator account, not public.

 

Try right-clicking and click "run as admin". If it doesnt help check your user wateva thing protection windows has, and turn it off.

 

right click - run as admin worked. Thanks =)

 

guys i'm getting a problem, when i start the BigSister, he does everything ok likke logging into wow getting inside my character but then he starts HB and he dosen't do the login and he asume that he has done it allready..

 

@ MrBig

I know I'm not using the latest version. I use the version before with the \wow.exe\wow.exe bug - but i fixed it in the setting and everything works fine.

The only bug i'm expieriencing is: If i get disconnected (with 2 chars) the bot kills all Buddys and WOW windows. After that he the ssecond WOW to fast. So beforce the first Buddy (honorbuddy) is open, there are 2 WOW Processes - which means that my buddys hang in SELECT PROCESS ID.

Just 10 Seconds delay between FIRST BOT started and SECOND WOW starting and it would be fixed.

thank you for this great relogger!

 

At the moment, theres no delay as to start the processes. They will run as fast as the computer is able to. Except for the first startup that I manually gave it a sequencial startup order. And then each babysitter knows what she must do, and will do it, regardless of any commands you put on the bigsister main window. Except for kill methods ofc.

So, atm that isnt supported, I must add a system to "sync" them, so all know about each other and can agree on a startup order. I started working on that in the early days, before the keyboard emulation feature. Stop working on it because keyboard emulation would allow me to start all bots at same exact time. Now I see that the feature is needed because HB/GB will pop-up a selection screen and bigsister isnt programmed to handle that yet.

I will also work on having some sort of mecanism to syncronize the babysitters or work on auto-selecting the right process.

Stay tuned.

 

Normally it assumes that it started already for HB big only, but since HB big isnt completely supported at the moment, i suggest you try and use HB small.

If you were using HB small, then make sure that it isnt minimized and that the "Bot log" is showing up all the bot information properly. Reason why it assumes that it is already logged in, its because he cannot find the right buttons to push. While this might be a bug in bigsister itself, it can very well be some sort of client-side error or wrong settings. Please make sure your settings are correct and that other functionality is actually working.

If everything else is fine, please send me a log and explain me in detail what you do after you start bigsister (even stupid stuff, sometimes they are important to find the problem).

 

sounds good. Everything works very well for me.. but with 2 bots + 1 disconnect everythink is fucked up