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

Botstarter and Relogger for Gb/Hb

I've been running this with honorbuddy, was working well till it kept killing wow, im trying out the latest version

Will report back
 
bryt said:
hm, thats weird, the relogger will only work, if you have started the wow/bots with the relogger or botstarter, otherwise it should restart them

I have made some changes in the check wow loop, please try 1.8.4

//edit: ah, didn't see its working for you now, is it working with 1.8.3?
Click to expand...
sometimes it works, sometimes it doesnt. I will try 1.8.4 :) Btw the relogger checks with gb if you got dced right? Cus gb is not noticing if I get dced for some funny reason so it wont relogg.

edit:
No wow check errors with 1.8.4! Thanks.

I will report back about the not noticing dc thing.
 
Last edited:
Erikovitch said:
sometimes it works, sometimes it doesnt. I will try 1.8.4 :) Btw the relogger checks with gb if you got dced right? Cus gb is not noticing if I get dced for some funny reason so it wont relogg.

edit:
No wow check errors with 1.8.4! Thanks.

I will report back about the not noticing dc thing.
Click to expand...

the relogger will restart wow/bots if:
- wow or bot window does not exist
- gatherbuddy says: "Can't see player health" or "Not connected to WoW" or "Please auth first"
- honorbuddy says "Not in game or Me == null"

don't you get this messages in your gatherbuddy? if not, what messages are you getting when disconnected? or do you even get new msgs in gatherbuddy window when disconnected?
 
Gb tells me that Im stuck and repeats it.

edit: But that has nothing to do with your program ofc. Maybe I have a too small wow window?
 
Last edited:
Erikovitch said:
Gb tells me that Im stuck and repeats it.

edit: But that has nothing to do with your program ofc. Maybe I have a too small wow window?
Click to expand...

//update 1.8.5:
- if you geht crazy unsticks on disconnect, it should now detect it and restart the wow/bots
Click to expand...
if you have problems with this feature, you can disable it by changing
Code: 
Global $unstickcheck = 1
to 0
 
there seams to be a bug, on accounts under "battlenet account settings"
when you leave it blank, so when there is only 1 account, and try to start it, you got connection problem on starting wow

all other accounts where i had WoW1 WoW2 etc. write in, are working


*edit*

sry seams to be a prob with wow servers
 
Last edited:
Hey m8, thanks so much for all these updates, the project is moving along great and thanks for including my suggestions so quickly! I just have one issue that kind of destroys the point in what you have scripted. Basically, occasionally when I disconnect or just randomly, I get a wow error. When I get these wow errors (one happened about 20 minutes after I went to bed last night), the relogger goes crazy. I had about 100 GBs open, and it was because there was the option to connect to an empty wow window and the relogger didn't know what to do. What I was wondering was if you could have an "AFK" mode - you can tick it in the settings and what it does is make sure that only you're wows and connected GBs/HBs are open. I don't know how hard it would be but it would just require looking in an Applications Open type thing? Tbh I have no idea :S But yeh, that would ultimately complete this for me as otherwise leaving it on overnight doesn't work greatly.

So, just for example:

You have two wow gb settings running with relogger.
If the afk button is clicked, AutoIt will check (along with the pink check?) if there are correctly four windows open, World of Warcraft, World of Warcraft, Gatherbuddy, Gatherbuddy
If this is correct, continue monitering.
If there is another unknown window, kill it.

And I'm guessing if it kills this window and it causes WoW to close, GB will close and it will relogg it.

Also, for example:

If there are three WoWs instead of two, kill all and start again. (as when relog begins again, it simply wont work)


So yeh, I know it will be hard and I don't even know if its possible but either way thanks for all your work that you've put into this and thanks if you can make this work :)

*PS - For people who have issues with the password not being typed in fully over and over, I just added a few extra sleeps and tested over and over to make sure xD
Thanks again m8 <3

EDIT - Just got a wow error thing because I dced, I didn't have this running so I couldn't see results but the error I get is attached, anybody else get the same error? So that's the window that I get, along with a window called "WoWError" - so if it's easier or possible, if those windows appear, close them and then begin relog? Thanks xD

Forgot to attach:

error.webp
 
Last edited:
It works ok for me now, at least I dont come back to a pc with a dced wow but it sometimes disconnect without having too.. Btw I must say you thought of a very nice way to fix the issue!

example:
 

Attachments

  • issue.webp
    issue.webp
    28.3 KB · Views: 58
Last edited:
hm the newest version (1.8.5) doestn work at me. He doesnt relog or start to login and sends no errors.
But 1.7.9. works perfect.
 
//update 1.8.7:
- crazy unstick check should now leave the loop, when a new message is visible
- error msg should be fixed
- new feature: if more than xx wow/bot's are opened, it will kill all wow/bot's and restart the relogger
- a new tab in settings: Relogger, here you can make some changes for the relogger, like enable/disable pingcheck and also edit the new feature

- bot timers are still a bit buggy
with 20 23 settings
it would bot from 20 o'clock until 23 o'clock
but 20 1 would not bot from 20-1 o'clock
I have to rethink about it
Click to expand...
relogger.webp

I hope there are no new bugs :P
 
This version try to start the hole time wow's with Gb;s

it seams it dont reconize that there are allready running wow's are...
i have 9 wow's in and he try to start these 9the hole time over and over :D
 
crack00r said:
This version try to start the hole time wow's with Gb;s

it seams it dont reconize that there are allready running wow's are...
i have 9 wow's in and he try to start these 9the hole time over and over :D
Click to expand...

hi, please try 1.8.8

and if you have still problems, uncomment the msgbox in line 2525, just remove the ; and tell me the information after your 9th wow
 
ok, testing

*edit*
the std. dont work..
still relog the hole time around the list

now try the 2nd

*edit2*
i remove the ; in 2525 but still try to load the hole time

just some infos for the settings:
1-6 = GB
7-9 = HB
10 = GB

i activate all GB's and 1 HB
Setting 8 & 9 is deactivated
 
Last edited:
crack00r said:
ok, testing

*edit*
the std. dont work..
still relog the hole time around the list

now try the 2nd

*edit2*
i remove the ; in 2525 but still try to load the hole time

just some infos for the settings:
1-6 = GB
7-9 = HB
10 = GB

i activate all GB's and 1 HB
Setting 8 & 9 is deactivated
Click to expand...

do you have the problems with the relogger or just with the Start Bots function?
 
You must log in or register to reply here.
Back
Top