Sorry won't happen again, I just didn't know how to better express myself lol. Edited my post earlier post.
LMAO got banned, dont mess with us botters. (espesially the ones who are stupid enough to bot on their mains)
... why do a botter report other botters?? because he wants to be the botter.. LOL.. .. get it?? me neither... >.> IN OTHER WORDS cheer you got banned man fellow botters dont have to be reported by the same botter comunity, thank you fellow botter chinajade... btw im a botter..
Guys, help, starting hb and he writes Attached to WoW ID 468(or any another) and stucks.... another account works(even another character works), cache was cleared. Log: Code: [09:57:41.175 N] Honorbuddy v2.5.6922.552 started. [09:57:42.536 N] Вхожу... [09:57:45.177 D] Attached To : D3D11 [09:57:45.676 N] Прикрепился к WoW с ID 3632 [09:57:45.944 D] System.TypeInitializationException: Инициализатор типа "Styx.Helpers.CharacterSettings" выдал исключение. ---> System.Xml.XmlException: ".", шестнадцатеричное значение 0x00, является недопустимым знаком., строка 1, позиция 1. в System.Xml.XmlTextReaderImpl.Throw(Exception e) в System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) в System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[] data, Int32 length, Int32 invCharPos) в System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() в System.Xml.XmlTextReaderImpl.ParseDocumentContent() в System.Xml.XmlTextReaderImpl.Read() в System.Xml.XmlReader.MoveToContent() в System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options) в System.Xml.Linq.XElement.Load(String uri, LoadOptions options) в Styx.Helpers.Settings..ctor(String settingsPath) в Styx.Helpers.CharacterSettings..ctor() в Styx.Helpers.CharacterSettings..cctor() --- Конец трассировки внутреннего стека исключений --- в Honorbuddy.MainWindow.LoadSettings() в Honorbuddy.MainWindow.HandleSuccess() --> System.Xml.XmlException: ".", шестнадцатеричное значение 0x00, является недопустимым знаком., строка 1, позиция 1. в System.Xml.XmlTextReaderImpl.Throw(Exception e) в System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) в System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[] data, Int32 length, Int32 invCharPos) в System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() в System.Xml.XmlTextReaderImpl.ParseDocumentContent() в System.Xml.XmlTextReaderImpl.Read() в System.Xml.XmlReader.MoveToContent() в System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options) в System.Xml.Linq.XElement.Load(String uri, LoadOptions options) в Styx.Helpers.Settings..ctor(String settingsPath) в Styx.Helpers.CharacterSettings..ctor() в Styx.Helpers.CharacterSettings..cctor() [09:57:45.944 D] System.TypeInitializationException: Инициализатор типа "Styx.Helpers.CharacterSettings" выдал исключение. ---> System.Xml.XmlException: ".", шестнадцатеричное значение 0x00, является недопустимым знаком., строка 1, позиция 1. в System.Xml.XmlTextReaderImpl.Throw(Exception e) в System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) в System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[] data, Int32 length, Int32 invCharPos) в System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() в System.Xml.XmlTextReaderImpl.ParseDocumentContent() в System.Xml.XmlTextReaderImpl.Read() в System.Xml.XmlReader.MoveToContent() в System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options) в System.Xml.Linq.XElement.Load(String uri, LoadOptions options) в Styx.Helpers.Settings..ctor(String settingsPath) в Styx.Helpers.CharacterSettings..ctor() в Styx.Helpers.CharacterSettings..cctor() --- Конец трассировки внутреннего стека исключений --- в Honorbuddy.MainWindow.LoadSettings() в Honorbuddy.MainWindow.HandleSuccess() --> System.Xml.XmlException: ".", шестнадцатеричное значение 0x00, является недопустимым знаком., строка 1, позиция 1. в System.Xml.XmlTextReaderImpl.Throw(Exception e) в System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) в System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[] data, Int32 length, Int32 invCharPos) в System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() в System.Xml.XmlTextReaderImpl.ParseDocumentContent() в System.Xml.XmlTextReaderImpl.Read() в System.Xml.XmlReader.MoveToContent() в System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options) в System.Xml.Linq.XElement.Load(String uri, LoadOptions options) в Styx.Helpers.Settings..ctor(String settingsPath) в Styx.Helpers.CharacterSettings..ctor() в Styx.Helpers.CharacterSettings..cctor()
There is a lesson in all this. 1st. fix bot. 2nd. add new API's to the beta when release version of the bot runs fine. NOT the other way around.
enjoy your ban on hb reporting other botters is bad and it wil get you banned why you even report botters while youre doing it self let them alone are u jelly on them? that they have more bots then you
I dont mean to annoy any one here, but i am noticing a significant decrease in leveling time with this release, maybe the last one or two releases? I have played for 2 Days and 9 hourish on my 66 Spriest, and i have played for 2 days and 13 hours on my Monk ( 79 ). Here's the thing. My Spriest has 5 Heirlooms and 10% guild XP. My monk only had 10% guild XP. I am using Kick's profiles. Nothing special to either. All default. Any one else noticing this or could it be just circumstance? I just spoke to someone that has played played for 1 day and 19 hours he is level 65. No heirlooms and doing it by hand. -------------- I wonder if the Heirlooms are throwing off the questing? Which is actually making me level more slowly. That seems to be my conclusion, the Profile or Bot isn't responding to the increase in XP that heirlooms are giving? What do you guys think? I noticed i had a quest log full of Terrokar Quest, at level 66, when i should have been in Nagrand. When i restarted honor-buddy and wow, it sent me to Nagrand. Not sure if this is a bug or not, but it DEF seems that Heirlooms are actually SLOWING down the leveling process by several hours.
CustomClass: singular, fpsware, superbad Role: tank, dps Queue Type: random Party Mode: on Dungeon: all of them.. must be a party mode glitch or something.. problem: i get spammed with the code below.. its in red and it doesnt move.. i have deleted tiles, ran in adminstrator, dling bontanist meshes. none of that works. it happens every single dungeon!! i have to x out honorbuddy, and reload for it to work. it happens right after it goes inside the dungeon. it happens to both leader and follower.. sometimes one or the other. and sometimes both. I say XX dung because i been doing 15-68 dungs so far and it keeps giving the same error for every dung except different name. I do have those dungeon meshes dled but it still gives me that error -.-. one simple refresh fixes it, but it really makes it anoying having to babysit it.. dungeonbuddy didnt use to do this
its been 3 months since i last used my bots. today i tried it again downloaded the new update etc but am getting an error while its logging that could no find a file or so, i ve tried downloading it again but still same issue and i have no clue how to fix it
I think it just hit now my bots have been running all nite but were dc 5mins ago then got the ninja patch update. Blizzard is watching
try and keep them up once u dc youre f#ck I cant see them updating anytime soon due to the shutdown of the servers 2nite
Im beginning to think its a blizzard conspiracy to wear out bot developers lol. they have trouble tracking botters in the game if your smart. and even if they catch you another takes your place, or you buy a new account. But, by ninja patching super frequently like all the time. you can make it to where its more of a hassle for developers of bots, if they started patching everyday or even twice a week. or even randomize teh version some how at every log on. no developer would be able to keep up. between us getting pissed its always down and complaining and the constant up keep the developers. would make it either not worth continuing or so expensive for us the consumers wo couldn't justify still buying it. I really do feel for the devs. just about the time you get it going and can relax there's a new patch, i'm sure its frustrating. you all make a great product, keep up the good work Beware the ninja conspiracy. haha
your theories are dumb. there was lots of bugs in 5.2 also users themselves will eventually get psised off at these stupid patches.
