RebornBuddy Forums
Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
HB ARCHIVES: ARelog--DO NOT DELETE
- Thread starter Kickazz006
- Start date
Thank you for the fix, working as intended (maybe doing a 60 sec delay instead of 30 for users with slow internet or pc connections, it will still be much better than idling for 30 min on the character selection screen like it used to be).
I just sent you a PM about this new serious bug that came up on this lastest version : if HB crashes during launch or later ingame or if you close HB manually for example, Arelog will show an error and won't relaunch HB again until you manually close WOW.
I just sent you a PM about this new serious bug that came up on this lastest version : if HB crashes during launch or later ingame or if you close HB manually for example, Arelog will show an error and won't relaunch HB again until you manually close WOW.
Just wanted to point out a suggestion to fix another old arelog bug : the multiple HB windows crashing during the login.
FACTS :
- If you launch multiple WOW accounts at the same time or with little delay : usually they all get ingame without causing any problem, and rarely crashes (depending on how many accounts you start and your computer specs or network speed...)
- But if you launch multiple HB windows at the same time or with little delay (like 1 to 8 sec between each instance) : usually you get one or more HB windows to crash at the initialization process.
SUGGESTION 1 :
The first suggestion would be to add in arelog a check for the status of the launched accounts.
If you start 3 accounts at the same time for example, all wow windows can start simultaneously (like how it is working now). But each HB account window need to wait for the previous instance to complete it's loading, by checking the status in arelog.
The first HB window can then start instantly when you get ingame, but the next HB window needs to read and wait for the arelog status of all previous accounts to show "Monitoring" before it can start, so arelog can check in a loop all the launched accounts and while one of these accounts has the status of "Logging in", it waits for that status to change.
SUGGESTION 2 :
If the first suggestion is inaccurate or hard to manage, maybe you can add an option on the settings of each account, like a delay input in seconds.
As a user, when having 3 or more accounts to start, i can simply enter in the settings a delay of 0 sec (after wow gets ingame) for my first account before HB can login, 10 sec for the second account, and 20 sec for the third one.
That way, all wow accounts should start at the same time, but when these accounts enter the game simultaneously, the first one gets an instant HB login, and after 10 seconds passes the second HB account starts, and 20 seconds later the third one follows...
Or better yet, having only one input value in the settings for all your accounts. Like if i type 15 seconds in it, the first HB account starts after 15 sec passes, the timer resets and starts counting another 15 secs for the next HB account and so on...
This should fix the HB login crashes for good hopefully.
FACTS :
- If you launch multiple WOW accounts at the same time or with little delay : usually they all get ingame without causing any problem, and rarely crashes (depending on how many accounts you start and your computer specs or network speed...)
- But if you launch multiple HB windows at the same time or with little delay (like 1 to 8 sec between each instance) : usually you get one or more HB windows to crash at the initialization process.
SUGGESTION 1 :
The first suggestion would be to add in arelog a check for the status of the launched accounts.
If you start 3 accounts at the same time for example, all wow windows can start simultaneously (like how it is working now). But each HB account window need to wait for the previous instance to complete it's loading, by checking the status in arelog.
The first HB window can then start instantly when you get ingame, but the next HB window needs to read and wait for the arelog status of all previous accounts to show "Monitoring" before it can start, so arelog can check in a loop all the launched accounts and while one of these accounts has the status of "Logging in", it waits for that status to change.
SUGGESTION 2 :
If the first suggestion is inaccurate or hard to manage, maybe you can add an option on the settings of each account, like a delay input in seconds.
As a user, when having 3 or more accounts to start, i can simply enter in the settings a delay of 0 sec (after wow gets ingame) for my first account before HB can login, 10 sec for the second account, and 20 sec for the third one.
That way, all wow accounts should start at the same time, but when these accounts enter the game simultaneously, the first one gets an instant HB login, and after 10 seconds passes the second HB account starts, and 20 seconds later the third one follows...
Or better yet, having only one input value in the settings for all your accounts. Like if i type 15 seconds in it, the first HB account starts after 15 sec passes, the timer resets and starts counting another 15 secs for the next HB account and so on...
This should fix the HB login crashes for good hopefully.
Last edited:
I'm experiencing for the first time ever that some of my HB's load up with 0 bots in the dropdown menu.
I then close HB by clicking the cross on the HB window, which used to trigger ARelog to restart it. Now it never restarts.
Attached, log of a malfunctioning HB and log of ARelog.
I then close HB by clicking the cross on the HB window, which used to trigger ARelog to restart it. Now it never restarts.
Attached, log of a malfunctioning HB and log of ARelog.
Last edited:
Bengan12
Well-Known Member
- Joined
- Feb 24, 2011
- Messages
- 1,967
Latest update did not just add 1 minute delay to HB restarts it added a permanent tdelay it just never restarts.
[13:42:04:716] Starting ARelog v1.0.1.9
[13:42:04:716] Succesfully updated to v1.0.1.9
[13:42:09:833] Starting WoW
[13:42:09:985] Waiting for WoW to idle
[13:42:17:140] [PID: 4764] Hooking EndScene and starting Lua
[13:42:23:761] [PID: 4764] Selecting character and entering world.
[13:42:25:829] [PID: 4764] Logged in! Waiting on loading screen.
[13:42:25:829] [PID: 4764] Disposing hooks
[13:42:35:330] [PID: 4764] Starting Honorbuddy
[13:42:43:556] [PID: 4764] Current Task: Botname: Questing - ProfilePath: - Finish Time: 2011-10-08 01:42:09
[13:43:13:565] System.NullReferenceException: Objektreferensen har inte angetts till en instans av ett objekt.
vid (Object )
vid ARelog.Monitor.()
[13:42:04:716] Starting ARelog v1.0.1.9
[13:42:04:716] Succesfully updated to v1.0.1.9
[13:42:09:833] Starting WoW
[13:42:09:985] Waiting for WoW to idle
[13:42:17:140] [PID: 4764] Hooking EndScene and starting Lua
[13:42:23:761] [PID: 4764] Selecting character and entering world.
[13:42:25:829] [PID: 4764] Logged in! Waiting on loading screen.
[13:42:25:829] [PID: 4764] Disposing hooks
[13:42:35:330] [PID: 4764] Starting Honorbuddy
[13:42:43:556] [PID: 4764] Current Task: Botname: Questing - ProfilePath: - Finish Time: 2011-10-08 01:42:09
[13:43:13:565] System.NullReferenceException: Objektreferensen har inte angetts till en instans av ett objekt.
vid (Object )
vid ARelog.Monitor.()
Anyone else can confirm that 1.0.1.9 is working fine for him and did try what i just posted above (Closing HB manually ingame to see if it will launch automatically a new window) ?
Are you sure Dubbelu that you are using the latest version ? i'm not the only one having this problem since the update, but you are the first one to post everything is working fine.
Are you sure Dubbelu that you are using the latest version ? i'm not the only one having this problem since the update, but you are the first one to post everything is working fine.
Yes, it does actually restart HB for me. It takes a minute as it is intended to do.
However, when using the Relogger to start WoW, it keeps giving me an error ("out of sync-bla") sometimes. Might be fixed after a computer restart though, so don't see it as an error report.
However, when using the Relogger to start WoW, it keeps giving me an error ("out of sync-bla") sometimes. Might be fixed after a computer restart though, so don't see it as an error report.
I don't have that problem at all Trippy, wow starts normally and HB too (i'm on win7 sp1 64bit, honorbuddy.exe is set to launch as administrator and Arelog too), but it can't relaunch HB if i close it or if it crashes, it just shows me this error after the log writes starting honorbuddy, this is produced everytime at 100% rate, and i made a new Monitors.xml file to make sure it is not a setting error in the config file.
Here's the error again from the log, i think it is the same as Bengan12 and sadistlex posted before, and i'm sure this has started since the new 1.0.1.9 update :
[1:32:15 PM:639] [PID: 164] Starting Honorbuddy
[1:33:22 PM:712] System.NullReferenceException: Object reference not set to an instance of an object.
at (Object )
at ARelog.Monitor.()
Here's the error again from the log, i think it is the same as Bengan12 and sadistlex posted before, and i'm sure this has started since the new 1.0.1.9 update :
[1:32:15 PM:639] [PID: 164] Starting Honorbuddy
[1:33:22 PM:712] System.NullReferenceException: Object reference not set to an instance of an object.
at (Object )
at ARelog.Monitor.()
Last edited:
Thanks for your answer Dubbelu.
Sadly i have no idea what is exactly going on inside the relogger. Why does it show that error all time for some users and not others ?
I installed all updates on win7 sp1, including the latest .net 3.5.1 updates, i have regional settings set to english and us, tried other countries too, deleted the monitors.xml file and typed the account infos again in the settings. It launches correctly and starts fine, it just never relog an hb account, i waited 10 min and more, the only thing that pops up after closing HB is always this :
[14:00:04:496] System.NullReferenceException: Object reference not set to an instance of an object.
at (Object )
at ARelog.Monitor.()
I beg you Raphus to check this new issue or if you don't have time, just put for us a link of the 1.0.1.7 which was working fine.
It is sad to have such a wonderful relogger working great, and then be forced to use updates that sometimes can cause problems to some users, i hope you understand how we feel about this.
Thanks again for your help and support.
Sadly i have no idea what is exactly going on inside the relogger. Why does it show that error all time for some users and not others ?
I installed all updates on win7 sp1, including the latest .net 3.5.1 updates, i have regional settings set to english and us, tried other countries too, deleted the monitors.xml file and typed the account infos again in the settings. It launches correctly and starts fine, it just never relog an hb account, i waited 10 min and more, the only thing that pops up after closing HB is always this :
[14:00:04:496] System.NullReferenceException: Object reference not set to an instance of an object.
at (Object )
at ARelog.Monitor.()
I beg you Raphus to check this new issue or if you don't have time, just put for us a link of the 1.0.1.7 which was working fine.
It is sad to have such a wonderful relogger working great, and then be forced to use updates that sometimes can cause problems to some users, i hope you understand how we feel about this.
Thanks again for your help and support.
Using the latest 1.019 Same bug. Logs in on the second toon (loop task enabled) and stays there until i close them .
[5:36:02 PM:676] [PID: 4480] Reached end of task. Terminating.
[5:47:59 PM:557] [PID: 328] Reached end of task. Terminating. (nothing happens)
(once this happens If I press close all nothing happens.)