KBAnnounce displays in your chat box all of your killing blows that occur in pvp. It keeps a running total (streak) of your kbs without dying and displays that along with your kill announcement.
-- use /kbannounce or /kba to get a list of commands KBAnnounce will accept.
note: KBAnnounce does not currently inform anyone else of your 'prowess' but in later releases will add an option to change where the announcement is displayed.
-- version: 1.5.7
- toc updated for patch 4.2
-- version: 1.5.6
- toc updated for patch 4.1
- bug fixed pertaining to the addition of a new combat log parameter, which caused lua errors.
-- version: 1.4.6
- toc updated for cata (yes, this should have been done a long time ago :D)
-- version: 1.4.5 (a)
- the true fix for self inflicted damage errors.
-- version: 1.4.4
- fixed the issue causing wow to give a lua error on use of abilities such as shadow word: death, when you cause damage to yourself.
-- version: 1.4.3
- some issues caused in instances with certain boss abilities being classified as players, but not counted specifically as such and so had no GUID, have been resolved.
-- version: 1.4.2 --
- toc updated for 3.3
-- version: 1.4.1 --
- using a wrong variable for determining who killed the player and so the display of npcs would have a |c in front of their name
-- version: 1.4.0 --
- added faction specific colors. Horde players will see their kbs announced in red and alliance in blue.
- fixed issue where if the player was killed by a pet or a vehicle the killer's name wasn't displayed correctly.
- fixed a problem causing the killer to be sometimes confused with the target of the player.
Getting this error message popup every so often, not sure what causes it, and it doesn't seem to stop KBAnnounce from working, but nonetheless here it is:
[14:29:50] Interface\AddOns\KBAnnounce\KBAnnounce.lua:108: Usage: GetPlayerInfoByGUID("playerGUID")
[C]: ?
[C]: in function `GetPlayerInfoByGUID'
Interface\AddOns\KBAnnounce\KBAnnounce.lua:108: in function <Interface\AddOns\KBAnnounce\KBAnnounce.lua:35>
I've not been keepingup on this addon up recently, but I knew about that issue and finally found time to work on it, hopefully it should be fixed completely now.