29 - Fails to attach proper bosses to loot or announce kills to guild the majority of the time

What steps will reproduce the problem?

1. Join a raid (10-man Firelands, BoT and so on).

2. Kill bosses

What is the expected output? What do you see instead?

Expected: the Raid Loot to be automatically, properly associated with the bosses killed. As well as to have it announce to guild (when Reporting is enabled) a proper boss killed when it is done as well as loot dropped.

Instead: the majority of the time, Raid Loot is associated to things they shouldn't be: wrong bosses or "trash loot". And the boss kill reporting failing to happen (["isBossBroadcastEnabled"] = true, is in the main SVs for the mod). The loot reporting to guild worked properly the single boss I had it turned on for, however.

What version of the product are you using?

v1.10 with the "latest" LibBabble-Zone-3.0 (4.2-release7 as of this date) & LibBabble-Boss-3.0 (also 4.2-release7) for the examples shown below. USEnglish client/server, WoW 4.2.0A live.

Do you have an error log of what happened?

No errors.

Please provide any additional information below.

Some examples of this behavior, which makes the mod something that isn't too useful currently:

- - Baelroc (Firelands boss) killed. No guild announcement, even though Reporting is turned on. Three loot drops from him, all are improperly recorded as Source: Trash mob in the Raid Loot list.

- - Lord Rhyolith (ditto) killed. Identical behavior as the above.

- - Bastion of Twilight full run. 11 loot drops. Two trash drops properly attributed to Source: Trash mob. The remaining nine drops all attached improperly to two bosses: the first one (Source: Halfus Wyrmbreaker) and the last one (Source: Cho'gall). Only five of those nine drops actually fall from those two bosses. Never saw any announcements either.

And so on. Hope this can be fixed so that recording and announcing actually works properly.

User When Change
Zidomo Aug 22, 2011 at 04:45 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of kagaro kagaro Sep 09, 2012 at 14:21 UTC - 0 likes

    ive been working on fixes for detection

  • Avatar of Zazhu Zazhu Oct 03, 2011 at 13:29 UTC - 0 likes

    We experienced identical behavior last night in Firelands 10. 3 boss kills (Alysrazor, Rhyolith, Baleroc), none of which were recorded or broadcast (even though guild chat broadcast was enabled). All the loot drops were listed as coming from Trash mobs. No errors were received from the mod.

    Version: latest 1.10 from Curse, updated prior to the raid.

  • Avatar of Zidomo Zidomo Aug 28, 2011 at 19:44 UTC - 0 likes

    And the latest run: another full Bastion of Twilight run, again only Halfus (first boss) and Cho'gall (last boss) were recorded. The other two bosses in between those (Theralion and Valiona & Ascendant Council) were not recorded, as what happened in the ticket.

  • Avatar of Zidomo Zidomo Aug 26, 2011 at 21:17 UTC - 0 likes

    For the Baradin Hold 4.2 boss listed above, under Boss Kills it has never been recorded during any run there.

    For the Bastion of Twilight run listed above with the 11 loot drops, only two bosses were recorded (those listed above)

    For the Firelands bosses listed above and some others, none were recorded.

  • Avatar of kagaro kagaro Aug 24, 2011 at 02:55 UTC - 0 likes

    is it recording the boss kills correctly?

  • Avatar of Zidomo Zidomo Aug 23, 2011 at 13:32 UTC - 0 likes

    Latest incorrect boss drop recording: Baradin Hold 10-man, doing the new-for-4.2 Occu'thar boss.

    Boss killed, improperly no announcement of such to guild, even though the option was turned on (as shown in the ticket with other examples).The T12 Paladin healing legs dropped, they were announced to guild, but with an improper Source: Trash mob attached to the text (again, as above). The loot recording attached to the raid in the HeadCount2 frame also recorded it improperly as Source: Trash Mob.

    The second piece of loot from the boss was DEd to a Maelstrom Crystal, so there was nothing further to record/announce.

    For the record, at no time during any boss kill/drop distribution either here or in the ticket examples did I leave the area or was not in the same zone. During every improper recording/announcement by HeadCount2, I was right there by the dead boss.



Last updated
Mar 30, 2012
Aug 22, 2011
New - Issue has not had initial review yet.
Defect - A shortcoming, fault, or imperfection
Medium - Normal priority.

Reported by

Possible assignees