I just downloaded honorbuddy last night and gave it a try. I had my WoW open and logged into honorbuddy, when it was connecting, WoW had lagged slightly and disconnected as soon as honorbuddy gained connection. I got 2 errors as soon as i disconnected from WoW, 1 was for WoW and the other was for honorbuddy. I clicked dont send for both, later realizing that you said to check off the "ignore this error and attempt to continue" I am not sure if that's the reason why its not working at all for me now because everytime i try to log into honorbuddy it disconnects me from WoW and i can't log back in until i have restarted WoW and closed honorbuddy. I have made sure I am on 32bit and running on directx9 in windowed mode. please help
Heya all! i'm testing this honorbuddy up. i bought cheap 1 day test thingie.. and ive seen few bugs that are bit lamezoer.. :s in alterac valley ( horde side ) it's killing other players.. it's good, but it's always going to sh bunker to "def" even after bunker is burned down.. it still says " going for defend sh bunker" any way to fix that 1 ? and in arathi basin it's killing players as it should.. but but.. again this "defensive" mode is going on it wont leave farm.. it is defending it to very end and from all other players it's bit suspicious if im standing there like 15 min x) Eots- same def bug defending Belf tower nothing else.. but this far i havent seen any other bugs and yeah..! after its defending in bgs.. i maybe get D/c once or twice. If some1 more professional can help me fix this.. you'r welcome! ( and cant get leveling thing working, but bg's+instances will do)
Tony thank you.i installed netframework and there is no error now.but my HB simply doesnt starts now. in log file it writes [15:12:02:955] System.Windows.Markup.XamlParseException: Не удается найти DependencyProperty или PropertyInfo для свойства с именем "Uid". Имена свойств определяются с учетом регистра. Ошибка в объекте "Window" из файла разметки "Honorbuddy;component/mainwindow.xaml". в System.Windows.Markup.XamlParseException.ThrowException(String message, Exception innerException, Int32 lineNumber, Int32 linePosition, Uri baseUri, XamlObjectIds currentXamlObjectIds, XamlObjectIds contextXamlObjectIds, Type objectType) в System.Windows.Markup.XamlParseException.ThrowException(ParserContext parserContext, Int32 lineNumber, Int32 linePosition, String message, Exception innerException) в System.Windows.Markup.BamlRecordReader.ThrowException(SRID id, String parameter) в System.Windows.Markup.BamlRecordReader.ReadPropertyRecordBase(String attribValue, Int16 attributeId, Int16 converterTypeId) в System.Windows.Markup.BamlRecordReader.ReadPropertyConverterRecord(BamlPropertyWithConverterRecord bamlPropertyRecord) в System.Windows.Markup.BamlRecordReader.ReadRecord(BamlRecord bamlRecord) в System.Windows.Markup.BamlRecordReader.Read(Boolean singleRecord) в System.Windows.Markup.TreeBuilderBamlTranslator.ParseFragment() в System.Windows.Markup.TreeBuilder.Parse() в System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream) в System.Windows.Application.LoadComponent(Object component, Uri resourceLocator) в Honorbuddy.MainWindow.InitializeComponent() в Honorbuddy.MainWindow..ctor() [15:12:02:962] System.Windows.Markup.XamlParseException: Не должно быть вложенных вызовов BeginInit для одного и того же экземпляра. Ошибка в файле разметки "Honorbuddy;component/MainWindow.xaml". ---> System.InvalidOperationException: Не должно быть вложенных вызовов BeginInit для одного и того же экземпляра. в System.Windows.FrameworkElement.BeginInit() в System.Windows.Markup.BamlRecordReader.ElementInitialize(Object element, String name) в System.Windows.Markup.BamlRecordReader.BaseReadElementStartRecord(BamlElementStartRecord bamlElementRecord) в System.Windows.Markup.BamlRecordReader.ReadElementStartRecord(BamlElementStartRecord bamlElementRecord) в System.Windows.Markup.BamlRecordReader.ReadRecord(BamlRecord bamlRecord) --- Конец трассировки внутреннего стека исключений --- в System.Windows.Markup.XamlParseException.ThrowException(String message, Exception innerException, Int32 lineNumber, Int32 linePosition, Uri baseUri, XamlObjectIds currentXamlObjectIds, XamlObjectIds contextXamlObjectIds, Type objectType) в System.Windows.Markup.XamlParseException.ThrowException(ParserContext parserContext, Int32 lineNumber, Int32 linePosition, String message, Exception innerException) в System.Windows.Markup.BamlRecordReader.ReadRecord(BamlRecord bamlRecord) в System.Windows.Markup.BamlRecordReader.Read(Boolean singleRecord) в System.Windows.Markup.TreeBuilderBamlTranslator.ParseFragment() в System.Windows.Markup.TreeBuilder.Parse() в System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream) в System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc) в MS.Internal.AppModel.AppModelKnownContentFactory.BamlConverter(Stream stream, Uri baseUri, Boolean canUseTopLevelBrowser, Boolean sandboxExternalContent, Boolean allowAsync, Boolean isJournalNavigation, XamlReader& asyncObjectConverter) в MS.Internal.AppModel.MimeObjectFactory.GetObjectAndCloseStream(Stream s, ContentType contentType, Uri baseUri, Boolean canUseTopLevelBrowser, Boolean sandboxExternalContent, Boolean allowAsync, Boolean isJournalNavigation, XamlReader& asyncObjectConverter) в System.Windows.Navigation.NavigationService.GetObjectFromResponse(WebRequest request, WebResponse response, Uri destinationUri, Object navState) в System.Windows.Navigation.NavigationService.DoNavigate(Uri source, NavigationMode f, Object navState) в System.Windows.Navigation.NavigateQueueItem.Dispatch(Object obj) в System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter) в System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
i use hb for quest lvl with fpsware paladin cc with all plugin enable but when it come to certain level HB keep saying goal : grinding to level 37 so i must manually grinding / quest to level it need to continue quest bot :| how can i solve this problem
The bot should start to grind by it self to level 37, the goal is not for you. if it dosn?t start to grind it might be calculating a path to a new area or an error should appear.
uhm could u explain this code ??? <GrindTo Level="40" /> <!-- EPL --> <Checkpoint Level="40" /> i don't understand the difference between grind to level and check point level i'll modify the level to make it flawessly
uhm i don't like the check point and grinding if u can please make an automatic system which realize and do for us the missing level --> full auto not grinding only quest
http://www.thebuddyforum.com/honorb...uest-1-58-kalimdor-eastern-kingdoms-kick.html should be quest only - without grinding. when starting this profile after lvl 16+ change <QuestOrder IgnoreCheckPoints="True" > -- True to False (hint: open the profile in notepad & 'find' ) in the [H - Quest] 12-58 K-EK [Kick] xml file.
Hi! I've been using Honorbuddy for the last day or two and my Druid went from 1-34. Very impressive! However I've noticed that there are certain points where it seems to be having issues completing/picking up quests. I tried the fixes for "Erratic Behaviour" on the FAQ (namely, disabling my AV), but that did nothing, and I can't find the "installer workaround" file that the other solution talks about. So, here I am to ask for help Now, I know you guys want the logs, but the log file is too big to attach and I don't want to delete anything in case I delete what you need to see. So, please download the .txt file here. Cheers!
Live Support will be offline for the rest day today 14/4 and also will be offline at 15/4 and 16/4 (Orthodox Easter)
Having no luck getting honorbuddy to work at all, since i paid 30 euros for it, emailed support 4 times and all i got was follow this link to installing HB, which i've already done a 1000 times, at the point of giving up, even had friends who use honor buddy to try and help and they have no idea either. Tried the latest version .5872, friends are using 5800 and its working even after wednesdays wow patch. Instead of getting my previous message saying i'm using the wrong wow, i'm now just getting constant authentication failed! Big sigh!
