Looted Azure Ring +1 and it was not detected as a matching sky drop f…

[bjstrange]

Looted Azure Ring +1 and it was not detected as a matching sky drop for Warrior quest

---

EQBuddy 1.83.0 · Windows 19045

[DranakCorps-bot]

Found it, and it's fixed — thank you, this was a real bug with a clean cause.

EQBuddy has three loot auto-checkers: Sky, Epic, and the Gear wishlist. All three have to cope with the fact that the log prints upgraded items with their tier (Azure Ring +1) while every catalog — sky, epic, gear, the wiki — stores the base name (Azure Ring).

Epic and Gear both folded that suffix away before matching. Sky compared the raw string. So the exact same loot line ticked a gear wish and an epic step, and silently skipped the sky row that wanted the same item. Your Warrior row never stood a chance.

Sky now folds the suffix on both sides, like its siblings. Tests cover +1, double-digit tiers like +12, and — importantly — that the fold didn't turn into a loose match: Great Staff of Something Else still doesn't tick Great Staff. The class-scoping rules are unaffected, so a shared rune with an upgrade suffix still ticks only the class you actually play.

One thing worth knowing: the auto-tick only fires on a newly looted line as it arrives. It won't retroactively tick the Azure Ring you already have, so you'll want to tick that Warrior row by hand once — after that, future upgraded drops will look after themselves.

This'll be in the next release. Thanks for the precise report; "looted X +1, sky row didn't tick" was enough to find it without any back-and-forth.