Xuerian has actually posted a "cease development" notice on Wowinterface,
which was sad news for me as this is one of the first addons going into Interface folder :)
Hopefully it will hold for a while without breaking as long as Blizzard doesn't do significant API changes.
Xuerian has actually posted a "cease development" notice on Wowinterface,
which was sad news for me as this is one of the first addons going into Interface folder :)
Hopefully it will hold for a while without breaking as long as Blizzard doesn't do significant API changes.
Yeah... I see he posted
"I'm no longer developing XLoot.
Check out addons like Butsu"
But I liked the extra features that XLoot had over minimalistic addons like Butsu. Like being able to link the items in chat. Plus, does that mean that the other XLoot plugins will not be developed anymore either? I use all 4 and prefer them over other things that I have seen... Hopefully they will stay working for a long time. :)
Yeah... I see he posted
"I'm no longer developing XLoot.
Check out addons like Butsu"
But I liked the extra features that XLoot had over minimalistic addons like Butsu. Like being able to link the items in chat. Plus, does that mean that the other XLoot plugins will not be developed anymore either? I use all 4 and prefer them over other things that I have seen... Hopefully they will stay working for a long time. :)
My favorite thigs about Xloot is the monitor, history and the link to chat...
But being abandonesd perhapps someone with a bit of knowhow could have a quick look at it for the few errors that are and make some fan update...
ElfReloaded is very nice.. it's what I was using before I switched to XLoot + family.
I might go back to it, I had no complaints... just XLoot has more candy.
For now I'll stay with XLoot and maybe tweak it a bit for minor bugs until something breaks it in a bad way.
I would be forever grateful if someone withs oem knowhow could look at the autopass error and perhaps help me out with what i need to do to get rid of it, pops a lot in MgT cos of the satchels being uniqe.
[2008/04/01 13:56:37-1499-x1]: XLootMonitor-0.7.54067\XLootMonitor.lua:512: attempt to index local 'c' (a nil value)
(tail call): ?:
<in C code>: ?
AceEvent-2.0-66043 (Ace2):302: in function `TriggerEvent'
AceEvent-2.0-66043 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>
---
From looking at the code, c is turning up nil for some reason, the line before it sets it to RAID_CLASS_COLORS[class]
Guessing when it autopasses it doesn't pass the 'who' to the function, anyways, you could try, replacing this Line 510ish:
row.fsplayer:SetText(who)
local c = RAID_CLASS_COLORS[class]
row.fsplayer:SetVertexColor(c.r, c.g, c.b)
with this:
row.fsplayer:SetText(who)
local c = RAID_CLASS_COLORS[class]
if c then
row.fsplayer:SetVertexColor(c.r, c.g, c.b)
end
That 'should' at least not error, but I don't use it and it's entire drycode so uh, use it at your own risk, heh.
I was curious if there is anyway to stop announcing to the raid when Epic gems get looted to someone. I want to still send the message for other items, but just not gems like Crimson Spinel, Empyrean Sapphire, Lionseye, Pyrestone, Seaspray Emerald, Shadowsong Amethyst.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
ID: 18
Error occured in: Global
Count: 2
Message: ..\AddOns\XLoot\XLoot.lua line 550:
Usage: GetItemInfo(itemID|"name"|"itemlink")
Debug:
...AltClickToAddItem\libs\AceEvent-2.0\AceEvent-2.0.lua:299: TriggerEvent()
...AltClickToAddItem\libs\AceEvent-2.0\AceEvent-2.0.lua:910:
...AltClickToAddItem\libs\AceEvent-2.0\AceEvent-2.0.lua:903
AddOns:
XLootGroup, v0.5
XLootMaster, v0.6
XLootMonitor, v0.7
XLoot, v0.9
Date: 2008-03-27 22:37:52
ID: 28
Error occured in: Global
Count: 1
Message: ..\AddOns\XLootMaster\XLootMaster.lua line 605:
Couldn't GetMasterLootCandidate(7) - chosen from between 1 and 15
Debug:
[C]: ?
[C]: assert()
XLootMaster\XLootMaster.lua:605: GetRandomMLID()
XLootMaster\XLootMaster.lua:632: GiveRandomLoot()
XLootMaster\XLootMaster.lua:355: func()
...ce\AddOns\AtlasLoot\Libs\Dewdrop-2.0\Dewdrop-2.0.lua:721:
...ce\AddOns\AtlasLoot\Libs\Dewdrop-2.0\Dewdrop-2.0.lua:660
AddOns:
XLootGroup, v0.5
XLootMaster, v0.6
XLootMonitor, v0.7
XLoot, v0.9
Last update was a good while ago, but its working so its no panic (only ever popps error when u get autopass for some reason)
which was sad news for me as this is one of the first addons going into Interface folder :)
Hopefully it will hold for a while without breaking as long as Blizzard doesn't do significant API changes.
Yeah so far the only problem I've seen is (as you said) when the game automatically passes on BoP loot that you can't use.
I really hope it stays maintained unless someone knows of a good replacement.
Yeah... I see he posted
"I'm no longer developing XLoot.
Check out addons like Butsu"
But I liked the extra features that XLoot had over minimalistic addons like Butsu. Like being able to link the items in chat. Plus, does that mean that the other XLoot plugins will not be developed anymore either? I use all 4 and prefer them over other things that I have seen... Hopefully they will stay working for a long time. :)
My favorite thigs about Xloot is the monitor, history and the link to chat...
But being abandonesd perhapps someone with a bit of knowhow could have a quick look at it for the few errors that are and make some fan update...
I also love the monitor and history features, even though they are a bit quirky.
Not to mention the rollframes! forgot to mention those.
So much better then blizz oversized chunks of screencoverage...
hehe
got any info on it? there's no wiki page.
I might go back to it, I had no complaints... just XLoot has more candy.
For now I'll stay with XLoot and maybe tweak it a bit for minor bugs until something breaks it in a bad way.
But ElfReloaded is definitely an option.
I would say Minimalist addon
I attach the file here if you want to try it out.
It has a message loot output to tell what you looted.
But being a total nooblet on Lua all i can do is hope for fan updates or simmilar.
Guessing when it autopasses it doesn't pass the 'who' to the function, anyways, you could try, replacing this Line 510ish:
with this:
That 'should' at least not error, but I don't use it and it's entire drycode so uh, use it at your own risk, heh.