Could not navigate to current hotspot dequeuing it!

[Votoxa]

Hello, i am a level 26 mage, and always when i try to use instancebuddy or grindbot this error comes


Could not navigate to current hotspot dequeuing it!


Here the log!


Loading Honorbuddy 2.0.0.3449 settings.
Authenticating..
Gatherbuddy Sessions: 0/0
Honorbuddy Sessions: 1/2
Shared Sessions: 0/0
Attached to WoW with ID 4364
New bot added!: Combat/Heal Bot [1.0.0]
New bot added!: Instancebuddy
New bot added!: Grind bot
New bot added!: PvP
New bot added!: Mixed
New bot added!: RaF - Combat Assist
New bot added!: Questing - Beta
Honorbuddy 2.0.0.3449 started!
Character is a level 26 Mage
Current zone is: Tirisfal
Building spell book
Spell book built
Loading C:\Users\Heiko\Desktop\Honorbuddy\Default Profiles\1-60 Horde New World Kalimdor.xml.
Changing current profile to 26-32 Stonetalon Mountains
Chose Default Mage 1.0.1 as your combat class!
[Default Mage]: Creating 'Rest' behavior
[Default Mage]: Creating 'PreCombatBuff' behavior
[Default Mage]: Creating 'PullBuff' behavior
[Default Mage]: Creating 'Pull' behavior
[Default Mage]: Creating 'Heal' behavior
[Default Mage]: Creating 'CombatBuff' behavior
[Default Mage]: Creating 'Combat' behavior
[Instancebuddy v3.0.0.0]:Checking for script updates
[Instancebuddy v3.0.0.0]:All scripts are up-to-date
Could not navigate to current hotspot dequeuing it!

 

[bossland]

grab the new Test release

 

[Votoxa]

I already did

 

[Votoxa]

What tha fuck? is in the new version ? xxx 88 no instance buddy? why ?

 

[Balasagun]

first of all ur not using the last version,and then you are in trisfal glades that not in kalimdor but ur using a profil that grinds over kalimdor and as i know HB is not able to use zepplin or ships to sail between kalimdor and eastern kingdoms.so u need to move ur char to kalimdor i think

 

[eduardo]

I'm getting this error too with the new version. It worked earlier today, but I logged into WoW/HB tonight, and started getting this error on multiple characters trying multiple profiles. I deleted my mesh folder, reinstalled, and did everything else I could think of. Here my log:

View attachment 12-9-2010_11_47 PM Log.txt