FYI this happens to my toons when they level also (all of them I think 20+ characters). Seems to be a pathing issue - characters try to jump over a hill nearby when they are stuck, they are not near the vines. I have to manually run them around then up mountain to the correct spot. They get stuck here trying to jump over a small hill: Need to be here where the vines are:
Hmm interesting. Thanks for the screenshots and the log! I've got this marked down. Will have a tester out there to figure up a blackspot of this vine (or a blackspot for the buggy path to it). Hopefully I'll have this fixed today or tomorrow.
Having trouble with the [QO] Netherwing Rep A [Kick].xml profile, particularly when it comes to the portion of the profile where it picks up the quests from the Mistress of the Mines and asks to enable two defunct plugins. I've already in a previous post attached a log for the egg collector profile but this is for the actual questing profile [A]. When the bot attempts to load the plugin NetherwingCollector1.9.cs, the plugin found with the profiles this error is printed: Code: [21:55:20.566 N] Compiler Error: C:\Users\unfre_000\Desktop\HonorBuddy\Plugins\NetherwingCollector\NetherwingCollector1.9.cs(84,28) : error CS7036: There is no argument given that corresponds to the required formal parameter 'reason' of 'Mount.Dismount(string)' When the script is loaded, these errors are printed: Code: 21:56:01.284 N] Changing current profile to [QO] Netherwing Rep A [Kick] ($Rev: 3547 $) [21:56:01.284 D] BlackspotManager forcing unload of meshes - New profile loaded [21:56:01.395 N] [FlyTo-v1987(warning) @line 735]: Found attribute via its alias name 'Name'. Please update the profile to use its primary name 'DestName', instead. [21:56:01.399 N] [FlyTo-v1987(warning) @line 758]: Found attribute via its alias name 'Name'. Please update the profile to use its primary name 'DestName', instead. [21:56:01.406 N] [ForceSetVendor-v1738(warning)] The VendorType attribute has been deprecated. Please replace it with DoMail/DoRepair/DoSell/DoTrain='true' [21:56:01.408 N] [FlyTo-v1987(warning) @line 885]: Found attribute via its alias name 'Name'. Please update the profile to use its primary name 'DestName', instead. [21:56:01.409 N] [ForceSetVendor-v1738(warning)] The VendorType attribute has been deprecated. Please replace it with DoMail/DoRepair/DoSell/DoTrain='true' [21:56:01.409 N] [FlyTo-v1987(warning) @line 914]: Found attribute via its alias name 'Name'. Please update the profile to use its primary name 'DestName', instead. [21:56:01.409 N] [FlyTo-v1987(error)] Neither the X/Y/Z attributes nor the <DestinationChoices> sub-element has been specified. [21:56:01.410 N] [ForceSetVendor-v1738(warning)] The VendorType attribute has been deprecated. Please replace it with DoMail/DoRepair/DoSell/DoTrain='true' My plugins folder, if it makes any difference: And I've attached the full log as well. You can disregard the HBRelog plugin errors, those are printed when HonorBuddy is started without HBRelog. View attachment 5452 2016-02-21 16.55.txt
Thanks for the further details! Yea, I've had this marked on my 'to do' list - it's just that the non 1-100 related bugs are a little bit lower priority. Sometime tonight or tomorrow(ish) I'll be doing a bug-fix wave and will definitely look into this one. Like I said before, I think the usage of the plugins can be completely removed. Do you have a Skype? I could probably use someone willing to test the changes as I fix it.
how to avoid questing in low level areas? my lowbie in full heirloom is questing in zone for 18~24 lvl
The Questbot is designed to use the checkpoint system, which checkpoints make the bot skip quests that are too low level. Unfortunately, checkpoints are only considered when the bot is first started or when the bot reaches a 'Checkpoint' line in the profile. There's a feature request to have it check every time your player is leveled up, but it's being worked on. At the moment I have no ETA when this feature will be available. However, as an alternative - you can write in a DoWhen code that will restart the profile every time your character levels. Here's an example of the code: HTML: <CustomBehavior File="RunCode" Type="Definition" Code="int startLevel = StyxWoW.Me.Level;" /> <!-- Store your starting level as a int Variable --> <CustomBehavior File="WaitTimer" WaitTime="500" /> <CustomBehavior File="Hooks\DoWhen" ActivityName="LoadAutoLoader_OnLevelUp" AllowUseWhileMounted="true" UseWhen="startLevel != StyxWoW.Me.Level" > <CustomBehavior File="RunCode" Code="Logging.Write(System.Windows.Media.Colors.Yellow, "[Profile Notification]: We leveled! Loading Auto-Loader.");" /> <CustomBehavior File="RunCode" Code="ProfileManager.LoadNew(Utilities.AssemblyDirectory + "\\Default Profiles\\Questing Profile Pack\\Auto Loader - v2.xml");" /> </CustomBehavior> To utilize this code, you must place it under every <QuestOrder> in each profile you're wanting to use. This DoWhen will load Auto Loader v2 which comes with your Honorbuddy installation. You can change the load directory, but right now it's going to the pre-packaged profiles located here: \Honorbuddy Folder\Default Profiles\Questing Profile Pack\ Be sure that you edit the correct profiles when adding this code if you don't want to change the load directory You're most-likely not using the profiles that are shipped with the bot.
Good evening, I have a problem playing my priest level 99. I'm in Nagrand and the bot goes "waypoints" but never touches the ground and therefore never dismount ... I'm in Horde
So my warlock has been killing mobs in N strangletorn for awhile ( lvl 26 warlock). Ive tried auto loader v2, regular autoload and simply trying to put him 12-58Ally profile, still goes back to NS to kill mobs, whats the deal? This seems highly inefficient
As carz pointed out. It's grinding to level 27. There are some questing locations that lack proper quest density - so when Kick was writing out the profiles, he wrote them so they just resort to grinding mobs. While it is a bit inefficient, there shouldn't be much it has to grind before it levels. So it shouldn't do this for long.
The bot never use the flying point, is the log it said that apparently "something is wrong with flight paths". Anyway thanks for your work ! I'm level 31. I attach the log.
Thanks for the log! Could you try with the latest update of the bot? If that doesn't work, try with a fresh install of the bot. There may be an error in your character settings.
Seems working now, already done a fresh install in the evening. New problem, toon stuck while trying to kill mobs that repop infinitly, maybe cause of the path, die after that and no click on ressurect. Attach below.
There seems to be a bug with the level 72 quest Planning for the Future. The bot kills the Snowfall Glade Pups rather than collecting them as they are level 1 attackable NPCs. The profile is [Fly][A - Quest] LK 68-80 [Kick].xml and I'm using TuanHA DK routine. I've attached a log here: View attachment 2744 2016-02-25 18.09.txt
This issue is most-likely caused by the external additions you're running such as your combat routine and this "Alisha Engine" and the "Botter Helper" plugin. Combat routines or plugins that aren't shipped with the bot typically cause issues as they aren't entirely designed for questing. Make sure when you're running the questing profiles that you're only using Singular and no extra plugins. It will run much better this way.
As mentioned in my post above. Third-party combat routines will typically cause errors while questing as they aren't entirely designed around questing. Combat routine such as TuanHA's have been reported to cause several issues such as the bot attacking neutral quest givers, or messing with quest behaviors. It's only recommended that you run Singular while using these questing profiles.