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

New version up, hopefully fixed the last bot activity bug.

More information please.

 

seems the bugs are fixed - cool mate! will let in run until tomorrow morning (which is in about 8 hours)

 

Mines spamming "Failed to write log, unlock the log.txt"

 

Did you unlock it?

A file lock can be caused by a number of things, such as you having notepad open with it. Did you check if you are running BigSister as admin? Maybe limited writting rights can cause that.

 

My mind reading skills are kinda rusty, but maybe check your settings, do you have wow path with 2x"\wow.exe" ?

That is caused by using old settings, I will add an extra check on future versions to help reduce this problem

 

Edit: just saw the above post, had wow.exe in there twice.

Hey MrBig, currently getting spam of:
"Exception: "

Settings are as follows:
alias: ski
Realm Name: (Correct)
Realm Region: US
WoW Path: C:\Users\Public\Games\World of Warcraft\Wow.exe\WoW.exe (Just noticed this, this post is now meaningless).
Bot Path: C:\hb1245\hb.exe (confirmed location)
WoW Name: Wow (default, not sure what this should be)
Bot Name: hb.exe (again, not sure what this should be)
MultiAcc: Checked, tried 0 and 1 (first account in list)
Char Index: 7 (confirmed)
Bot Type: HB Small
WoW Account: (Correct)
WoW Password: (Correct)

Profile saved and reloaded, upon hitting Start, log spams with "Exception:" and another message that I cannot see.

Screenshot:

 

Updated to the above: Upon removing the second WoW.exe, it re-adds it. Set path to just "C:\Users\Public\Games\World of Warcraft\" and it only adds it once, however the "Exception:" still occurs.

 

"Exception:" shows up in program, but it will show itself correctly in the log.

Will upload a new version with a review on the settings form, to see if that bug is fixed.

 

i had the same at first but when i deleted wow.exe and the gb.exe it worked.

 

New Version up, should fix any problems with old settings.

 

Another version is up.

Should fix some odd cases by looking deeper than settings form.

Also alot more elegant and maintainable solution.

 

3/6/2010 7:07:12 PM killAndRestartWowAndBot requested
3/6/2010 7:07:12 PM KillWowAndBot requested
3/6/2010 7:07:12 PM StartFreshWowAndBotSequence requested
3/6/2010 7:07:12 PM Exception: System.ArgumentException: String cannot be of zero length.
Parameter name: oldValue ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 778, offset:277 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 769, offset:252
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at MultiRelogger.BabySitter.#5l()
at MultiRelogger.BabySitter.#4l()
3/6/2010 7:07:12 PM Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at (Object )
at MultiRelogger.BabySitter.#4l()
3/6/2010 7:07:12 PM Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at (Object )
at MultiRelogger.BabySitter.#4l()
3/6/2010 7:07:12 PM Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at (Object )
at MultiRelogger.BabySitter.#4l()
3/6/2010 7:07:12 PM Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at (Object )
at MultiRelogger.BabySitter.#4l()

 

I had to delete my wow.exe and leave my Gather/honorbuddy.exe in the path file this time

Another thing that i noticed, not sure if its some sort of cpu saving thing or it might just be windows 7 but i minimalized it and now i cant seem open it again. it still open cause i can see it with alt tab but if i click on it nothing happens

*EDIT*
nvm after minimalizing all my bots i was able to open it.

 

This seems sweet, tomorrow when i'm sober i'll even going to read through 8 pages of "chat"

 

I made my best to keep the front page updated with all the information users had problems with along the 8 pages this thread already has.

I am sure you can just start using it effectively by just reading the front page.

 

Did this happen when you clicked start or after having it running for a while?

 

Was it in the background, behind the bots? If that was the case, you can enable the TopMost feature.

You shouldnt have to delete your wow files for a simple path string on a program, please dont edit the config files directly. Allow for the program to edit them, it should auto-fix anything.

If you edit the files manually, make sure you didnt "mess up" somewhere. The bot path in config files shouldnt use "\Wow.exe" at the end anymore. I added it manually inside the code, I now just need the "path to wow install" in the config files.

 

First time running it. After hitting start.

 

ya, still getting that exception error.. :/ hope it gets fixed, nice contribution tho.

 

I had it too at first,


Try this:
Delete the Wow.exe from the folder path so it only has the "E:\Games\WorldOfWarcraft\" instead of "E:\Games\WorldOfWarcraft\Wow.exe"