HB Failure to correctly read FlyTo Location.

Every now and then (this has been happening for a while, and 3-4 of my friends have been experiencing the same issue) when HB is reading a line like this

HTML:

<CustomBehavior File="FlyTo" X="-1276.984" Y="4298.551" Z="77.25219" />

It just keep flying into the distance ending in me dying of fatigue, then getting stuck trying to walk back. It takes forever for the bot to get out of this fatigue zone.

Here is the part of the log where it happens. There is nothing to see there basically.
I have tried to change the coordinates SEVERAL times but the issue keeps occurring every now and then.

HTML:

[Profile Message]: Flying Back To Continue Route
[QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
Goal: Mounting for Flying travel
[CGSpellBook::CastSpell] Override ID: 32240, KnownIndex: -1
[QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
Goal: Flying to <-1123.26, 4230.834, 93.66737>
[FlyTo-v501(debug) @line 1189]: Flying to '<-1123.26, 4230.834, 93.66737>': <-1123.26, 4230.834, 93.66737>.
[Singular] attention: Pull Distance set to 1 yds by Questing, Plug-in, Profile, or User
[QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
Goal: Flying to <-1276.984, 4298.551, 77.25219>
[FlyTo-v501(debug) @line 1190]: Flying to '<-1276.984, 4298.551, 77.25219>': <-1276.984, 4298.551, 77.25219>.
We are stuck!!
[Stuck] Trying strafing right.
[Singular-DEBUG] YourCurrentTarget: changed to: (null)
Inserting Rik'kal the Dissector [Questgiver, SpellClick] into the database!
Stopping the bot!
Stop called!
Bot Stopped! Reason: User pressed the stop button

 

You should post full log if you actually want support, optionally link to profile (it seems like profile error, but log should tell it also).

 

Anything above wont matter. its_not_the profiles fault.

Ive been running the same profile for two months and this only happens like once a week or something. Like i said, I have also tried to change the coordinates. and the issue started after the 5.4 patch.

 

I see. If I were you, I would try to replace flightor with MyCTM ( use flightor to fly in the sky first, when you are safe in air switch to MyCTM, after when almost on spot use flightor again)

 

Thats exactly what ive done on another profile I have. yet the users of it has reported the same issue. I doesnt matter where the FlyTo coordinate is. if it fails, it fails.

 

Thats strange, only isues I had with flightor was mountains, and I was overcoming it with CTM. If its not related to that, I didnt encounter that bug then.

 

if you would, please post a full log as an attachment so we can see whats going on.
http://www.thebuddyforum.com/honorbuddy-forum/honorbuddy-guides/35945-guide-how-attach-your-log.html

 

The log seems to be gone. but TRUST me when I say there is nothing so see there. the important and only relevant part of this is already shown in post #1

 

ok it happened again on ANOTHER profile just now. and this time at was a TON of other players standing on the EXACT same location!

imgur: the simple image sharer

I'm telling you.. HB is seriously broken.

 

This has been happening to me ALOT as well, usually once i step away from the computer for any amount of time 2 minutes 20 minutes doesnt matter, the profile i use has no stuck points either but seems since the patch to be getting stuck places where the profile does NOT even point to!

 

So you're wasting your time removing my "bump" post instated of actually replying.. Well done! /clap

McDonald's has better customer support than you guys.

 

wow, thats a great way to get support. china is not obligated to reply to posts. this is the first time i saw this thread again since the first. so maybe instead of insulting the people trying to help, you can be patient.

 

Having to wait more then 2 weeks for a reply that doesn't even address the issue, is in fact commonly known as bad support. I stand by my previous statement.

 

great you can figure it out yourself then.

thread closed.