Originally Posted by Meorawr
UnitAura seems to have changed but I couldn't find this mentioned anywhere. More importantly it's behaving in a really horrible way.
On live there's 13 return values (name through to isBossDebuff) plus an additional 3 return values for tooltip information.
In the latest build there's a minimum of 14 return values, the last one being a boolean. You'd expect the 3 tooltip values to then be values 15-17, however here's how it works for the following two buffs:
Legacy of the White Tiger:
14 return values, last one is a boolean. Values 15-17 aren't returned (so they're nil, effectively).
Life Cocoon:
17 return values, however 14-16 are the tooltip values, whereas this mystery boolean is #17.
Basically it's a major pain now because whereas we could (hopefully) have assumed #14-16 to be nil/number values, we now have to check if #17 is not nil in order to determine whether or not tooltip values exist.
Of course I could be completely missing something here so do correct me if I'm wrong 
/dump's of the returns:
<snip>
In short the stack needs 0's or nil's at 14-16 for the first case |
I just noticed this too while updating TellMeWhen. I wrote a quick script to pull buff and debuff information from anyone I targeted, went to the training dummies in Org, and went crazy targeting everyone I could find.
Here is a CSV of the results:
http://pastebin.com/pBczmavs (Save it with a .csv extension and open it with Excel/OO Calc/etc.)
The point was basically to see if there was any pattern to what that last boolean is, but I couldn't figure it out. Perhaps with a bigger sample set we could notice something.