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

Thanks for the log!
I'll check it out and get a fix live as soon as possible.

 

Is Bladespire citadel actually discovered?
If so (or if not), can you run this in-game and tell me what it says?

Code:

/run local a1=(select(3,GetAchievementCriteriaInfo(8937,0))); local a2=(select(3,GetAchievementCriteriaInfo(8937,1))); print(a1, a2);

 

I've sent a blind edit that 'should' fix the issue.
I don't have any testers near this quest, so if you could verify, that'd be helpful.

 

It looks like there may be minor complications between the profile and navigator.
From the looks of it, Kick had originally hard-coded the profile to use the rope to get down, however a jump-link was added to the Mesh that tells the bot to use the rope when navigating in that area.

So the profile is conflicting with the bot's navigation, which is probably why it's going up and down endlessly.
The profile is telling the bot to use the rope, so while the bot navigates to the rope - the navigator uses the rope instead, meanwhile the profile still wants to use the rope, so it continues to go to the rope... and yea. Heh.
Endless loop since the navigator is endlessly hijacking the rope usage over the profile.

I've sent an SVN update that comments out all the hard-coded 'rope usage' from the profile so hopefully that should fix it.
The bot's navigator will handle all the rope usage on its own, and the profile with just quest as normally without worrying about it.

 

Hmm, so it's returning true on both. Yet if you were to start the profile (right now) it'll go to discover the Bladespire Citadel?

Very strange.
"true, true" means you've discovered it.
So the bot should also see that you've discovered it, yet it's not.

Could you try one more thing and run this profile for me?
It will pop information up on your Honorbuddy, just copy+paste the whole chunk that pops up, even if it has repeating lines.

View attachment Bladespire Test.xml ​

 

Thanks for the log and report!
I'll check it out and get a fix made asap if I can find anything.

I may need to send testers out to replicate the issue or to test changes, so I may not be able to update you on the status.
However, it will be documented here.

 

The profile seemed to be operating as it should - seeking and gathering roots to complete Kindling the Fire
When you came back to your character, could you see the mob that the bot was trying to engage? If so was that mob in a location where you couldn't navigate to?

Acording to the log the trinket usage bugged out twice. The first time you died while it was trying to spam usage of it.
After the bot revivied, the bot got back on track - then the same occured again, which is when the inactivity timer tripped.

If anything, this looks more like a Singular issue.
Singular trying to use the trinket, but usage of it isn't succeeding so it endlessly spams it.

You could turn off trinket usage in the "Class Config"
See here:

​

[HR][/HR]


Sure, I'll take any log you got.
Although navigational stuck issues are only (typically) helpful if the bot is actually stuck on an actual object which we can blacklist.
Like a fence, seasonal object, mailbox, etc.

Often the bot will fall into a location where there's no way to "walk" out of it - so the bot will bug out.
Stucks like this are typically unavoidable since the bot falling in the first place wasn't intended. There's not really much we can do about those.

I don't typically list every bug on the 'bug sheet' - just some of the more major ones. :3

 

There's no as far as I'm aware. And I'm not sure of the necklace issue, you'd need to add in a feature request to Bobby, the Singular routine developer.
You may also want to provide him with this log. The usage of the necklace isn't forced in the profile at all, so that's all Singular's doings.

Hehe xD

 

Your log is showing a massive amount of errors.
Like litterately over 7,448 lines of errors.

I'm not sure what happened to your installation - but you'll definitely need to do a fresh installation to fix that.

 

Remember to save your key somewhere. As doing a fresh install will delete your settings files.

Make a folder and name it anything you want - this is where your Honorbuddy installation will go.
Click this link: http://updates.buddyauth.com/GetNewest?filter=Honorbuddy
That will download the latest Honorbuddy as a .zip file.

After the download is complete, open the .zip and extract the contents into the folder you made earlier.
That's pretty much it. Start up Honorbuddy, enter you key, then try the questing profiles again.

You can delete your old Honorbuddy folder and the downloaded .zip file.