Thanks for the amazing script. One thing I've noticed though, that happens only if I start with the restarter_without_gui. ( It doesn't do that if I just click start bot on the actual gui ) WoW1 launches, logs in, re sizes the window, HB1 Starts, logs in and the bot starts... Now, after that, WoW2 starts, logs in, re sizes the window, HB2 starts ON TOP OF HB1 and doesn't re sizes or move. Restarter can't see HB1 and closes WoW1 but not HB1... It tries to launch another WoW1, and the new HB1( or HB3 now, since it didn't close HB1 ) blocks HB2, so WoW2 closes... It does that all over again. It works perfectly fine with the "Start Bots", and re sizes every time with it, as opposed to the restarter_without_Gui.
Not sure what I'm missing here.. This works for HB right? I setup the script to open my two GB bots first, then my two HB bots (so four total clients or sessions). After it loads the GB bots, it opens the first HB client, resizes it, then opens HB.exe for that client then spams waiting for visible button, then closes the game. When it restarts the HB1 game, it suddenly closes my GB2.exe (bot itself not game client for gb2) and then I get a nice little select process when it opens HB1.exe again cause the GB2 client is open and it restarted the HB1 client.. so then it closes everything and begins the loop again haha I have HB boxes checked for accounts 3 and 4 so I'm not sure why it wont click login for HB. Am I making sense with all the hb1s hb2s lol. I rename honorbuddy.exe to HB1 HB2 etc
I have this problem: I run 5x Gb and 3 x HB on my PC. The relogger starts the wows and opens the bots fine...everything works perfect. I let it do the 5 Gbs first and the 3 HBs after that. But as soon as the latest Hb is opened it closes the fiirst wow and relogs it. As soon as this wow is reloged it closes the second and so on...this continues the whole time. I tried unticking all options under the reloger but it still does this
I'm still getting the relogger not being able to detect whether the bot or WoW are open or not. Once it logs into both of my accounts, starts both the bots (1 hb, 1 gb) it simply starts to restart the first one then the second and logs that the bot and wow could not be found.
We are all having the same problem it seems. If it's not something you can fix easily, it would be nice to have it check the Process ID instead of the window being visible, just temporarily until you figure out what is causing that.
I have the same problem. wow starts, hb starts. then it close wow and restart, but not hb. Then i tried version 1.9.6 and it works fine. maybe it helps you guys.
there was something wrong for HB in relogger, I have fixed that in version 2.0.1 and if you still have problems with not detected wow/bot, then try the 2.0.1_test version, this will use processid instead of window handle I think so, just test it
Yeah everything is fixed minus the repositioning/resizing of HB program itself.. they just started almost ontop of each other, never were repositioned/resized, not a biggie but just saying.
Maybe you could make it restart if the same error message gets repeated like 3 times? GB doesnt notice DC so it just keeps spamming some error message upon dcing.
I'm not sure if I did something wrong but none of my monitoring plug-ins work.. For example iMonitor keeps throwing a "creating iMonitor.ini" over and over; and SugarMonitor doesnt have any of my settings saved and keeps throwing errors in the log Edit: anyone know why my plug-ins aren't working when I use this? Are plugins supported?
I have tested iMonitor and can confirm it ends up in a endless msg with creating imonitor.ini, it only happens when I start honorbuddy with ShellExecute() or Run(), I don't know why :/ But I have added a workaround for this in version 2.0.3, I hope its working for you, enable it in settings:
Awesome Bryt! That's great to hear. I mainly use SugarMonitor and what happens is it erases my login details for my webspace(URL, login, password) and throws an endless error. If I try to enter my settings in while the Relogger is running it crashes HB.
Says I DL'd 2.0.3 but dont see it in the folder with the other updates.. any ideas. Well DUH downloaded it from the first page.. 2.0.3 then told me theres a new version and said it was 2.0.3 lol
sorry, I forgot to edit the version number, please redownload 2.0.3 again the updater is not working in version 2.0.1 and 2.0.2, but you can use an older version to update