In dire need of a relogger.

Hey,

I know theres Arelog, but this wont work for me. I get the usual Invalid executor error, then it wont type anything into wow.(Don't know if these 2 are related tbh)
I also understand a script won't work, because HB needs to have a char loaded to run it, and if you get disconnected, hb will stop working.

However, I'm im dire need of something that will relog for me. Every day I wake up with the 'You have been disconnected from the server' message. Which is funny really, because I can babysit the bot for 10 hours and get no disconnects. But as soon as I go to bed..

Is there anything out there for us that can't get ARelog to work?

- Dandy

 

if you cant get it to work, what problems are you having with it?
Arelog works really well, thats why its the only one. so if your having problems, what are the problem so we can get you up and running.

 

noticed that as well

 

you must have a letter off here or there... in the Edit area. i know sometimes when i add new accounts if i forget to add the (x86) C:\Program Files (x86)\World of Warcraft

Than i get errors, just make sure you have the paths correctly. OR your internet service could restart late at night.... before when i ran bots just reg, i would wake up to " disconnected from wow blah blah" but since i got the Arelog it never does it unless its a server restart

 

Hey,

Heres how it goes:
Launching Arelog - Start all - 3 seconds goes by - Getting a invalid executor error(Can provide a SS if necessary) - Wow instantly pops up afterwards - Nothing else happens - Arelog says 'Waiting for wow to idle'

Now, as for my setup.
My char has weird characters, ie ??. Not sure if this has anything to do with it.
My paths should be correct. I've double clicked where you input your path, and linked to the exe. My bot is renamed, not sure if this has anything to do with it either. My wow is on C: drive and bot on D: drive.

So basicly, the problem is, when it launches wow, nothing happens.

 

hmm ya try to just launch one at a time.?

 

yea, post a screen shot, just make sure all toon names are edited out if they are shown.

 

Yes, I only have 1 account added, and I've tried both Start selected & all.

 

Funny thing.

I forgot I had wow already open, and launched everything as previously described, and it worked like a charm. Closed all running wow windows, and tried again and got same old error.
Im not sure what to make of this now.

 

did you make sure to full in all the information for the account, like character name, server name, passsword username, everything?
if not try going into your Arelog folder and deleting Monitor.xml
and re-entering all your information.

also make sure Arelog is updated to the latest version.

 

take a picture of the edit info. bleep out your account info but show the folder locations of wow and honorbuddy


i bet you messed with the window resizing and that s causing an error for some reason. leave "window Size" and "window Location " on 0's

 

the location can be 0,0
but when i setup the window size i put 800,600

so if leaving them blank wont do it, try at least filling in the window size

 

Not quite sure how the scheduling works, but I added it in there anyway.

 

you happen to have lowerping installed or something similar?

 

No, but I do have something similar. I do not think its called LowerPing, but it was a script i ran and magicly lost 250MS hehe.

I have no clue whatsoever how to uninstall it.

To clarify; I do not have any ping addons installed.

edit: If it infact was a addon, why would it run perfectly when wow is already open?

 

i know what it is.. you have the W capitalized in wow.exe



also i don't think you need to put the account name if there is only one account on the bnet account.. at least i don't

 

now if you select the account, and press "Start Selected" does it start up fine? make sure HB and WoW are completely Closed.
also your custom class, you may need to uninstall the other custom classes for that class, so HB auto selects it. and just leave it blank in arelog.

 

Under the right conditions Arelog will wait until the WoW window is loaded and waiting for input before attempting to log in. According to your description this isn't happening, exception is thrown before the WoW window shows up. The LowerPing program interferes with Arelog and can cause it to not wait for the WoW window to not load. There might be other programs that also interfere, idk

 

Done, made zero difference.

Done, no difference.

Didnt make a difference, I've several accounts on the same bnet account(Oh my do I regret)


Really appreciate all this speedy help, im sure we'll get it soon!

 

It was Leatrix latency fix I was thinking of, but made a search on my computer and I no longer seem to be running this. Must've forgot to install it again after whiping my harddrives.

So I should'nt have anything out of the ordinary interfering..