olixxl: You can always lower the ML threshold. You right click your portrait and set it to uncommon, if that's what you mean... Because Master doesn't initiate rolls unless you ask it to. On that note, you can also use the Priority Configuration menu under options to add someone to the priority list, which adds click-able rows for each priority looter just beneath the item, to make instance items easy to distribute.
Hope this isn't a stupid question? Anyway I have been asked by many Guild member how the actual random function within XlootMaster works. I assume people are either given a random number that they keep the whole raid or set alphabetically etc? We are using it for coins/bijou's/scarabs and greens and most people are happy with it. One person claims there is a pattern but if it is random I know that it is most unlikely but I am not a Statistician and they are lol. It does speed the run up and if anyone could answer this it would be greatly appreciated so I can let everyone in the Guild know.
XLoot is my favourite mod, thanks a lot for your efforts. With WoW 2.0 in mind, I tested XLoot build #18206 on the current PTR. After changing the .toc and setting forcecompat to on, looting seems to work OK. But upon looting the last item, I got the Blizzard frame: "XLoot has been blocked from an action only available to the Blizzard UI."
Extract from BugSack:
[2006/11/30 10:52:37-99-x1]: <event>ADDON_ACTION_BLOCKED:AddOn 'XLoot' tried to call the protected function 'CloseLoot()'.
XLoot\XLoot.lua:400: in function `AutoClose'
XLoot\XLoot.lua:331: in function `OnHide'
XLoot\XLoot.lua:729: in function <Interface\AddOns\XLoot\XLoot.lua:729>
<in C code>: in function `Hide'
XLoot\XLoot.lua:798: in function `Clear'
XLoot\XLoot.lua:398: in function `AutoClose'
XLoot\XLoot.lua:584: in function `Update'
XLoot\XLoot.lua:321: in function `obj_method'
AceEvent-2.0\AceEvent-2.0.lua:285: in function `TriggerEvent'
AceEvent-2.0\AceEvent-2.0.lua:846: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:839>
I'd appreciate if you checked this, it might happen that Blizzard changed some restrictions or it is just my failure.
Starlight: Gwah? Why is CloseLoot() a protected function now? argh... I'll look into it. Thanks for telling me.
Mindlessgalaxy: Here's the function. It gets the max people in the group, and grabs a random (math.random, built in function) number in the pool until it gets a valid (In range, online, existing) member. Random is, by flaw of design, somewhat patterned, but master has no intended pattern.
local max = GetNumRaidMembers() > 0 and 40 or 5
local name, id
while not name do
id = math.random(1, max)
name = GetMasterLootCandidate(id)
return name, id
Got the following error in TBC today. Was grouped with one player and a Green item dropped.
Unfortunately I was unable to roll :p
XLootGroup\XLootGroup.lua:128: attempt to call method 'AddRow' (a nil value)
XLootGroup\XLootGroup.lua:128: in function `obj_method'
AceEvent-2.0\AceEvent-2.0.lua:285: in function `TriggerEvent'
AceEvent-2.0\AceEvent-2.0.lua:846: in function <...ce\AddOns\XLootGroup\Libs\AceEvent-2.0\AceEvent-2.0.lua:839>
I just noticed a small bug using XLootGroup r 18179 (i think... ^^)
When you press need or greed for an BOP item and on the confirmation dialogue you select "cancel" then you only see the button you just clicked. So you have to wait until the time runs out or you choose the same option again.
Starlight: Alright, I removed the call to it (It was rather extraneous anyway...), let's hope it works.
I am afraid, this gets more complicated than expected :(
If there is nothing to loot in the corpse:
2006/12/01 09:25:39-156-x1]: <event>ADDON_ACTION_BLOCKED:AddOn 'XLootMaster' tried to call the protected function 'CloseLoot()'.
FrameXML\LootFrame.lua:18: in function `LootFrame_OnEvent'
XLoot\XLoot.lua:364: in function <Interface\AddOns\XLoot\XLoot.lua:362>
<string>:"LootFrame:OnEvent":2: in function <[string "LootFrame:OnEvent"]:1>
I was trying it solo, so master looting did not apply... Just wondering why XLootMaster is involved.
An other (rather small) issue is, that upon closing the loot window without looting the junk, the character stays kneeling until it moves.
Starlight: I don't know what to tell you. I haven't gotten any other reports of it not working. Tried removing AnchorsAway, XLoot, and all plugins, then re-downloading? The only thing I can think of is that somehow hiding the actual loot frame (To close loot since I can't do it directly) taints it... I'm not on tbc/ptr, so I can't test it myself, unfortunately.
I asked someone in #wowace to test it on the ptr, and apparently they have no problems. =\
Find 'closeloot' in 'X:\Games\World of Warcraft\Interface\AddOns\XLoot\XLoot.lua' :
X:\Games\World of Warcraft\Interface\AddOns\XLoot\XLoot.lua(400): --CloseLoot()
Found 'closeloot' 1 time(s).
tbc report as you wanted me to test it. when going solo i had no problems but when i entered an instance with a group stuff started to happen. bla bla only blizzard ui is allowed to do this thing bla bla was what i got. dunno if it was due to the group or amount of items in the loot though.
well, if noone else reported this problem, then it's definitely my fault somehow, I apologize.
What I did was downloading Ace2-r18401[TBC], AnchorsAway-r18177, Deformat-r18346 and DewDrop-r18347. Plus XLoot, XLootMaster and XLootMonitor, today's builds. Switched off everything else and got the error above.
Never mind, let's hope I made some stupid mistake, and I cross my fingers that XLoot will work with WoW 2.0.
Thanks for your efforts, I would badly miss your fantastic mod. :)
Alright. I'm going to ritually hunt down ways to do this without trying to call a closeloot even correctly call "HideUIPanel(LootFrame)", otherwise I'm raising voice at blizzard's forum. How the hell they think CloseLoot() is something that only blizzard addons need access to is beyond me.
Thanks for the reports, everyone.
If anyone has extracted their FrameXML for the very latest builds, I need a copy of LootFrame.lua/.xml at least, I'm working on outdated copies.
XLoot is on hiatus with respect to PTR/Beta until Slouken resolves the issue with CloseLoot clearing the target. This, hopefully, will be early next week.
there is also an error in live in respect to what I think is considered LootClose(), if you open a window of an item opened from inventory (a lockbox, clam, etc.) and close it, without looting the item, the item containing the stuff actually bugs out and prevents you from re-opening it, moving it, etc. until you reload UI.
This is in the current version (1.12) and is a new issue in the latest version of xloot alone. Although Xloot may not be working in TBC because Blizzard's ignorant, there is still something wrong with the way you currently have it implemented in live, specifically, in the most recent versions.