Hello I have a might sounds weird request, but it is based on my experience with recent bans. I was too tired and fell asleep when the banning process happened. Toons was farming Botanica and I suspect a GM made mobs inside cannot die and let the toon stuck hitting endlessly (this invincible mobs happens before but i was there to stop the bot). After that they will disconnect us and send us a password reset request to our email. They will note that HBrelog keeps logging in with the same password endlessly, and thus decide that we are botting and ban us. My request is that you provide a behaviour so HBrelog don't auto relog after two wrong password attempt. So we can later found our password was changed and set it right. edit : might as well set an option to completely turn off relogging at all (yeah kick my shin ) Fortunately my appeal was successful, I don't even get 72 hours. HBrelog is a magnificent program, makes botting so much more convinient, I thank you.
why do you want an option in a relogger to stop relogging? but an option to set a relog attempt would be great
Can I have an example of tasks usage please, I tried to read and understand but it seems I'm still confused.
So this is the issue that i'm running into: I have setup a chain of profiles When i start the profile i have these settings: Farm Profile wait 120 Idle 5 Start Profile: Bank Profile Stop Profile: Farm Profile Bank Profile Wait 25 Idle 5 Start Profile: Alt Profile Stop Profile: Bank Profile Alt Profile Wait 180 idle 5 Start Profile: Farm Profile Stop Profile: Alt Profile What seems to be happening is that either the profiles arent stopping properly, and when i come back to my PC all the profiles are running at the same time. It seems for some reason when i am watching it that when wow or HB crashes instead of restarting the apps, its starting the next Profile task.
thats because you think that hbrelog jumps from task list to task list. but thats wrong each profile treads on the other profiles feet.
Yes but by as soon as the other profile has started the Stop profile should stop the current profile that is running... thats why i'm logging issue....
OK so thats a bug. If you run a profile by clicking the Start button, and then click the Stop button to stop a profile, you dont expect it to start running the tasks in that profile again. If the last task of my profile is to stop itself then it should STOP???
If a profile is Stopped it should not be running any more tasks. If i wanted my profile to keep running then i would use idle not STOP, i'm not sure you understand what stop means? Defeats the point of having a Stop profile, if it doesnt stop profiles and the tasks keep running?
If i wanted to start a profile have it run for 3 hours then stop, how would i do that? I cant use stop because the tasks will continuously keep running forever...
Highvoltz can you check one think? This may be hbrelog's issue after recent updates I'm facing this issue that I've never faced before I think this could be because HBrelog isn't loading profiles good. Sometimes when it loads profiles bot just runs from hotspot to hotspot not killing anything nor looting only defending if agro. But it happens randomly and when it happens I see in the log files: [12:07:35.487 D] Lua failed! Status: ErrRun [12:07:36.267 N] [Singular] info: Pull Distance set to 100 yds by ProfessionBuddy, Plug-in, Profile, or User [12:07:36.410 D] Styx.HonorbuddyUnableToStartException: Can not start quest bot - this profile does not contain a quest order! at Bots.Quest.QuestBot.Start() at HighVoltz.Composites.PbRootComposite.<CreateSeondaryBotBehavior>b__1(Object ctx) in c:\Users\PC\Desktop\HB\Bots\Professionbuddy\Composites\PbRootComposite.cs:line 43 [12:07:36.625 D] Lua failed! Status: ErrRun [12:07:36.672 D] Changed POI to: Type: Kill, Name: Thundermaw [12:07:37.245 D] Lua failed! Status: ErrRun my professionbuddd profile loads questing profile never had these issues before
View attachment 134164 worked perfectly fine till few days ago, everytime i start it freezes my wow. Logg inc!
I request a better logic for HBrelog for tasks sequence, so it is possible that next task is executed after the current HB profile finished a cycle (for example dungeon run), instead of cutting it right away in the middle.
Yes task schedule is terrible hbrelog doesnt work good in scheduling sometimes I see it idling in like 10 mins of running and it suppost to idle in like 2 hour
Need Help If i set up HB Relog i get some errors and it doesnt log in Need Help View attachment 134376
as the random time of the task works I put in 20 minutes in 45 random and select -18 minutes if possible as this is supposed to have put between 20 and 45, what is the problem?
the problem is you didnt read well. 20 minutes with 45 min random means a time between -25 and 65 min...read the tooltip, it helps
