Cant run the latest version of HBRelog! And I was using it just fine like 10 minutes ago, but closed it. Now when I use it I get this error: (The only text in the log file) Code: [3/2/2012 8:42:46 AM] System.Xml.XmlException: Root element is missing. at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.ParseDocumentContent() at System.Xml.XmlTextReaderImpl.Read() at System.Xml.XmlReader.MoveToContent() at System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options) at System.Xml.Linq.XElement.Load(String uri, LoadOptions options) at HighVoltz.HBRelog.Settings.GlobalSettings.Load() at HighVoltz.HBRelog.HBRelogManager..cctor() I've done 3 fresh installs in different folders of my computer and on desktop, but still nothing. Any help?
My guess is the settings file got corrupted. I would close HBRElog and delete or rename the settings file (which is found at %APPDATA%\HighVoltz\HBRelog\Setting.xml)
If both the bot path and the profile remains the same path, I have to specify under "tasks" to logon again the paths? Some of the paths in the tool saves me not at "tasks", so HB dont start the profile...
HBRelog isn't working properly idk why :/ I just wake up to a pc with wow instances open but normal sized, not connected and in the middle of the screen, sometimes I find launcher.exe open idk why. And when I select all on HBRelog and make it stop, it doesn't kill the wow windows, so I guess he just "lost" them or something. The first night I used HBrelog (2 or 3 days ago) it was perfect :/ The log is full of: Full log View attachment Log[2012-03-02_12-33-48].txt
Found something curious, when He's starting WoW after an idle it opens up two wow instances, that should be the problem! Code: 20:21:26] [20:21:28] Blackrock1: starting C:\WoWUS\World of Warcraft\Wow.exe [20:21:28] Blackrock1: Idle complete [20:21:29] Blackrock1: Logging on different character. [20:21:29] Blackrock1: starting C:\WoWUS\World of Warcraft\Wow.exe [20:21:32] Blackrock1: Installing Endscene hook [20:21:32] Blackrock1: GlueStatus: Disconnected [20:21:33] Blackrock1: Setting Window location to X:582, Y:300 and Size to Width 336, Height:292
[21:50:38:810] Starting ARelog v1.0.3.4 [21:50:38:913] Checking for updates. [21:50:39:639] ARelog is up-to-date [21:50:46:598] Starting WoW [21:50:46:644] Waiting for WoW to idle [21:50:51:942] [PID: 11648] Moving WoW Window to: 311, 133 - With size: 1298x765 (here it makes wow crash for some reason) [21:51:22:491] [PID: 11648] Restarting WoW + Buddy Edit: Woops, this was with ARelog... Still same problem though.
My HBRelog doesn't seem to like the Realm status feature, it opens wow, but won't log in at all. It seems that HTML: http://www.battle.net/api/wow/realm/status?realms= diverts to http://sea.battle.net/en/api/wow/realm/status?realms= in my location so it probably can't be fixed unless a setting for both EU or US is added with a separate URL for each. HTML: http://us.battle.net/api/wow/realm/status?realms= and http://eu.battle.net/api/wow/realm/status?realms= as these both work if I type them into the browser manually. It logs in okay when the setting is disabled. Also, if wow wants me to enter in my authenticator code the wow window stays blank with just the deathwing animation playing in the background, the box for the authenticator doesn't appear. if i stop HBRelog and manually log in then I can see the code box again, any chance we can have HBRelog wait and let the user enter the authentication code if prompted. Log is below for both problems. Also attached screenshot of what the wow window I'm describing looks like compared to what it should be doing. View attachment log.txt
highvoltz, HBRelog is still buggy, lot's of wow windows opening up that aren't used, that end up by slowing the pc until nothing runs anymore. Launcher opens also :/ Ps: I have last svn, from sunday.
"D:\#1\Kick's Profiles\1-85 Questing Profile Pack\Classic\[A - Quest] 1-58 [Kick]\[A - Quest] EK 12-58 [Kick].xml" Code: [01:20:33] [L]: Login sequence complete. Removing hook [01:20:40] [L] : starting C:\Users\Andy\Desktop\Kunden\HonorBuddy\HB\Honorbuddy.exe [01:20:41] [L] : Waiting for 0 minutes before executing next task [01:20:41] [L] : Wait complete [COLOR="#FF0000"][B][01:20:42] [L] : Unable to find profile [/B][/COLOR] [01:20:44] [L] : Idling for 0 minutes before executing next task [01:20:44] [L] : starting C:\World of Warcraft\Wow.exe [01:20:44] [L] : Idle complete [01:20:44] [L] : Logging on different character. With ARelog the Path works Perfect...
Profiles can now select a Wow region e.g. US,EU,China or Auto(default). This is used to check for server status. If a Logon Task follows an Idle Task then 2 Wow instances should no-longer get spawned.