fasmdll_managed.dll . you will need to have that dll in same folder as HBRelog.exe and BlackMagic.dll. It's on the svn in the bin/Release folder. also available on the web
HB will eventually log back in when session times out (3 min timeout I believe) If you attach a log I might be able to figure out why it's crashing.
hmm very strange, The log is complaining that it can't find the fasmdll_managed.dll file. You have .net4 installed right? (off to bed)
Yes, did a repair of the .net4 also. Hmm, when I come to think of it. I do have Win 7 64bit.. Can that be the reason? Sleep tight mate
I'm a bit confused about the "Wait" task. If I set only a "Wait" task with the duration of, let's say 120 minutes, what will the bot do in these 120 minutes if it's the only task set up? Also, as a bug report, if I just set up the task "Wait", enter the Minutes and RandomMinutes then hit the Save and Close button, the task will not have its time saved. Seems that the current task being edited only saves when you add another task. Not sure if that's the proper way to use it or not, as our EU servers are still down... --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Also, another thing: If HBRelog doesn't have a task associated (ie: it is my understanding that if you do that you want to run it 24/7 with the same profile), instead of selecting the proper character on the Login Screen (ie: the one that you set up in the Bot tab), it will log on the previously logged on char.
oh very nice will give this a try later on this day when i have the time to download and configure it ^^ one question, any chance that authenticator support is planned for HBRelog? i would try porting winauth (opensource winauth - World of Warcraft / Battle.net Authenticator for Windows and Windows Mobile - Google Project Hosting) if i had any coding skills
hey... ive got 2 problems with hbrelog. 1st of all there is not much to read in the logfiles... so i describe my 2 problems... 1. in the settigs section windows position. grab current position does not work and there is nothing in the log about this... the 2.) and bigger problem ist that there is a problem with Realms wich have special caracters like" ' " in there name like "abc'def" the log only shows the following PVP: GlueStatus: CharacterSelection PVP: GlueStatus: ServerSelection PVP: GlueStatus: ServerSelection PVP: GlueStatus: ServerSelection PVP: GlueStatus: ServerSelection PVP: GlueStatus: ServerSelection PVP: GlueStatus: ServerSelection PVP: GlueStatus: ServerSelection PVP: Wow has been at server selection for too long, lets restart
I am having a problem with this, but no doubt it is down to me making a stupid error. I have this set up and it will load WoW and log in, launch honorbuddy and start, but even though it says it has chosen the custom class I entered, it will not fight back. It moves towards the NPC but then the CC dose not seam to take over. I tried leaving the field blank and manualy selecting the CC when the window comes up but the same problem happens again. If I launch WoW and honorbuddy myself I dont get this issue though. Any ideas? =) Thanks, EDIT: I just realised I have not followed the OP request and attached an error log, I'll do that when I get home from work.
Can you please add a restart HB function if it's stopped for more than 3 mins? And it would be better to differ HB path loading between PB path loading. And as always, awesome job
Wonder if you could a button to copy previous accounts, this would useful if the location of wow and hb don't change!
Can you add a feature: if you launch HBRelog with -autostart argument, it will start all accounts automaticly on launch.
thanks highvoltz for your time for doing this i have a question how can i edit the time in the Logon Task ? there is no timer there i want to idle for 30 min then log for 2 hours then idle again how can i do it ? Edit: nvm i got this did not read the wait task thingy
A hidden feature, if you select an account and press the 'Add' button it makes a copy of that account.
Checking if HB is actually running is a little bit more complicated then for exampled checking for crashes. I might look into it after if weed out the bugs.
Nope, should work fine on win 7 64 bit. (Wow 32bit client). Thats what I'm using. I'm going to remove the dependency on those 2 dlls
By itself it does nothing. Its used to insert a delay before running the next task below it. Are you putting in decimal values? currently it doesn't support the use of decimals but I might add that. I'll look into it.
