I would hazard a guess that another addon has started the taint
and what you're seeing there is poor reporting on behalf of the taint logging mechanism.
An easy way to verify this:
1. backup your WTF folder so all your settings are preserved before you start the game.
2. disable every other addon except XLoot*
3. pull 2-3 trash mobs, kill one and loot it in combat.
4. check your taintlog for errors.
My guess is you won't have any.
5. exit and overwrite WTF with your backup to get all your addon selections and settings back like you had them.
pre 3.1 when i was master looter it showed the raid broken down by (colour coded) class, now post 3.1 its only showing by raid group - i havent changed anything and i cant seem to find an option to swap the display around. what have i missed?
I don't know what happened the other day. I updated XLoot and XLoot Master through Curse Gaming Client because it said there was an update available. As soon as I did so, and I raided the same night (and I was loot master), I couldn't get a single loot window to popup with any XLoot addon enabled. I disabled XLoot and I could loot. I then rolled back the addon to the Dev3 copy I downloaded from here, and everyting worked perfectly again.
Updating through an auto-updater is not the best idea currently,
unless you have set it to only update from release versions.
There was for a brief period of time a beta of the next version of XLoot that Xinhuan is working on.
This is a rewrite and there was a bolded warning that none of the existing plugins would work with it.
If the updater installed that version in your interface it would break.
As well, do not use the Dev3 copy.
(it works but a couple more things were fixed and uploaded on Curse since)
are the current compatible versions at the time of posting.
Do not upgrade to the XLoot 1.x versions if you want to use the plugins.
(or until Xinhuan either makes it compatible or goes on to write plugins that work with it)
Stay with the 0.x versions for the moment and all should be ok.
Yea I had found the edit file. It's how I marked them beta in the first place since I wanted to stay with the numbering scheme Mikk started and the site auto-flags it release.
I was hoping we're not forced to flag something "release" just to update the default download.
Also the 'edit relationships' on the Actions nav menu in file page seems to be doing nothing.
The description of the intended site feature reads:
"Relationships are how your files interacts with others, mostly related to whether your file is dependent on another project." and instructions how to declare them: "Should be the project's short name or project/repository" so I assumed it's something with a bit wider scope than ##ReqDep
Whatever the intended use, it's not working :P
I made a couple commits in each of XLoot, XLootMonitor and XLootMaster
with the last few differences between the last releases and my local working copy.
I tried pretty much every option both in party and raid and couldn't cause it to error,
so it seems at a good point atm.
I'll go around removing links to temporary uploads to avoid confusion,
and try to go through proper channels for changes in the future.
(apologies for causing a bit of chaos there Mikk, Xuerian)
I have 2 small requests :)
1. Does anyone know how we can select which file will be the default for download on Curse?
Not an alpha ofc, I mean among the ones getting published there (beta and release)
At the moment it seems default download sticks with the last "release"
despite it being older than the most recent "beta".
Am I missing something or are we forced to tag "release" to update the default download?
2. Would be nice if the most current betas could be updated to WoWInterface as well.
I can't do it as there's no joint-authorship facilities I could find.
Interface\AddOns\XLoot\XLoot.lua:138: attempt to call global 'GetAutoLootDefault' (a nil value)
[C]: in function `GetAutoLootDefault'
Interface\AddOns\XLoot\XLoot.lua:138: in function <Interface\AddOns\XLoot\XLoot.lua:137>
Interface\AddOns\XLoot\XLoot.lua:259: in function <Interface\AddOns\XLoot\XLoot.lua:258>
(tail call): ?
would be nice, addon works fine, but spams that error
Took me a while to realize that you were talking about the package I uploaded.
For several of the other errors posted in this thread the lines didn't match my copy
so I assumed people were still using the old one from files.wowace.com.
I'm guessing it's happening during resource gathering? (mining/herbing etc)
... or I would have noticed sooner.