The limitations of FlyTo...
Hi,
Bogdan23lolx, and thanks for the log.
Basically, the problem occurs when both of these conditions are met:
- There is no ground path to the destination.
This happens when the destination is 'in the air' (like a few of the dungeons), or on a ledge (like found in Deepholm). Also, recall that Honorbuddy cannot calculate a ground path if a 'zone boundary' transition is required. Examples include inter-continental travel, or entering/leaving instances.
- FlyTo is called while the toon is standing in a non-flyable area.
'Non-flyable' areas include deeply 'indoors', or other flight-restricted locations. FlyTo will make an effort to locate a nearby flyable area, move to it, and try again, before emitting the message.
FlyTo emits the message and stops, because it has no way to distinguish between a 'temporary' non-flyable situation (e.g., the toon is indoors), versus a 'permanent' non-flyable situation (e.g., the toon does not have flight capabilities for the continent, flying is disallowed on the expansion at the moment, the whole zone is deemed 'non-flyable' such as Ghostlands/Bloodmyst Isle, etc). Since there is no ground path to the destination,
FlyTo cannot fall back to surface-based navigation.
It is the profile's responsibility to make certain the toon is standing in a flyable area before any attempts are made to call
FlyTo. Profile defects should be reported to the author.
HOWEVER, if you manually moved your toon into a non-flyable area, then the defect was caused by you, and not the profile.
As a work-around, just move your toon into a flyable area on the correct continent before starting Honorbuddy.
cheers,
chinajade
