I read through this whole thread doing as you guys telling me to do if I encounter the problems I do, but still I don't go around them. When I'm starting my Honorbuddy.Launcher.exe file and start wow.exe through there the Honorbuddy still doesn't find a valid instance. I removed my 64-bit version .exe file and I have applied correct maps. I'm using the correct build and my client says that it is the x86 release, what can be wrong? Cause I downloaded the EU version, but I'm still having the problems. This is what my Honorbuddy tells me; logfile; Code: [09:37:18.712 N] Honorbuddy v2.5.7861.660 started. [09:37:19.833 N] Logging in... [09:37:21.043 N] ------------------------------- [09:37:21.043 N] You have not selected a valid instance of WoW to attach to! [09:37:21.043 N] Please restart Honorbuddy and choose a valid instance of WoW to use Honorbuddy with! [09:37:21.044 N] This version of Honorbuddy only supports WoW Build #17359 [09:37:21.044 N] You are currently on build #0 [09:37:21.044 N] ------------------------------- [09:38:28.289 D] System.NullReferenceException: Object reference not set to an instance of an object. at Styx.Helpers.Settings.get_CharacterSettingsDirectory() I appreciate any assistance, thanks!
Same as OP, I'm using the Launcher though. Everything updated etc. Correct file locations and settings. Just unsure as to the problem.
When using the HB launcher it opens wow.exe automatically, indeed. Still I'm encountering the same problems.
1. start launcher 2. set paths 3. launch 4. log into the wow-world with your desired char 5. wait 6. once the char is logged in, login to the open HB window
Just trying to minimize the amount of clutter for same problems. I'm just going to follow this thread as a solution is available. But just adding to what appears to be the same problem many people are having at this moment.
Oh dear god, that's the syntax. Okay, I tried to get it all to work without logging in, I did not use Hb for about a year, hence why I'm missing out on these stuff. Thank you both for your fantastic support. You may now close the thread and mark it as solved!
