HB ARCHIVES: ARelog--DO NOT DELETE

AMAZING, great release thank you Raphus!

 

I have got problem with schedule.
I filled out like below:

Then I press Start All button (profiles are selected) and it runs, after 2 hours stops and then not starting after 1 hour of idling. Why?

 

I need a delay timer, when clicking on "start all".
delay timer = 60 - 60 seconds between starting every wow/bot.

is it able to built it in ?

 

Guys, i have problem and cant know this problem new version hb or arelog?
problem: Keyboard setting in wow set to default? and setting interface (mouse and camera).
Before when I did not use the arelog I not have this problem.
Sry for my bad english.
(hb only change setting to add "mouse click to move")
(sry my bad english and ty)

 

[9:57:25 AM:180] Starting WoW
[9:57:25 AM:189] Waiting for WoW to idle
[9:57:25 AM:375] [PID: 776] Moving WoW Window to: 3022, 1 - With size: 816x638

BLAHH!!!!!!!!!!!!!!!!

Anyone know why it will just open up WoW, think its idle, then "try" to move it, but it does nothing and sits there forever?

TLDR, Opens wow, doesnt move window, idles forever.

 

I got a Problem with ARelog. It starts Wow. Logs successfully in. Loads Character. Starts HB. And in this moment when HB is starting Wow gets a "Disconnected from Server". And HB cant inject into the WoW-Process.

The Log:

Code:

[16:09:10:77] Starting ARelog v1.0.0.8
[16:09:10:80] Checking for updates.
[16:09:12:766] ARelog is up-to-date
[16:09:21:335] Starting WoW
[16:09:21:352] Waiting for WoW to idle
[16:09:26:22] [PID: 1600] Moving WoW Window to: 0, 0 - With size: 1024x768
[16:09:29:828] [PID: 1600] Selecting character and entering world.
[16:09:31:952] [PID: 1600] Logged in! Waiting on loading screen.
[16:09:37:952] [PID: 1600] Starting Honorbuddy
[16:09:46:546] [PID: 1600] Terminating monitor on request.
[16:09:46:888] All monitors are terminated.

Code:

[16:09:38:921] Logging in...
[16:09:39:325] Buddy Sessions: 0/0
-----
Shared Sessions: 1/3
[16:09:39:685] -------------------------------
[16:09:39:685] You have not selected a valid instance of WoW to attach to!
[16:09:39:685] Please restart Honorbuddy and choose a valid instance of WoW to use Honorbuddy with!
[16:09:39:685] This version of Honorbuddy only supports WoW Build #14333
[16:09:39:686] You are currently on build #0
[16:09:39:686] -------------------------------

 

I have 2 wows and 2 hbs running on a quarter of the screen each, so i can watch the status as well. Took me a while to set that up.
A relog didn't see that a) i'm already logged in on both chars ,which is a little bit sad but b) could you also make it resize and place the hb windows too if the user wishes to do so?
Can you make it automatically place those windows in a perfect 1/4th of the screen somehow? resizing manually is difficult.

Next, a more important point:

I don't like other people stealing stuff from my accounts so the underlying bnet account is protected by a wow authenticator.
German IPs only change if you disconnect (happens every 24h at 6am for me). When the IP changes , wow askes for the authenticator key once till ip changes again.
I'd love to see Arelog detecting that window and entering the correct authenticator.number.
Source for authenticator-emulators can be found on mmowned and the internet, so it should be easy to add.

 

HB saves its size and position in the settings. So you have to size and place the HB-Window only once.

 

Would it be possible to add an option to loop through the scheduled tasks?

 

Thanks for the work you've done. Just make it close HB errors on its own and it will be perfect for me)

 

For the scheduling can we add a option for x time break, like
Load profile 3 hours
break
relogin 3 hours profile

kinda idea would be great.,

 

can you please chance the hours into minutes? at schedule?

 

Same here.

 

With the new update it is constantly spamming the ARelog log with 'Current Task: Botname: Gatherbuddy2 - ProfilePath' and so on.

also when starting it up it keeps thinking HB has crashed (even when it hasn't) and it closes it and re-opens it, it repeats this about 50 times and then it will finally start.

no issues up until this last update.

 

Yould you built in a "Relog-Delayer" ?
I didn't found an answer onto my question :/

 

For me it should have got options:
- reloging, that schedule is not enaught, I need HB works 24/7 and donot want to touch that reloger by weeks, just repeating all the time relogs
- able to random close and start HB, fe. you set idle 30-60 mins and farm 240-300mins and it makes bot farm and idle for random amount of the time in these brackets
- idle and run should be in minutes
- after HB crash it shouldnot log to HB so fast becouse session is not killed and he is doing that 30 seconds, if he would press login button every 10 sec would be better
- same with WoW but login button should be press like every 2 mins or less