eafa
Members
-
Joined
-
Last visited
Everything posted by eafa
-
Hi, when I'm using a batch file to run wow, relogger is just launching it over and over, assuming that games has failed to launch, even though 1st instance is already running fine. HBRelog handles batch launching fine though, please fix that coz it's a crucial feature for me. http://joxi.ru/brRdeg3SJyPlx2?d=1
-
Thank you, was busy with Legion, will try tommorow
-
system is fine, temp is low even on 100% cpu load and when it runs wow bots it is 10-30% load, not more than that
-
found this article https://support.microsoft.com/en-us/kb/2876900 I'll try their fix and see if it helps
-
Ok, thanks.
-
BSOD again, no driver module or anything, just this : STOP: 0x000000F4 Also there is big wow mouse pointer in the middle of the screen which means that wow was full screen 800*600 or 1024*768 - default setting, which happens exactly when I try to launch more than 1 wow instances at the same moment. Wow just goes default probably coz Config.wtf is busy at that moment.
-
Don't need it to go into [Regen] , how to completely remove this state from engine ?
-
no idea, turned off auto-reboot to look at it next time and let you know, also noticed that I have DEP on in my system settings, which I remember may cause problems with bot programs
-
Sorry for the confusion, my problem was caused by a .dll plugin which was compiled with the previous version, all good without it. But ! I still have another problem - my PC may get BSOD and reboot accidently while running 3+ wrobot+wotlk instances, it also seems that it happens on mass relog/restart, for example when server goes down or works unstable, I've also noticed that relogger doesn't "lock" wow executable while loading, hbrelog does such thing and it lowers to minimum any loading collisions. Can you add a checkbox for "loading lock" to allow only 1 wow instance to load at once ?
-
I have crash reports turned off but I've noticed that it crashes after green logs (fightclass).
-
Like it says, it crashes after starting any grinder/quester profile, had to roll back to 35712, latest backup I had :(
-
There is another issue now, when relogger is launching all profiles using "Start Checked" (8 atm) , 1 or more wow instances would load with default setttings (fullscreen, default graphics, etc) so a minor delay between launchs is needed, atleast 1 sec.
-
works now, thanks !
-
-
-
clean windows 7, all bs disabled (uac, guard, etc.), worked fine till today
-
Same issue, please help.
-
works well, thank you !
-
This is how it works (ss attached)
-
Because I need to use proxy to avoid bans for running all accounts on the same IP and proxifier/proxycap require different wow executable for each proxy. I thought everyone nowdays is using proxies to bot, looks like I was wrong, haha.
-
*** using Wrobot on 3.3.5a Warmane server
-
Grinding in Northrend on stags/bears and bot doesn't skin mobs sometimes, it happens quite randomly so sometimes it would skin all mobs for 10 minutes, then skip few mobs and start skinning again or just skins half of the mobs all the time. Please look into skinning logic and make changes to recheck whether mob is skinnable and able to be skinned. P.s. same thing happens to honorbuddy for 3.3.5a so I had to make own plugin for it to skin correctly, will have to write such plugin for wrobot too if you won't fix it
-
Hi, please add <PathToWow> for each Relogger profile to choose separate wow executable for each profile for proxification purpose. Now I have to launch 1 relogger for each wow instance and it causes problems when 2-3 reloggers try to restart wow simultaneously PC may hang or reboot. I've bought yearly sub and plan to use Wrobot for both Wotlk and Legion later. Thanks!
-
Hi, please add <PathToWow> for each Relogger profile to choose separate wow executable for each profile for proxification purpose. Now I have to launch 1 relogger for each wow instance and it causes problems when 2-3 reloggers try to restart wow simultaneously PC may hang or reboot. I've bought yearly sub and plan to use Wrobot for both Wotlk and Legion later. Thanks!
