?ndere aktuelles Profil zu [N - Quest] 87-88 Kun-Lai Summit [Kick]
Bot wird gestartet!
?ndere aktuelles Profil zu [N - Quest] 87-88 Kun-Lai Summit [Kick]
[Sharp Exit] Sharp Exit is disabled. Skipping initialization.
[Singular] Your Level 88 Goblin Frost DeathKnight Build is
[Singular] ... running the Questing bot Solo in Kun-Lai-Gipfel
[Singular] Context changed, re-creating behaviors
[Profile Message]: Compiling Kun-Lai Summit Quests
[Profile Message]: Compiling Binan Village Quests
Could not find quest giver NPC with ID 61065 in database.
Bot Stopped! Reason: Could not create current in quest bot!
?ndere aktuelles Profil zu [N - Quest] 87-88 Kun-Lai Summit [Kick]
Bot wird gestartet!
?ndere aktuelles Profil zu [N - Quest] 87-88 Kun-Lai Summit [Kick]
[Sharp Exit] Sharp Exit is disabled. Skipping initialization.
[Profile Message]: Compiling Kun-Lai Summit Quests
[Profile Message]: Compiling Binan Village Quests
Could not find quest giver NPC with ID 61065 in database.
Bot Stopped! Reason: Could not create current in quest bot!
View attachment 72410
Code:?ndere aktuelles Profil zu [N - Quest] 87-88 Kun-Lai Summit [Kick] Bot wird gestartet! ?ndere aktuelles Profil zu [N - Quest] 87-88 Kun-Lai Summit [Kick] [Sharp Exit] Sharp Exit is disabled. Skipping initialization. [Singular] Your Level 88 Goblin Frost DeathKnight Build is [Singular] ... running the Questing bot Solo in Kun-Lai-Gipfel [Singular] Context changed, re-creating behaviors [Profile Message]: Compiling Kun-Lai Summit Quests [Profile Message]: Compiling Binan Village Quests Could not find quest giver NPC with ID 61065 in database. Bot Stopped! Reason: Could not create current in quest bot! ?ndere aktuelles Profil zu [N - Quest] 87-88 Kun-Lai Summit [Kick] Bot wird gestartet! ?ndere aktuelles Profil zu [N - Quest] 87-88 Kun-Lai Summit [Kick] [Sharp Exit] Sharp Exit is disabled. Skipping initialization. [Profile Message]: Compiling Kun-Lai Summit Quests [Profile Message]: Compiling Binan Village Quests Could not find quest giver NPC with ID 61065 in database. Bot Stopped! Reason: Could not create current in quest bot!
Profile does not work
Activity: Moving towards - <775.8038, -1785.62, 56.52417>
[STUCK] Got stuck at <794.7736, -1897.96, 65.33358> on map 870
[STUCK][HITTEST] LD/LU: False
[STUCK][HITTEST] Left: True
[STUCK][HITTEST] RD/RU: False
[STUCK][HITTEST] Right: True
[STUCK][HITTEST] Behind: True
[STUCK][HITTEST] Behind Left: False
[STUCK][HITTEST] Behind Right: False
[LogMeOut!]: Stuck detected (X="794,7748" Y="-1897,962" Z="61,27098"). Number of consecutive stuck : 3/8
[STUCK] Couldn't get unstuck.. Adding blackspot.
[STUCK] Moving backwards for 3 seconds.
[STUCK] Clearing current path to regenerate it around our stuck location.
Flushing timed movement. Direction: AllAllowed
Could not generate path from {791.1956, -1910.904, 60.05686} to {775.8038, -1785.62, 56.52417} (time used: 0 milliseconds) @ FindStartPoly
Updating repair cost for current equipped items. New value: [10g58s33c]
Could not generate path from {791.1956, -1910.904, 60.05686} to {775.8038, -1785.62, 56.52417} (time used: 0 milliseconds) @ FindStartPoly
Enabling Check at 22:24:27
Checktimer has Finished its Total wait of 5 Minutes, Enabling Item Check for next Opportunity
Will Run Next Check At 22:29:27
EnableCheck was Passed!
Turning off Check Since Done!
Unloading tiles!
Activity: Loading Tile/s
Loading HawaiiMainLand_35_30
Could not generate path from {791.1956, -1910.904, 60.05686} to {775.8038, -1785.62, 56.52417} (time used: 0 milliseconds) @ FindStartPoly
Activity: Moving towards - <775.8038, -1785.62, 56.52417>
Could not generate path from {791.1956, -1910.904, 60.05686} to {775.8038, -1785.62, 56.52417} (time used: 0 milliseconds) @ FindStartPoly
You really shouldn't have to do it now. The problem is with the cache folder (and fyi its an HB problem, not a profile writer's issue). In my opinion, a complete reinstall is typically overkill and should only be used as a last resort when nothing else is working. I only direct my users to delete the cache folder and it works just fine.
If you want to use the Grinding profiles - do so at your own risk! Blizzard keeps track of grinders.
<If Condition="(HasQuest(29922)) && Me.X < 200" >
<If Condition="(HasQuest(29922))" >
Druids can fly at level 58. It would be nice to see the outlands profile using it if it's available.