WowAce

When Rarity pops up the achievement-like panel like in the first image shown in the Images category, and I click it, the achievements panel opens with somewhat garbled content along with an error:

Message: ...ns\Blizzard_AchievementUI\Blizzard_AchievementUI.lua:2544: bad argument #1 to 'band' (number expected, got nil)
Time: 03/24/18 19:12:13
Count: 2
Stack: ...ns\Blizzard_AchievementUI\Blizzard_AchievementUI.lua:2544: bad argument #1 to 'band' (number expected, got nil)
[C]: ?
[C]: in function `band'
...ns\Blizzard_AchievementUI\Blizzard_AchievementUI.lua:2544: in function `AchievementFrame_SelectAchievement'
Interface\FrameXML\AlertFrameSystems.lua:421: in function <Interface\FrameXML\AlertFrameSystems.lua:401>

Locals:

Clicking on actual achievement pop-ups work without errors.

I THINK this started to happen when I installed Pawn, but I can't be sure. I have reported this to the author of Pawn, but as Pawn doesn't interact at all with the achievement window, it doesn't seem likely to be a fault in Pawn. But who am I to tell. :)

What should happen when you click on it?

I've never clicked it.

How would I know what should happen? I didn't write the addon. :-P If nothing should happen, then that mission was not accomplished. ;-)

I believe what Urtgard means is, what did you, as a user, expect when you clicked the faux achievement popup? That's a fairly standard question.

I'll see if I can reproduce the issue. This might just be an oversight, as Allara might not have intended for anyone to click on the non-functional achievement popup, or something has changed since/interferes with it in some way (needs further investigation).

I've looked into this, and it's simply a side effect of hijacking Blizzard's achievement alert system with items instead of achievement IDs.

Unfortunately, there is no good way (that I have found) to work around this without copying large chunks of their interface code. I'm open to ideas, but pending that I'll put this on the back burner. Pawn isn't to blame, though, as it appears the click would always have caused an error.

TL;DR: Don't click the popup. It's not supposed to work (I think) :P