HB ARCHIVES: Honorbuddy Profile Pack--DO NOT DELETE!

This log shows that there's a lot of quests in your log - and that it was moving to do a quest before you stopped it.

 

Yes, but it will be a while before I do so as I'm still working on other things such as Singular and the Artifact profiles.

 

It does the Exodar scenario at the moment - that's it.
I've been busy working on Singular and the 36 artifact profiles.

 

The issue with the eggs is known, and it's being looked into.
For the navigation issues, those will most-likely need to be fixed internally for the bot's navigation system.

I've set the gun hotspot over to the one you posted.
This should make it use it instead.

I've added the blackspot - but I can't guarantee it will work as blackspots are being reworked at the moment.

 

If it says false, that means the quest hasn't been completed yet.
But for whatever reason the quest giver isn't offering it for you?

This sounds like it could be a Blizzard issue.

If you do /dump IsQuestFlaggedCompleted(33721) does it return "True" ?

 

I've added a code that should make it go out of flight form.

I believe flight form can loot objects without going out though?
Unless they changed that.

 

I'll add in attributes that may fix this, but I'll need a log to see why the InteractWith isn't interacting.
Right now I'm assuming its either a mixture of players being near your bot - or the interaction failing and the blacklists preventing them from running again.

Kill between hotspots is more of a user preference and isn't required to be on or off.
It just makes it so the bot will kill mobs that are outside of the hotspot areas.

 

There are no official profiles for the world quests yet.
I'm currently busy working on other things at the moment.

Thanks for the feedback!

 

What was the "Goal" of the bot during this?
or
What was making it want to go past that wall?

 

This is a combat routine issue, not a profile issue.

Please report combat routine issues to the developer of the combat routine you're using.

 

This profile is currently unsupported and still being tested/debugged.
Due to the ridiculous stealth mechanics for this, it may never be fully AFKable for the bot.

 

It looks like the quest behavior used for this quest is having a lot of error output for whatever reason.
This could be related to the errors that Lockwood has posted previously.

I can look into getting this quest behavior removed and replaced with some hard-coded logic instead that should be more reliable and future-proof.
Thanks for the log!

 

I don't believe there's a profile for that on this pack.
You'd have to look on the forums for one.

 

That error should be fine.
It's just saying the DoWhen codes are looping.

Is it affecting bot performance?