Honorbuddy v2.5.11837.752

Hi, Tarathiel2, and many thanks for the log.

You are the only one that has reported this problem (so far). As such, we believe there may be something awry in your Honorbuddy installation, but the log does not support our suspicion.

As such, we've opened HB-1383 ("DungeonBuddy recognizing completed dungeons, but not leaving them") against this issue.

cheers,
chinajade


[size=-2]Ref: Tarathiel2's problem report w/log[/size]

 

Hi agan, Wullie,

We just believe the problem has been localized by inspecting the log. We have not investigated the cause of the issue yet. It could be a simple bug in InteractWith, it could be a nasty interaction cause by ProfessionBuddy, or a botch in HBcore's target filtering, or a whole host of other things.

Will just have to wait and see how the report is resolved. If there was a potential work-around, it would've been offered in the original reply.

cheers,
chinajade

 

Hi, Cevaps,

We still have a lengthy list of severe bugs to address before we will look at optimizations. I'll put a note to that effect in the second post.

cheers,
chinajade

 

Hi, Jazzman170, and thank you for the very nice write, video, and log!

We believe what your are observing is the new "item selling limit" imposed by the WoWclient. After selling 20 or so items to a vendor, the window must be closed and re-opened, and another round of selling occurs. We have no clue if this is a WoWclient bug, or a 'feature' to prevent a particular kind of exploit, or just a very ugly way to throttle WoWserver load.

Anyways, .750 and prior failed to sell correctly if more than 20 items were involved. What you are observing is the new algorithm to handle selling 20-items-at-a-time to make the WoWclient happy.

We've created HB-1389 ("ProfessionBuddy repeatedly opens and closes the Vendor frame") to confirm this. But, we expect it to be closed as "Not a Bug".

cheers,
chinajade


[size=-2]Ref: Jazzman170's original post w/log[/size]

 

Hi again Tarathiel2, and thanks for the follow up.

We've added your observations to HB-1383.

cheers,
chinajade

 

Hi, PiroxTester, and many thanks for the log.

We've opened HB-1399 ("ProfessionBuddy emit wrong messages due to handler detach failure") against this issue. There appear to be some quirky things in this profile you're running, could you attach or link us to the profile, so we can attach it to the problem report?

cheers,
chinajade


[size=-2]Ref: PiroxTester's problem report w/log[/size]

 

Hi, all.

Thanks for that log Medalofwhat! Also, thanks for that tip, LimboMessiah.

We've had great difficulty reproducing the problem since users that report this problem rarely attach logs. We'll hazard a guess that one of your plugins is causing this problem. Perhaps, MrItemRemover2. Try disabling MrItemRemover2 and see if the problem goes away. If it does, you'll have to seek help in the MrItemRemover2 thread.

For now, we are not going to consider this an Honorbuddy bug. We don't have sufficient logs to establish that pattern, and we're not going to waste the senior staff's time chasing a non-issue.

cheers,
chinajade


[size=-2]Ref: Medalofwhat's problem report w/log[/size]

 

Hi again, PiroxTester, and thank you for the follow-up.

We've attached your profile to HB-1399.

cheers,
chinajade


[size=-2]Ref: PiroxTester's follow-up w/profile[/size]

 

Hi, GK2014, and MANY thanks for these improvements.

We've opened HB-1404 ("Updated Protected Items.xml") to have the modifications folded in.

cheers,
chinajade


[size=-2]Ref: GK2014's recommended ProtectedItems changes[/size]

 

[size=+1]Thread closed / Honorbuddy Update Status (Build #19102)[/size]

We're waiting on an Honorbuddy release that will address WoWclient Build #19102.

If you don't know what's going on—its WoWclient "patch day". More info here:

BosslandGmbH:HelpDesk:Game client "Patch Recovery" blues​

Status here:

[Official] Honorbuddy Update Status - Patch 6.0.3 (Build #19102) ​

cheers,
chinajade