starter... i cant use the relogger it start GB1 Gb2 GB3 gb4 gb5 gb6 hb1 gb7 then again start gb1 gb2 etc.. i mean wow with gb1 etc. as you know whne i try to click settings ore relogger nothing happen... it start the hole time all gb's
Bryt i have got problem with any higher version then 1.7.1. 1.7.1 works perfect for me ,but if i start higher version is always after start up all my wow and bots autoIT got critical crash.
ah, I always thought you had the problems with the relogger, I have just tested the botstarter and could reproduce it, should be fixed in 1.8.9 also if you still have problems with the relogger in newer versions, please change Code: Global $debug1 = 0 to 1 if its the same error, that crack00r has posted on page 10, then it should be fixed in the newer versions //edit: in 1.8.9 I have forgot to remove a msgbox after starting bots is done, I have just reuploaded 1.8.9 without msgbox
I've to say that I didn't look at ur code - but probably it's pretty simple. Do you calculate how log to run and let it run? Would mean: from 14:00 to 22:00 ==> 22-14 = 8 hours to run (works perfect) from 22:00 to 01:00 ==> 01-22 = -21 - what wouldn't work. how to deal with in a pretty simple way? Check if the second number is bigger then the first (14<22) if yes - calculate. If not add 24 to the second number and to the same calculation: example: 14<22 = true --> calculate; 22-14=8 --> bot 8 hours 22<01 = false --> add 24 to the second number and calculate; 22-(24+01)= 3hours to bot
Isn't it too intricate? Is simplifier / smarter solution make 2 msgboxs with bot time and wait time? For example, bot 10h - wait 16h. oor make something for every day in week due to maintance
So, how do you guys monitor your tells from other people if your windows are so small and always being kept automated (relog etc)? I mean I just had someone bitching at me in storm peaks saying I killed their rare mob, and I've had someone tell me im in storm peaks a lot.. been thinking of moving to another place for icethorn/lich.
Dont know if anyone else is having my problem, but with the newest version, i have it for 2 accounts, and it gets the 1st one done flawlessly, then opens the 2nd wow, logs in flawlessly as well, then opens up the 2nd GB and tries to start the 1st one, which makes him move the 1st GB to where the 2nd GB should be, and the 2nd GB never gets started or touched after the .exe is run. Any help?
Hi, hm, this is weird, the code says: Code: Run(IniRead("settings.ini", "Account", "gbpath" & $i, "")) Sleep(4000) Select Case GUICtrlRead($Checkbox_hb[$i]) = 4 $hwnd = WinGetHandle("[CLASS:WindowsForms10.Window.8.app.0.2004eee]") $bothwnd[$i] = IniWrite("settings.ini", "Account", "bothwnd" & $i, $hwnd) if there are more than 1 windows with the same name, autoit will use the last active window, so the only reason I can think of is that the other GB window was active, before it saves the handle to settings.ini, but this should be unlikely. //btw I hadn't time to work on the bot timer feature, yet
and if you have time please put some function into, to rename each wow window to an different name and a function to deactivate only the 1sec status ping message. But great thanks for this nice reloger. I think you should putting a donate button on this thread to say a special thanks to you