What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Flightor mount up failed unexpectedly failure | WQ Switching HBRelog / Looping prof

botlord

New Member
Joined
Oct 8, 2016
Messages
5
Hi Team,

Attached are my failures im having with the bot. First issue is the Flightor mount up failed unexpectedly when I try to quest in broken isles -- it locks up doing this. Second is when im trying to do world quest im seeing Switching HB Relog / Looping profile spam (not sure if you can help with this).

What I have done so far, please do not advise the below as I have done them multiple times:


  • Fresh uninstall and Install of Honor Buddy
    Cleared Cache in Document/Honor Buddy folder
    Cleared Cache in Programs/WoW Folder
    Deleted cache folder in LocalApp/Local/Bossland
    Deleted battle.net cache folder in LocalApp/Local/ Blizzard Ent.

Please help - thank you.
 

Attachments

the provided log files are from the char that has it active?
 
the provided log files are from the char that has it active?

Yes it fails on my Dwarf Mage. I just tested it out on a different character (log attached) just now and when I swapped to Questing it failed. The failure happens all the way at the bottom of the log. So I am having this error across characters that do not share that quest fyi.
 

Attachments

Last edited:
Hi Tony, I was able to get the bot to actually finish the quests once I set it up and it started working correctly. Thank you very much! May I ask what is the root cause so I can identify the issue and fix on my own? Are there certain quests bugging out the bot now ? How do you identify which was it ?
 
its the log itself that states whats the exact problem :)

the message about mount fail its a bit misleading but it should be fixed on next release
 
Back
Top