What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

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

Didn't work. I noticed you blacked out "Bot Name". Is that not supposed to be the name of the *buddy executable file? In any event I tried the filename, and just in case I was mistaken, the character name. Neither work.
 
okeofs said:
Didn't work. I noticed you blacked out "Bot Name". Is that not supposed to be the name of the *buddy executable file? In any event I tried the filename, and just in case I was mistaken, the character name. Neither work.
Click to expand...

I have the character name on there yeah, hm wierd it dindt work :( cant think of anything else i did to make it work
 
DiFusioN said:
I have the character name on there yeah, hm wierd it dindt work :( cant think of anything else i did to make it work
Click to expand...

Mess1337 tould me to wirte in the name of your Honobody.exe not the Name of the Bot you want to use^^

Why the name of the exe?

Some say Blizzard or rather Warden scans your computer and open threads/folders/exe's for they're names, so many ppl - like me - rename they're .exe and folders^^
 
Getting a weird popup though, if one of my bots disconnects it will start one back but i get this:

Currentrealm SET realmName "My-realm-name-here" Replaced by: SET realmName "Same-realm-name-here"
Click to expand...

And well it wont start up wow before i click ok
 
DiFusioN said:
Getting a weird popup though, if one of my bots disconnects it will start one back but i get this:



And well it wont start up wow before i click ok
Click to expand...

I don't have the current version but is there any kinde of file that you can configure?
If so, open it and search the line (using STRG+F button) >Currentrealm SET realmName "My-realm-name-here"<-
Put between the " " the name of your realm. For example
uparrow.gif
Bloodhoof
 
No go. It's also not throwing out the whitespace of my realm name. I doubt that the realm name is the issue.
 
getting errors

Code: 
3/7/2010 1:09:19 AM killAndRestartWowAndBot requested
3/7/2010 1:09:19 AM KillWowAndBot requested
3/7/2010 1:09:19 AM StartFreshWowAndBotSequence requested
3/7/2010 1:09:19 AM 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/7/2010 1:09:19 AM Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at (Object )
   at MultiRelogger.BabySitter.#4l()
3/7/2010 1:09:19 AM Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at (Object )
   at MultiRelogger.BabySitter.#4l()
3/7/2010 1:09:19 AM Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at (Object )
   at MultiRelogger.BabySitter.#4l()
3/7/2010 1:09:19 AM Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at (Object )
   at MultiRelogger.BabySitter.#4l()
3/7/2010 1:09:19 AM Exit Watching Loop, no longer Baby Sitting
 
Looks like we all have the same problem. Will check again in the morning. If you need logs let me know. Thanks for the hard work thus far. Looks highly promising.

Best,

Jon.
 
Tried all manner of paths, .exe names, names, etc and can't get around the Exception error. :(
 
ski said:
Tried all manner of paths, .exe names, names, etc and can't get around the Exception error. :(
Click to expand...

By reading the front page, you can get this info :
Configuration:
- WoW Name is the process' running name without the ".exe" -> default should be: "Wow"
- Bot Name is the process' running name without the ".exe" -> default should be: example "Gatherbuddy" or "Msn", etc.
- Multi Acc is used to configure the relogger to handle multiple wow accounts inside the specified Battlenet account, including the index position of the one you want. 0 means the first one, and so on.
Click to expand...

Its been there for quite a while.


As for the messagebox popup, i removed it in the last version, are you sure you updated it?

Maybe I mixed up the upload if you are sure you have the lastest version
 
Dalees said:
Mess1337 tould me to wirte in the name of your Honobody.exe not the Name of the Bot you want to use^^

Why the name of the exe?

Some say Blizzard or rather Warden scans your computer and open threads/folders/exe's for they're names, so many ppl - like me - rename they're .exe and folders^^
Click to expand...

Thats correct, some ppl dont like to have .exe named "HonorBuddy.exe", and by renaming the file, the process name and window caption will also change, to allow for this change, I added a configuration option for that. Also for WoW, but right now I think I completely phased out the use of that string. I kept it because it will be used in a future version for detection of already open processes.

As far as your exceptions, where exactly do you get them? What exactly did you do?

Without this information it will be a ton hard to find the problem.
 
Regardless, this is not working. I will put back the default way of doing things, and add an extra configuration option.

Maybe like that it will make it easier for you guys.
 
Last edited:
MrBig said:
By reading the front page, you can get this info :


Its been there for quite a while.


As for the messagebox popup, i removed it in the last version, are you sure you updated it?

Maybe I mixed up the upload if you are sure you have the lastest version
Click to expand...

I'm aware of the front page info :)

I tried that, and many other combinations. The error still happens. It is not a messagebox, it is spammed inside the log window of the program as my screenshot before shows.

I'll try the latest upload again and see what happens.
 
Last edited:
Will this relogger react to wow crashes? a 132 for example, will it close the error screen and reopen wow? I would hate for it to hang or send the error report to blizzard.
 
Mordd said:
Will this relogger react to wow crashes? a 132 for example, will it close the error screen and reopen wow? I would hate for it to hang or send the error report to blizzard.
Click to expand...

Yup, AFAIK the error report uses the same process of the wow window, so, if it crashes, it will stop beeing ingame, if its not ingame and it should be ingame, everything is closed, and restarted. (but i didnt make any special code for it, and didnt test it because i dont know how to force a crash, but i have seen wow crash and when relogger started everything the error window vanished, not sure if relogger did this)

If for wateva reason the error resets your configurations, the relooger will edit some basic configurations like "windowed mode", "agree to TOS", "agree to EULA, and a bunch of other items including the server and region, and go from there.
 
Old settings system is back on.

New settings for setting up the location of the Config.wtf file.

New version should be released shortly, did a major overhaul to all the detection procedures and added logic to handle unexpected undetected behavior by looking for expected results. Also if something crashes in the middle of the sequences, the whole process should be restarted from scrap to avoid further problems.

Also, added code so that I know exactly what threads were started thus beeing able to shutdown everything, even sub-sub-sub-threads.

Changed the logs code to make it simpler to identify errors by Alias, your logs should now show up on the "Logs" folder with format "ALIAS_Log.txt", folder will be auto-created if it isnt present.

Rearange windows code changed slightly, should now display properly the ALIAS of the corresponding "baby" instead of the baby number.

Several stability problems also addressed.

Performance counters are now disabled until I found out why are they corrupting WoWs memory.

Running some final checks to see if everything is working. Then will upload it
 
Last edited:
So it will load a wtf ?

If not, would be cool to have a backup.
 
You must log in or register to reply here.
Back
Top