So I keep running into an issue where honor buddy seems to just stop working. I have noticed when it goes to harvest a quest item it will harvest a few then stop and just stand there. Even if a mob attacks it will not defend. I noticed if I stop the bot and try to restart it. It will not restart. The log is not showing anything because honor buddy hangs up when I try to restart it. I have noticed this seems this is a common issue and has made botting nearly impossible for more then 30 mins at a time. Any idea what would be causing this? I have done a fresh install of honor buddy and the issue still exists. I just don't know what to do. Sent from my SM-N900T using TheBuddyForum mobile app
View attachment 121350 Here is a log of it happening last night. I logged in, started the bot, it ran around stopped at a node to harvest an item for a quest and then stopped. I saw this happen so i stopped the bot and then restarted it. The start button grayed out as if it was trying to start but it never did. I cant find a log of it trying to start back up. Eventually wow just logs out. I have also noticed honorbuddy is using quite a bit more memory then normal. Normally its around 180-240 megs of memory but when the thing happens that i just described HB is using 500-700 megs of memory. The memory issue really isnt an issue to me since i have 32 gigs of memory but I think it might have something to do with whats going on.
View attachment 121351 Here is another instance of it doing again. The bot just randomly stops moving and does nothing. A mob attacked me and the bot does not defend at all. I stopped it and tried to restart and again its broke. Here is a picture as well: View attachment 121352
I have also been getting this error when i try to log in to the original install of HB. [23:15:18.333 N] Honorbuddy v2.5.9775.726 started. [23:15:19.600 N] Logging in... [23:15:20.906 N] Attaching to D3D11 [23:15:21.091 N] Error attaching Honorbuddy to WoW! - System.TypeInitializationException: The type initializer for 'Styx.Helpers.CharacterSettings' threw an exception. ---> System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1. at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[] data, Int32 length, Int32 invCharPos) at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() 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 Styx.Helpers.Settings..ctor(String settingsPath, String oldSettingsPath) at Styx.Helpers.CharacterSettings..ctor() at Styx.Helpers.CharacterSettings..cctor() --- End of inner exception stack trace --- at Styx.Helpers.CharacterSettings.() at Styx.StyxWoW.() at Styx.StyxWoW.(Process , GraphicsApi ) at Honorbuddy.MainWindow.FindAndAttachToWoW(Boolean& found64Bits) [23:15:23.518 N] Wow is a 32 bit version, yes i have checked and verified. If i open the clean installed one that I made a few days ago HB attaches just fine but if I open the original install it throws that error.
I believe it is an issue with BuddyCon. I was experiencing the same problems. Disabled buddycon and everything works fine. Give that a go.
I have been disabling the plug in one by one to see if it improvesm Sent from my SM-N900T using TheBuddyForum mobile app
Yes I deleted the settings folder and the problem still existed. I found after i deleted mr item remover 2, the problem seemed to go away. I think what was happening had something to do with it checking if it needed to sell or not. I just start a lvl 85 to quest up to lvl 90. I will report back if it runs properly or not.
Seems to be doing ok now once I disabled MIR2 and buddycon. I am really hoping buddycon gets an update or fixed because its a great plugin for detection prevention. I have gotten this error a few times: Bot stopping! Reason: Could not create current in quest bot! View attachment 121586 Not sure if its a profile issue or not. using cava's profiles.
its an issue that the devs are working on. just complete the quest manually then start the bot again.
