Ok I have to wonder, we already have arelog which is working fine but with some bugs. Why make a completely new relogger instead of simply helping perfect the one we already have and everyone already uses?
Arelog is close sourced and I had made this reloger before Arelog was release, though I did a complete redo recently and fixed it up when my internet connection was terrible (hourly disconnects), and Arelog couldn't login my character because of a letter that it was using in its name. And I needed wanted an excuse to play with WPF
Yes, it always loops infinitely. I can't think of a situation when this wouldn't be the desired effect but one could always place a 'Wait' task at the bottom of the task list with an insane long duration too
I wanted the infinite loop part. Thanks for this and answering my questions so quick. Donating tomorrow when i have some money in my paypal.
How would I, if i even can, set this up to be used with Felmaster, where there is a secondary radio button after selecting the CC, to chose which FelMaster profile?
Just Tested it Just Tested it and it works perfectly!!!! Thanks for the Awesome Job! 2 Little BUGS I found: 1 - In the activies, when you try to click the random time text box(not selecting the text, just clicking the text box to edit it), it crashes if you press the delete key 2 - I've tried to stop the reloger(stop button) and it succecefuly closed wow+honorbuddy. But After I started it again, I got a MAX Sessions information(like if If the bot process was terminated without sending the logoff command to the server). This second issue is no big issue, because if you program an iddle activity long enough to expire the honorbuddy session, you'll be ok. PS - I've tried it on my 64 bit laptop and it didn't work. It gets an exception (when injecting BM, maybe?). I didnt had the time to test it to run in alternate compatibility modes. Will test tomorrow and give feedback. Here is the current log on the X64 machine: Code: This application has encountered a critical error: ERROR #132 (0x85100084) Fatal exception! Program: D:\play\World of Warcraft\Wow.exe ProcessID: 6580 Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:6FCD2E55 The instruction at "0x6FCD2E55" referenced memory at "0x088B0440". The memory could not be "written". WoWBuild: 15211 Version: 4.3.2 Type: WoW Platform: X86 Settings:
Won't login for me. It fires up WoW, repositions the window properly, then WoW just says "Connecting" endlessly. Windows 7 x64 - x86 WoW client.
Mine is crashing as well when tying to remove the 0 value from any time box. The workaround I have is to place your mouse pointer in front of the 0 and enter in a value which includes the 0. Will be testing this out more in the next day.
1) Is now fixed on SVN 2) This will sometimes happen from my experience. If I can figure a way to prevent this I'll add it. When you get the time could you attach a log from the laptop? When did the exception happen, Before wow load?,after WoW loaded?, when logging into game?
I have an ehancement request the abilitiy to choose a different hb path when you add a logon condition. Sometimes when you switch characters, it would be nice to use a different hb path to avoid loading certain plugins. I know i can create an entire new profile to do this but i want to be able to swap through multiple characters and hb installs on a single profile.
Revision 12: Logon Task now has the option to choose a different Honorbuddy Path edit : Rev 13: The HonorbuddyPath file selector dialog should now display .exe files instead of .xml.
Mine just crashes about 10 sec after the first wow window is open. Could you see what im missing from the log?
Question. So if wow crashes then honorbuddy says max sessions reached. So what do i set to make it wait before starting wow/honorbuddy again after the crash? I put idle on 2 min and when i hit start when it logged in it randomly exited.
