Converted InteractWith (not great for farming for an item to use) to GrindUntil. Should more effectively seek item it needs. Will be in release .21
Looks like issues with capability of downloading mesh files from the HB server, and issues with GreyMagic.dll, one of HBs libraries. Recommend a fresh install.
Forced Dismount before item use was missing from InteractWith for this quest. Was added and will work from here on (release .21)
Quest its trying to pick up becomes unobtainable if you have done any of the quests after it. A check for the followup has been placed in (release .21) however, it may have to be more verbose than that, since ANY quest after this point will negate this quest.
Known issue with WoW is that achievements for accounts containing more than 1 character may report true/false incorrectly, this stating you don't have an achievement done when in fact you do, or vice versa. This issue can be temporarily fixed by doing a full cache clear as stated on page 1, however the issue will resurface on next loading screen (zoning to another continent or something instance, changing characters, /reloadui). This bug does not affect everyone, but seems to be becoming a larger scale issue as time passes. First noted issues date back to mid-LK expac. Unfortunately I have no workaround for this short of removing all achievement checks and having the bot run through every quest 1 by 1, which fully defeats the purpose of profile selection automation. Check your achievement panel. Do you have the achievement? If yes, confirm it says that you are done by checking: 1) does the quest counter show completed? 50/50 is done, 2/50 is not even if it says you're done. 2) does the achievement say "not earned by..." And name your current character? If the achievement is not done yet, and you are at something like 1 quest missing, then that's different. I've had to remove several quests due to people skipping quests during leveling, and thus making these quests unobtainable. Please let me know if you have the achievement or not, AND what the quest tracker on the achievement says, regardless of having it or not.
Because of the achievement bug, it's not really working. It still would be nice to have, and it would fix the bug, kind of.
Looks like there is a bug in swamp of sorrows? Wow crashes and says it is out of memory. Here is the log: [01:44:50.329 D] System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 3880B01C, Size: 4 at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count) at GreyMagic.MemoryBase.Read[T](IntPtr addr) at Styx.WoWInternals.WoWObjects.WoWObject.[](UInt32 ) at Honorbuddy.MainWindow.StartStop(String stopReason) at Honorbuddy.MainWindow.btnStop_OnClick(Object sender, RoutedEventArgs e) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args) at System.Windows.UIElement.RaiseEvent(RoutedEventArgs e) at System.Windows.Controls.Primitives.ButtonBase.OnClick() at System.Windows.Controls.Button.OnClick() at Styx.Common.WpfControls.SplitButton.OnClick() at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e) at System.Windows.UIElement.OnMouseLeftButtonUpThunk(Object sender, MouseButtonEventArgs e) at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget) at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent) at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e) at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget) at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args) at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args) at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted) at System.Windows.Input.InputManager.ProcessStagingArea() at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input) at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport) at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel) at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler) [01:44:54.703 N] (Singular) (Singular) info: 15.3 seconds since BotBase last called Singular (now in OnBotStopped) [01:44:54.684 D] Exception in DoString: Process must have frozen or gotten out of sync: InjectionFinishedEvent_was_never_fired StackTrace: at GreyMagic.Executor.WaitForInjection(Int32 timeout) at GreyMagic.Executor.Execute(Int32 timeout) at GreyMagic.Executor.Execute() at Styx.WoWInternals.Lua.DoString(String lua, String luaFile, IntPtr pState) [01:44:54.685 D] Activity: RunLua: UseItemByName(27587) 1 number of times while waiting 2000 inbetween [01:44:54.685 D] Goal: RunLua-v1728: In Progress (no associated quest) [Ref: "Swamp of Sorrows Memory Block ($Rev: 32 $)" @line 142] [01:44:54.692 D] Activity: Honorbuddy Stopped [01:44:54.698 D] Handler for OnBotStopped threw exception! [01:44:54.700 D] System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00F45CE0, Size: 4 at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count) at GreyMagic.MemoryBase.Read[T](IntPtr addr) at Styx.WoWInternals.Lua.get_State() at Styx.WoWInternals.LuaEvents.() at Styx.WoWInternals.LuaEvents.(EventArgs ) --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.UnsafeInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.Delegate.DynamicInvokeImpl(Object[] args) at System.Delegate.DynamicInvoke(Object[] args) at Styx.CommonBot.BotEvents.(Delegate , Action`1 , Object[] ) [01:44:55.073 N] [ANIMUS] Deactivation Complete
It would "fix the bug" by forcing a check of all quests, and removing automation. I don't have any intention of reconstructing the framework at this time. Mostly because this would be the third reconstruction due to the need of half the users. When I redid it last time, it appeased the other half, but then brought up issues for the rest.
i just purchased this profile a few days ago. But since i saw this is still work on progress, does that means we just have to wait till it release? or we can use it as far as its goes?
[Profile Message]: Caution! Due to the underwater nature of this zone, AFK is not recommended! 达成目标: Picking Up Quest - 前往西岸峰 (To the Summit - Quest - World of Warcraft) : From - Jawn Highmesa (Jawn Highmesa - NPC - World of Warcraft) kalimdor
When you click the link to "Get the animus free here" and it takes you to the buddy store and has you log in, after you click it, it says that it will be installed automatically the next time you restart honorbuddy, but I'm unable to locate the file after restarting.
ಠ_ಠ Could you please remove the Chromie part of the Timeless Isle questline? It's unnecessary and some people may not want to spend 2500g just to pick up a quest in an obsolete area. Not sure why it was left in in the first place. EDIT: Never mind, doesn't even matter. It's been an hour and a half since I started it; it's only managed to find Old Piju & 1 chest and my armour is all red. I watched run through every damn mob it could find on its way from A to B. Chromie is the least of it's problems, it's #$%&ing suicidal.
Persistent suicide to what? Are you dying to Ordon's followers? Super elite turtles? Or falling damage? Also, have you turned on the spell avoidance in the plugin? Whats your gear ilvl? Details. Also, I need to research what quests are still available after eliminating the kicker (if it drops support for multiple quests as they won't open up to you)