What Class+Spec are you?: Druid Feral What 'context' is the bot in? Questing What level are you?: 96 (90-100) Have you made any modifications to Singular?: No What time (HH:MM:SS) or LogMark did your issue occur? [02:46:10.285 N] What happened (be specific)? Sometimes bot stuck for a minute or less before killing a mob pack (02:46:10.285 - 02:47:08.903), and instead of use AOE he killing one mob at once. If bot stucks before attack then with 50% chance will do nothing after killing, till gone afk and logout... Did you attach a complete debug log? Yes View attachment 3380 2016-07-26 12.44.txt
Hey all, Just updated to the newest version, and now what happens is that in the BgBuddy profile, my resto druid just sits there, doesn't move, will randomly cast Bark skin, but nothing more than that. Any ideas as to why? If the bot dies itll just afk in the graveyard until it get deserter - no addons enabled. So sorry if I keep adding more replies, just don't know how to directly to reply to someone - also, sorry if the ZIP file was done incorrectly...just a noob trying to fix his HB problems, thanks for the help - hopefully the log this time was up to snuff.
Singular problems with incoming heals... Hi, all, We've updated the Honorbuddy v2.6.15573.831 Known Issues list... Raphus has identified a bug in Singular when analyzing incoming heals in certain situations. The result is Singular will quit working, and your log will quickly fill up with entries like the following: [06:50:36.856 D] System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000000, Size: 160 at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count) at GreyMagic.MemoryBase.ReadArray[T](IntPtr addr, Int32 count) at Styx.WoWInternals.WoWObjects.WoWUnit.IncomingHealsArray() at Styx.WoWInternals.WoWObjects.WoWUnit.GetPredictedHealth(Boolean includeMyHeals) Since 'incoming heals' are more likely to happen in Battlegrounds, we expect those users will encounter the problem much more frequently than other uses of the bot. There is no solid work-around for this, and it will take another Test Release to resolve the issue. You might try changing activities (e.g., questing instead of battlegrounds), or changing classes (preferably one without explicit healing abilities. ). The issue is being worked. [26-Jul-2016 UPDATE]: ==> This problem is believed to now be repaired by simply restarting Honorbuddy. cheers, chinajade
soooooooooooo lol we have to buy custom routines now? only 4 CR's optioned now....even with legionbuddy we cant use it with HB 32 vs 64
enhacement shitting al over the place [04:22:33.118 D] Exception was thrown in BotBase.Root.Tick [04:22:33.119 D] Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000000, Size: 40 at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count) at GreyMagic.MemoryBase.ReadArray[T](IntPtr addr, Int32 count) at Styx.WoWInternals.WoWObjects.WoWUnit.IncomingHealsArray() at Styx.WoWInternals.WoWObjects.WoWUnit.GetPredictedHealth(Boolean includeMyHeals) at Styx.WoWInternals.WoWObjects.WoWUnit.GetPredictedHealthPercent(Boolean includeMyHeals) at Singular.Extensions.PredictedHealthPercent(WoWUnit u, Boolean includeMyHeals) in D:\Blizzard\HelperII\Routines\Singular\Extensions.cs:line 258 at Singular.Helpers.Rest.<>c.<CreateDefaultRestBehaviour>b__8_16(Object ret) in D:\Blizzard\HelperII\Routines\Singular\Helpers\Rest.cs:line 135 at Styx.TreeSharp.Decorator.CanRun(Object context) at Styx.TreeSharp.Decorator."_l(MvoiJu\,J$=-oD6(NkH_e.MoveNext() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.PrioritySelector.>_o7Sj90e|J:;\[T'zM"bd$cw!.MoveNext() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.Decorator."_l(MvoiJu\,J$=-oD6(NkH_e.MoveNext() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.PrioritySelector.>_o7Sj90e|J:;\[T'zM"bd$cw!.MoveNext() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.PrioritySelector.>_o7Sj90e|J:;\[T'zM"bd$cw!.MoveNext() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.Decorator."_l(MvoiJu\,J$=-oD6(NkH_e.MoveNext() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.PrioritySelector.>_o7Sj90e|J:;\[T'zM"bd$cw!.MoveNext() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.PrioritySelector.>_o7Sj90e|J:;\[T'zM"bd$cw!.MoveNext()
Beast Mastery can't load Singular normally. [07:12:04.001 N] (Singular) No spells blocked by DisableSpellsWithCooldown [07:12:03.889 D] System.ComponentModel.Win32Exception (0x80004005): Invalid access to memory location at GreyMagic.ExternalProcessMemory.***********(IntPtr , Void* , Int32 , Int32& ) at GreyMagic.ExternalProcessMemory.ReadString(IntPtr address, Encoding encoding, Int32 maxLength) at Styx.WoWInternals.DB.WoWDbRow.GetStringField[T](String fieldName) at Styx.WoWInternals.WoWObjects.ItemInfo..ctor(UInt32 id, String itemString, WoWDbRow sparseInfoBlock, WoWDbRow classInfoBlock) at Styx.WoWInternals.WoWObjects.ItemInfo.FromLink(String link) at Styx.WoWInternals.WoWObjects.WoWItem.get_ItemInfo() at Singular.Helpers.Item.IsItemImportantToGearScore(WoWItem item) in C:\Honorbuddy\Routines\Singular\Helpers\Item.cs:line 709 at Singular.Helpers.Item.CalcTotalGearScore() in C:\Honorbuddy\Routines\Singular\Helpers\Item.cs:line 660 at Singular.Helpers.Item.WriteCharacterGearAndSetupInfo() in C:\Honorbuddy\Routines\Singular\Helpers\Item.cs:line 488 at Singular.SingularRoutine.DescribeContext() in C:\Honorbuddy\Routines\Singular\SingularRoutine.Context.cs:line 349 at Singular.SingularRoutine.UpdateContext() in C:\Honorbuddy\Routines\Singular\SingularRoutine.Context.cs:line 195 at Singular.SingularRoutine.Initialize() in C:\Honorbuddy\Routines\Singular\SingularRoutine.cs:line 162 at Styx.CommonBot.Routines.RoutineManager.set_Current(CombatRoutine value) [07:12:50.318 N] (Singular) Initialize: started [07:12:50.347 D] System.ArgumentException: This handler has already been attached to this event Parameter name: handler at Styx.WoWInternals.LuaEvents.AttachEvent(String eventName, LuaEventHandlerDelegate handler, String filter) at Styx.WoWInternals.LuaEvents.AttachEvent(String eventName, LuaEventHandlerDelegate handler) at Singular.Managers.TalentManager.Init() in C:\Honorbuddy\Routines\Singular\Managers\TalentManager.cs:line 33 at Singular.SingularRoutine.Initialize() in C:\Honorbuddy\Routines\Singular\SingularRoutine.cs:line 76 at Styx.CommonBot.Routines.RoutineManager.set_Current(CombatRoutine value) [07:16:40.560 N] (Singular) Initialize: started What Class+Spec are you?: Hunter Beast Mastery What 'context' is the bot in? Questing What level are you?: 100 (90-100) Have you made any modifications to Singular?: No What time (HH:MM:SS) or LogMark did your issue occur? Each time you start HB. What happened (be specific)? Beast Mastery can't load Singular normally. "We have determined multiple custom classes for your current character class."
Another problem that sometimes if the pack of mobs is too big the bot don't use aoe and singular write next: [DoWhen-v$Rev$(debug)] Executing MoveDefHook hook [DoWhen-v$Rev$(debug)] Stopped executing MoveDefHook hook [Singular] Switching to BotPoi: Bellows Slave.D42D! [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] Combat, Pull Target Bellows Slave.D42D out of range/line of sight for 20.0 seconds, blacklisting for 00:00:20 and clearing BotPoi [Singular] CurrentTarget Bellows Slave.D42D blacklisted and not in combat with so clearing target! And stuck. Druid Feral 93 LV.
Another problem that sometimes if the pack of mobs is too big the bot don't use aoe and singular write next: [DoWhen-v$Rev$(debug)] Executing MoveDefHook hook [DoWhen-v$Rev$(debug)] Stopped executing MoveDefHook hook [Singular] Switching to BotPoi: Bellows Slave.D42D! [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] Combat, Pull Target Bellows Slave.D42D out of range/line of sight for 20.0 seconds, blacklisting for 00:00:20 and clearing BotPoi [Singular] CurrentTarget Bellows Slave.D42D blacklisted and not in combat with so clearing target! And stuck Druid 93 LV Also Aoe Atack not always work correct. Sometimes Bot AoE mobs sometime killing them by target.
After 7.03 Update HB (questing) skip loot. For example, if there is 2 packs(in different wow loot range area (30 + yard i think), he go to loot 1 pack and the another just passing through. Another problem that sometimes if the pack of mobs is too big the bot don't use aoe and singular write next: [DoWhen-v$Rev$(debug)] Executing MoveDefHook hook [DoWhen-v$Rev$(debug)] Stopped executing MoveDefHook hook [Singular] Switching to BotPoi: Bellows Slave.D42D! [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] MoveToSide: moving diagonally Left for 2.5 yds (stuck for 2- 3 sec) [Singular] Combat, Pull Target Bellows Slave.D42D out of range/line of sight for 20.0 seconds, blacklisting for 00:00:20 and clearing BotPoi [Singular] CurrentTarget Bellows Slave.D42D blacklisted and not in combat with so clearing target! And stuck. I think it is not a profile problem, cause the was 829 HB build all was ok. + Druid feral sometimes come to mobs and waiting for 10-15 sec and then attack them Log to all this problems View attachment 204862
'Incoming Heals' issue may be repaired by simply restarting Honorbuddy... MaiN indicates the 'incoming heals' problem should be repaired by simply restarting Honorbuddy. cheers, chinajade
Confirmed works in same dungeon (just running Dungeonbuddy at the moment), will report + edit this thread after next dungeon if it continues working or breaks, in any case. EDIT: Winner WInner chicken dinner, it works.... for the next dungeon as well, this suits my needs, I assume the same restart process needs to be applied when wow is restarted (even if you have a relogger) 2nd EDIT: I got to excited too fast, getting index out of bounds exception, it ALMOST completed entire stockades, and this is a new error along with the memory one.
There was another problem that should now be fixed - another restart of HB should resolve it for most cases.
Hey after update everything seems to work for me in. I was just wondering is it possible to make the bot use earth shock in elememtal after you reach a certain maelstrom?
Has anyone tried Guardian Druid? It appears to be working fine except it wasn't dumping my rage with Ironfur even when at low health. Wow went down before I had time to do any proper logs, so I was just curious if anyone else noticed that. After it comes back up I will post the logs and see what it's doing.