problem with random enchanted Heroic Scenario item

[mmitch]

I use Power Auras to warn me when I'm in PvP using my PvE gear and vice versa. My PvE set contains these boots: http://de.wowhead.com/item=98193/jinyusehersandalen They are created randomy enchanted and with four different names - mine are the "Jinyusehersandalen des Lauffeuers". I can't get a "Named Items / If in Bag" aura to work with these boots, PowerAuras always tells me that the Item "Jinyusehersandalen" can't be found in my bags. I've tried the short Item Name "Jinyusehersandalen", I've tried the complete name "Jinyusehersandalen des Lauffeuers" and I've tried the item ID "[98193]" - nothing works. My other items work fine. Could this be a problem with the random enchant/random title of the item?

[Resike]

If you have it equipped and invert the aura like that:

http://i.imgur.com/1TEE7Dj.jpg

Then the addon can find it?

[mmitch]

When I do that, the PowerAura is alwas active - regardless of having the boots equipped or in my bags. Ctrl+Click gives me the expanation: "should be displayed, because item Jinyusehersandalen not carried (inverted)" (I have to translate the message, so perhaps this is not 100% accurate)

Basically this is the same as my original problem: The boots are not found and because the Aura is inverted, now it is always active instead of never.

Another small question: In your screenshot, you gave the item id as "91303", not "[91303]" - are the square brackets optional?

[Resike]

Have you tried to put it in one of your different bags, different slots?

Yea the brackets are optional, the addon can convert it to number either way.

[Resike]

Bump.

[mmitch]

Moving the boots around does not help - still stays the same.

PowerAuras seems to know about the boots (the displayed icon is correct) but can't find them. I've tried the same Aura with a fantasy item named "XYZXYZXYZ", these are the differences I observed:

• Icon: the boots show up with the correct icon, XYZXYZXYZ gives me the red question mark icon
• Messages: PowerAuras' diagnostic messages ("should be/is not displayed because ...") about my boots end on "not carried", while those about XYZXYZXYZ end on "not found".

Perhaps this helps to track the problem down.

[Resike]

Try to enable debugging, in the BizzMenu/Interface/Addons/Power Auras Classic and then trigger the aura, you should get more info then.

[mmitch]

I've activated debugging and added "only when mounted" to the aura so I can trigger it - but nothing happens. I don't see any debug messages in my chat lot, although the aura triggers (boot icon is displayed when I'm mounted).

[Resike]

Oh yeah, thats only for event debug, enable the aura debug then in the effect editor of the aura, in the bottom right corner.

[mmitch]

Ah, I see. That's a lot of output :-) I will try to empty my bags and backup and remove all my other auras, but this could propably take some time (going to bed now).

(And how do I copy text from the chat log?)

[Resike]

It will print out every item from your bags, so you can check that if the addon can find it or not. But we mostly need this line:

itemLink= [Tyrannical Gladiator's Warboots of Alacrity] itemName= Tyrannical Gladiator's Warboots of Alacrity itemId= 91303

To check that the itemName gets the right name and id from the itemLink or not.

[mmitch]

Ah, ok.

Letting the aura check for [98193] and having the boots in my bags, the debug log says:

itemName=Jinyusehersandalen
[… lots of other items …]
nil - nil : [Jinyusehersandalen des Lauffeuers] >> Jinyusehersandalen des Lauffeuers
[… lots of other items …]
isEquipped = false isBagged=false

Looks like the boots are not found, because [98193] translates to Jinyusehersandalen which does not match Jinyusehersandalen des Lauffeuers – so the random suffix of the item would indeed be the culprit. Hmm, I could check this with my other character, he too should have the guaranteed random 516 boots from his first Hero Scenario.

[Resike]

I see. But to be honest i have no clue how to fix this to work with all the client languages atm, but at least we know whats the problem now.