HB ARCHIVES: Honorbuddy Profile Pack--DO NOT DELETE!

It seems that Kick has this quest setup so that if the player is within the bubble radius - it will loop a constant interaction with an NPC that's inside to 'get out of' it.
So somehow your character ended up within the detection radius.

An easy fix for this would be to turn down the detection radius - and have terminations if the player is outside of it.
I've got this one marked down and will tweak it a bit once one of my testers get to the spot.

 

While I have my doubts, this one could be a Mesh issue.
From the looks of your log, the bot ended up in the tower - and got stuck because it couldn't get down.

The log has an endless loop of:

Code:

[03:45:39.280 D] Changed POI to: Type: Kill, Name: Bladespire Raider, NavType: Run
[03:45:39.346 D] Clearing POI - Reason Pull target is blacklisted
[03:45:39.498 D] Changed POI to: Type: Kill, Name: Bladespire Raider, NavType: Run
[03:45:39.508 D] Clearing POI - Reason Pull target is blacklisted
[03:45:39.588 D] Changed POI to: Type: Kill, Name: Bladespire Raider, NavType: Run
[03:45:39.653 D] Clearing POI - Reason Pull target is blacklisted

Which is why I'd assume it's the navigation, because it can't get to the NPC.
However, this could also be a Combat Routine issue.

 

Treasures were added to the questing pack at the request of Kick because treasures give the experience equivalent of a single quest.

Also, this treasure was removed from the questing profiles a few weeks ago when it was noted as broken given the recent patch.
You're most-likely using an outdated copy of the profiles.

 

It looks like the bot fell to that location.
Issues like this aren't typically profile-related issues, and are caused by low FPS, NPCs with knockback abilities, or spells that causes the player to "jump" or "go" in a direction. (eg: Monk's roll or Warlock's demon jump.)

From the looks of your log, the bot had just completed a quest and started moving to the next location.
During this, it got stuck on an object which caused the anti-stuck handler to jump, which is when it fell down there.

Code:

[COLOR="#00FF00"][14:24:07.523 D] Goal: Moving to <1906.354, 3225.242, 133.759> [Ref: "MoveTo" @line 1281][/COLOR]
[14:24:31.046 V] We are stuck! (TPS: 14.65546, FPS: 29, Latency: 37, Map: Draenor, loc: <1593.608, 3288.043, 133.6591>)!
[14:24:31.048 D] Nearest game object, distance 15.44 yards
<!--Bench in Talador zone and on Draenor continent-->
<GameObject model="World\Expansion05\Doodads\Draenei\6dr_Draenei_pewlong.m2">
  <Matrix M11="-0.07845926" M12="-0.9969173" M13="0" M14="0" M21="0.9969173" M22="-0.07845926" M23="0" M24="0" M31="0" M32="0" M33="1" M34="0" M41="1597.52258" M42="3302.97925" M43="133.665314" M44="1" />
</GameObject>

[14:24:31.048 V] Trying dismount
[14:24:31.048 D] Stop and dismount... Reason: Stuck Handler
[14:24:32.255 V] We are stuck! (TPS: 12.841, FPS: 22, Latency: 37, Map: Draenor, loc: <1593.612, 3288.042, 133.6591>)!
[14:24:32.256 D] Nearest game object, distance 15.44 yards
<!--Bench in Talador zone and on Draenor continent-->
<GameObject model="World\Expansion05\Doodads\Draenei\6dr_Draenei_pewlong.m2">
  <Matrix M11="-0.07845926" M12="-0.9969173" M13="0" M14="0" M21="0.9969173" M22="-0.07845926" M23="0" M24="0" M31="0" M32="0" M33="1" M34="0" M41="1597.52258" M42="3302.97925" M43="133.665314" M44="1" />
</GameObject>

[COLOR="#FF0000"][14:24:32.256 V] Trying jump
[14:24:32.848 N] [Singular] *Slow Fall on Me @ 100.0%
[14:24:35.827 D] Generating new path because we are not on the old path anymore![/COLOR] [B] --- Bot fell here as a result of getting stuck on the objects listed above.[/B]
[14:25:07.965 D] Garbage collected 1 nav tiles

In that area, does it look like the bot can get away from it without jumping or falling? (a direct path)

This error may need to be reported to the navigation thread - as a patch to the mesh to blackspot the initial object the bot got stuck on would fix this.

 

This bug along with another similar bug has been noted already and is in the process of being fixed.
Thanks for the report!

 

The profiles that are shipped with the bot aren't updated as frequently as the store copy.

The store copy is updated twice a day at 11AM and PM UTC.
The profiles that are shipped with the bot are only updated when the actual bot is updated.

 

Huh, this one's a bit interesting.
Not a profile issue - but an issue in the "MountHook" logic.

The mount hook is used for lower level profiles to detect when you're high enough level to buy a mount.
Once you are high enough level, it hijacks the profile code and moves to buy a mount for you (if you don't have one already.)

Somehow.. the MountHook logic remained hooked into your bot once you loaded the initial profile which chain-loaded every profile up until the Gorgrond profile.

With your issue, the MountHook activated - causing the bot to 'attempt' to go to Orgrimmar to buy a mount.
I'll push this to the other devs, and see what they can figure up.

 

I need a log to see what's going on.
None of my testers have had issue with this quest - so something has happened on your end to cause the error you're having.

 

How are you obtaining the profiles?
This issue was addressed two weeks ago and a fix should've been made.

 

I've honestly not tested it out that much.

But at the same time, you have to count the fact that the higher level you are - the faster the lower level quests will be completed.
So even though the experience yield is a little bit lower, you're still completing them at a higher rate than you would quests that are your level.

Perhaps someone else here has experimented with it a bit.
If not, then your best bet would be to try it out.

If you're leveling a lot of characters - check their /played.
Have one group do things differently than another group and see how the /played matches up.