chinajade
Community Developer
- Joined
- Jul 20, 2010
- Messages
- 17,540
Good Morning!
First of all I'd like to explain that I am new to honorbuddy. I have successfully launched and configured everything from my understanding. I've been searching through the threads as to what might be causing this issue but ultimately I might need some insight.
I am going through the common issue of a profile starting and continuously interacting with an NPC to get a quest it already has, to remedy this I followed the deleting cache method to no conclusion. I have also gone through my drivers and all are up to date. Another thing to note is I am using the BETA client of honorbuddy, latest release. I'm not overly positive what Kicks profiles policy is on supporting the beta releases.
Attached you will find me log, please let me know if I have done this correctly.
First error reads at [14:26:14.151 D] for a quick search.
Thank you for the support.
***EDIT***
After further investigation and looking at the beta forums users problems logs I have determined this is likely to do specifically with the beta build. If you could confirm this that would be awesome, otherwise disregard the edit. Thank you.
Hi, Alexlaw, and thanks for the log!
From your log, we see a *lot* of these...
[14:26:14.151 D] System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.AccessViolationException: Could not read bytes from FFFFFFFF [299]!
at Styx.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Styx.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Styx.WoWInternals.WoWObjects.UnitThreatInfo.( , UInt32 , UInt64 , IntPtr& )
at Styx.WoWInternals.WoWObjects.UnitThreatInfo.(WoWUnit , WoWUnit )
at Styx.WoWInternals.WoWObjects.WoWUnit.GetThreatInfoFor(WoWUnit otherUnit)
at Styx.WoWInternals.WoWObjects.WoWUnit.get_ThreatInfo()
at Styx.WoWInternals.WoWObjects.WoWUnit.get_Aggro()
at Styx.CommonBot.Targeting.DefaultRemoveTargetsFilter(List`1 units)
at Styx.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Styx.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Styx.WoWInternals.WoWObjects.UnitThreatInfo.( , UInt32 , UInt64 , IntPtr& )
at Styx.WoWInternals.WoWObjects.UnitThreatInfo.(WoWUnit , WoWUnit )
at Styx.WoWInternals.WoWObjects.WoWUnit.GetThreatInfoFor(WoWUnit otherUnit)
at Styx.WoWInternals.WoWObjects.WoWUnit.get_ThreatInfo()
at Styx.WoWInternals.WoWObjects.WoWUnit.get_Aggro()
at Styx.CommonBot.Targeting.DefaultRemoveTargetsFilter(List`1 units)
This could be a lot of things--hardware problem, running HB the WoWclient without Windoze Admin privileges, a problem with the HB beta, etc.
Your problem is not a profile issue. Even if it was, Beta builds are not supported. Normally, we'd ask you to post your problem in the Support forum, but the Support forum won't provide help with Beta releases, either.
I believe for now, you're just going to have to sit tight and wait for the next Honorbuddy release. (And "no", we don't have a timeframe when this will happen.) As, the Beta is still working through the wrenches thrown by the 5.2 WoWclient update. If you still have problems after the next release then please follow up to the Support forum.
We know this is inconvenient, but you've joined the Community during a patch recovery period which is the absolute worst time to start having fun with Honorbuddy.

cheers & welcome aboard,
chinajade