As i mentioned before, the HeadCount.BOSS_TARGET table isn't used at all, so adding Champion's Cache to it would be pointless at present. I'm not entirely sure why the loot is assigned to Trash Mobs when nothing else has been killed though... i'll have to investigate further.
Trash mobs is default because - HeadCount.DEFAULT_LOOT_SOURCE = L["Trash mob"] in HeadCountConstants.lua and the loot management source menu in HeadCountFrames.lua .... I believe
You get the [Trash mobs] in the loot announce and default loot source but in the dropdown menu for where it drops from you can change it to the correct boss, meaning Trash mobs is default for a loot item.
So, if it is important for you to know where or what boss an item dropped from you will need to change the loot source manually when entering in the item cost and saving it to your raid record. You just don't get the pretty announcement with the proper boss, but your record will be fine when exported.
I didn't look through all the code but that's what it seems, and I know I've corrected some "Trash mobs" to the proper boss via loot management popup window.
Yeh, I often have to change trash mob to the proper boss (as the boss always gets added now, at least). There must be something that's causing the last killed boss to default to trash mobs though even when the last mob killed was a boss (which is causing the default to be wrong).
Some bosses weren't appearing in the dropdown before my wave of patches as their kills weren't recognised, but at least they are selectable now.
Ok, looking through the code i've worked out why sometimes loot will get assigned to Trash Mobs when its looted. Basically, when a looting message is seen like "X receives loot: Y", HeadCount attempts to work out the source of the drop by scanning every raid member's target to see if it's a boss mob, and it's dead. If a dead boss isn't targetted by anyone then it will fall through to trash mobs. So for any encounter that doesn't leave a corpse and leaves a chest instead (or just any boss that is killed but no one has the corpse targetted) won't be picked up as the default loot source and would need to be changed in the loot management popup (or manually if you don't use the popup). For bosses that do leave corpses, keeping the corpse targetted is a sure-fire way to get the loot assigned to that boss by default though.
I've managed to find a minor bug with the Northrend Beasts encounter that is causing a boss kill to be logged when Gormok dies, not when Icehowl dies due to the fact that there are no other active living bosses known. I think i've got a solution (moving gormok + jormungars to the blacklist, leaving just icehowl in aliases) but it needs testing.
The patch is at http://paste.wowace.com/1088/ against mainline/trunk if anyone gets a chance to test it before me. An easy way to test is to switch on boss kill announces - if it announces only after Icehowl dies, its working :)
Not sure if this is a bug, or just something weird, but if you suspend headcount and then type /hc gui instead of showing an error message suggesting that the addon is suspended, or just doing nothing the gui pops up and throws a bunch of errors.
sorry for my bad english, i play on zhTW locale, it shown the errors like this:
HeadCount-1.6.0\HeadCountFrames.lua:2065: attempt to index field '?' (a nil value)
<string>:"*:OnEnter":1: in function <[string "*:OnEnter"]:1>
HeadCount-1.6.0\HeadCountFrames.lua:2091: attempt to index field '?' (a nil value)
<string>:"*:OnEnter":1: in function <[string "*:OnEnter"]:1>
HeadCount-1.6.0\HeadCountFrames.lua:2116: attempt to index field '?' (a nil value)
<string>:"*:OnEnter":1: in function <[string "*:OnEnter"]:1>
Yeh, as HeadCount isnt localized in zhTW it's quite probable that HeadCount is getting the zhTW zone name from WoW and trying to use that to look up zone/instance info which wont exist as it's not translated.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumPatch against mainline/trunk (r94): http://paste.wowace.com/1002/
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumFixes a bug in esES locale, and a typo in one of the Twin Val'kyr's names.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAdd ruRU locale provided by StingerSoft in Ticket 104
Remove packager meta-info from SVN
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumFix that:
In file HeadCountConstants.lua find
add after:
In en_US.lua find:
add after:
In ru_RU.lua find:
add after:
p.s attached updated russian localization
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYou get the [Trash mobs] in the loot announce and default loot source but in the dropdown menu for where it drops from you can change it to the correct boss, meaning Trash mobs is default for a loot item.
So, if it is important for you to know where or what boss an item dropped from you will need to change the loot source manually when entering in the item cost and saving it to your raid record. You just don't get the pretty announcement with the proper boss, but your record will be fine when exported.
I didn't look through all the code but that's what it seems, and I know I've corrected some "Trash mobs" to the proper boss via loot management popup window.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSome bosses weren't appearing in the dropdown before my wave of patches as their kills weren't recognised, but at least they are selectable now.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe patch is at http://paste.wowace.com/1088/ against mainline/trunk if anyone gets a chance to test it before me. An easy way to test is to switch on boss kill announces - if it announces only after Icehowl dies, its working :)
HeadCount-1.6.0\HeadCountFrames.lua:2065: attempt to index field '?' (a nil value)
<string>:"*:OnEnter":1: in function <[string "*:OnEnter"]:1>
HeadCount-1.6.0\HeadCountFrames.lua:2091: attempt to index field '?' (a nil value)
<string>:"*:OnEnter":1: in function <[string "*:OnEnter"]:1>
HeadCount-1.6.0\HeadCountFrames.lua:2116: attempt to index field '?' (a nil value)
<string>:"*:OnEnter":1: in function <[string "*:OnEnter"]:1>
is it the new difficulty of instance?
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse Premium