| |
I noticed some odd behavior with GetMasterLootCandidate tonight. It appears that while you are in a raid, GetMasterLootCandidate only checks raid members for loot candidacy-- That is it will not include people who should be a loot candidate that aren't in your raid, but while in a party or solo, it returns the correct values even if the loot candidates are not in your party. Here is an easy-ish way to reproduce this odd behavior:
1) Create a raid of 3 people, and set yourself as the master looter with the threshold at "uncommon"
2) Get the entire raid to travel to the deadmines and kill stuff until a green item drops.
3) Create a macro that looks something like this:
/dump (function() local t = {} for i=1,40 do t[i] = GetMasterLootCandidate(i) end return t end)()4) Mouse Over the item and run the macro. You will see the 3 members of your raid show up as candidates for the loot.
5) Boot a member of the raid
6) Run your macro again. You will only see the remaining 2 players in your raid. The player you just booted is no longer reported as a loot candidate
7) Boot the remaining players in your raid
8) Run the macro again. You will now see the complete list again.
9) Begin reinviting people back to the raid (do it quickly before they get a free hearth!)
10) As long as you remain a party, GetMasterLootCandidate will give you a full list.
11) Convert to raid before all your members are back in the party, and run the macro again. You will only get a list of the loot candidates in your raid.
Is this how GetMasterLootCandidate is supposed to work?
[Note: The /dump slash command is provided by Iriel's DevTools. It's crazy useful and you can find it here: http://www.vigilance-committee.org/wow/downloads/ ][ post edited by Tem ]
What more work?
I don't wanna do that.
Yes m'Lord.
|
