- Version 2.6.2 modifies the way coordinate data is saved, please make a backup of your saved variable folder just-in-case *
I have updated Frenn's original addon which keeps track of your killed mobs, own deaths and highest hits/crits per spell/skill.
Full credit to Frenn for the excellent work done.
Original Addon: http://www.curse-gaming.com/en/wow/addons-239-1-kill-log.html
As this version is based on the original Kill Log released by Frenn, I do suggest that before you run it, you make a backup of your
+ Version 2.6.2a
* Bug Fixes:-
Fixes bug with debugging messages with fresh installs only (this version is not needed if you are updating from an earlier version)
Installation Guide
- Exit "World of Warcraft" completely
- Download the mod you want to install
- Make a folder on your desktop called "My Mods"
- Save the .zip/.rar files to this folder.
- If, when you try to download the file, it automatically "opens" it... you need to RIGHT click on the link and "save as..." or "Save Target As".
- Extract the file - commonly known as 'unzipping'
Do this ONE FILE AT A TIME!
- Windows
- Windows XP a built in ZIP extractor. Double click on the file to open it, inside should be the file or folders needed. Copy these outside to the "My Mods" folder.
- WinRAR: Right click the file, select "Extract Here"
- WinZip: You MUST make sure the option to "Use Folder Names" is CHECKED or it will just extract the files and not make the proper folders how the Authors designed
- Mac Users
- StuffitExpander: Double click the archive to extract it to a folder in the current directory.
- Verify your WoW Installation Path
That is where you are running WoW from and THAT is where you need to install your mods.
- Move to the Addon folder
- Open your World of Warcraft folder. (default is C:\Program Files\World of Warcraft\)
- Go into the "Interface" folder.
- Go into the "AddOns" folder.
- In a new window, open the "My Mods" folder.
- The "My Mods" folder should have the "Addonname" folder in it.
- Move the "Addonname" folder into the "AddOns" folder
- Start World of Warcraft
- Make sure AddOns are installed
- Log in
- At the Character Select screen, look in lower left corner for the "addons" button.
- If button is there: make sure all the mods you installed are listed and make sure "load out of date addons" is checked.
- If the button is NOT there: means you did not install the addons properly. Look at the above screenshots. Try repeating the steps or getting someone who knows more about computers than you do to help.
Translations
When you download a mod, please be sure that the mod is compatible with your translation of wow. Some mods only work on the US versions, while some only work on some of the various European versions. These variations are called "Localizations".
TOC Numbers (Out of Date Mods)
When Blizzard patches WoW, they change the Interface number. This means that all mods will be "out of date" unless or until the author releases a new version for that interface. Some people go into the .toc files and update the numbers themselves, but this is STRONGLY advised against as it will cause problems locating possible incompatibilities addons. When you log into WoW after a patch, you DO NOT have to delete your interface directory. All you have to do is simply tell WoW to ignore the interface numbers and load all the mods anyway. All you have to do is, while at the "character select" screen, look in the lower left corner and click on the "addons" button. A window will pop up listing all your installed mods.
If you look in the upper left corner of that window there should be a box that says "Load Out of Date AddOns". You want to CHECK this box. Now simply go into WoW normally and all your mods should load. As of the 1.9 patch, you will have to do this after EVERY patch/update that Blizzard posts! If you encounter any problems with a mod after a patch, please be sure to let the author of the mod know so they can fix it.
See also: About "Out Of Date AddOns"
Mac Support
WoW addons are not platformed based. As such, they can be used on either Mac or PC. You can extract both .zip and .rar files on a Mac using StuffitExpander.
Directory Structure
World of Warcraft
|_ Interface
|_AddOns
|_*AddonName*
|_ *AddonName*.toc
|_ *AddonName*.xml
|_ *AddonName*.lua
|_ (possibly others as well)...
- +0
- Thumbs Down
- Thumbs Up
Waywocket saidThought I'd add an update: I've updated the version at wowinterface - actually a while ago but I forgot to mention it here :p.
- +0
- Thumbs Down
- Thumbs Up
Detritis saidJust to let everyone know, I currently do not have time to actively maintain this addon and as such I have passed ownership to another willing author.
I am uncertain if he will update this site as well but for now you can get a fully working version at http://www.wowinterface.com/downloads/info6695-KillLogReloaded.html
Regards,
Detritis
- +0
- Thumbs Down
- Thumbs Up
Tobelia saidWould it be possible to get an update for patch 2.4?
- +0
- Thumbs Down
- Thumbs Up
Crazytoo saidOk signed on the next day and it works now, Who knows...... Thank you for a nice mod
- +0
- Thumbs Down
- Thumbs Up
Crazytoo saidTried v2.6.2a and I can not get it to track. Death tab and list tab are blank. All it shows is I killed a lvl 1 bug and after I signed off and back in that was gone also. I am a lvl 70 and was killing lvl 63 to lvl 70.
- +0
- Thumbs Down
- Thumbs Up
Gossamer saidOn my warlock it is not keeping track of my kills.
Any suggestions on what to do?
- +0
- Thumbs Down
- Thumbs Up
Detritis saidJust a quick fix for a silly debugging message I put in the wrong place causing problems for people doing fresh installs.
Anyone updating from an older version need not worry with the 2.6.2a update.
Detritis
- +0
- Thumbs Down
- Thumbs Up
Detritis saidHi All,
Sorry for the absence, finally managed to get a level 70 and able to do some proper testing.
2 Changes for this version, First redid the way coordinate data is stored (reduces the file size nicely) however when you first login the changes being made will cause a delay, depending on how much data you have. Second is the fix for the unreliable data recording for max level.
Thanks smeehrrr I had found the problem but was struggling to find time to correct and post the update.
Regards
Detritis
- +0
- Thumbs Down
- Thumbs Up
smeehrrr saidOK, got it. The fix is in KillLogFrame.lua. You need to wait for the PLAYER_ENTERING_WORLD event before UnitLevel("player") will return accurate results.
To get this working right now, add a RegisterEvent call for PLAYER_ENTERING_WORLD into KillLogLoadingFrame_OnLoad(), and replace the KillLogLoadingFrame_OnEvent function with this:
function KillLogLoadingFrame_OnEvent(event)
if ( event == "PLAYER_ENTER_COMBAT" or event == "PLAYER_REGEN_DISABLED" ) then KillLogLoadingFrame.combatEnded = nil; DebugMessage("KL", event.." >>> combat", "helper"); elseif ( event == "PLAYER_LEAVE_COMBAT" or event == "PLAYER_REGEN_ENABLED" ) then KillLogLoadingFrame.combatEnded = GetTime() + 5; KillLogLoadingFrame:Show(); DebugMessage("KL", event.."- +0
- Thumbs Down
- Thumbs Up
smeehrrr saidI went and debugged this, so now I know what the problem is, I just need to figure out how to fix it.
In KillLog_LoadData, when my level 70 logs in, the characterLevel variable gets set to 0 - UnitLevel("player") is returning bogus data, possibly because the player hasn't officially entered the world yet. Because of this, NoXpGain doesn't get set to true, so the addon expects me to be gaining XP for killing mobs, which of course I can't. If I reload the UI, the same function gets called with a different result and my kills start getting counted.
If I can figure out the fix, I'll post it here.
- +0
- Thumbs Down
- Thumbs Up
smeehrrr saidAnyone know of a good mod similar to this one that works at level 70?
- +0
- Thumbs Down
- Thumbs Up
Clark saidFor some reason, 2.5.2b will record kills for a level 70 in instances, but not outside. Or Perhaps it is in groups and not solo. I am not sure.
- +0
- Thumbs Down
- Thumbs Up
Heckler said@ Det
lol yea, fair enough. It's still a pretty good revival anyways. If there's anything else I can do to help just let me know =)
Edit: The error occurs when I try to click the Level 70 tab. When I click the lvl 70 tab, scrolling also doesn't work properly for some reason. Only the first entry scrolls, and everything else stays the same =\ It's also not recording my kills at all again. I tried killing some Teromoths, but nothing.
- +0
- Thumbs Down
- Thumbs Up
Detritis said@ Heckler
Ha very frustrating trying to trouble shot something when I know what the problem is but I got no way of testing it :(
The error you are seeing is part of the debugging I was using to sort the colors in the level list. I will have to dig a little deeper to see if I cant spot something I missed somewhere.
I hope to release a new version tomorrow which will sort the error you are getting and hopefully make the recording a little more reliable
Regards
Detritis
- +0
- Thumbs Down
- Thumbs Up
Heckler saidHmm, so after some use, it recorded alright for some mobs, but I was out farming elementals today and it failed to record any of my kills. Yesterday I did an instance, and it recorded kills no problem.
I also got this error when I went through my KL frame
Error: attempt to concatenate local 'levelValue' (a nil value) AddOn: KillLog File: KillLog_ListFrame.lua Line: 168 Count: 2
- +0
- Thumbs Down
- Thumbs Up
Detritis said@ Runob
Moved into the release section for now as I am also having trouble accessing the beta tab :P
Detritis
- +0
- Thumbs Down
- Thumbs Up
Detritis saidPosted a beta version to attempt to fix the bug with Kill Log not recording kills once you reach level 70.
It has not been tested as I don't have a level 70 myself so any feedback would be appreciated.
Regards
Detritis
- +0
- Thumbs Down
- Thumbs Up
Runob saidThe tab for "Beta" on cursegaming doen't work for me since yesterday...
- +0
- Thumbs Down
- Thumbs Up
Detritis said@ Heckler
That was one of the limitations in the original Kill Log, Frenn got around it by gathering details for the mob you currently have selected and if it died it logged it and if another mob died and it wasn't selected, well you missed out.
I found this method was very limiting in group and raid situations once you reached maximum level if you were a healer class for instance as 9 times out of 10 you wouldnt select a mob anyway and thus not get credited with any kills.
There is a test for maximum level in at the moment however I had to adjust it to handle people who might not have the expansion installed, thus level 70 wouldnt be their maximum.
Not having access to a level 70 myself I couldnt say if something might be going wrong with the check, it might be being reset back to 60 instead of 70 and so it would still be expecting you to gain xp from the kill and not logging it correctly.
I will recheck it and see if it might be doing that.
Regards Detritis
- +0
- Thumbs Down
- Thumbs Up
Heckler said@ Detritis
You know what I think it is... when you reach lvl 70 you no longer gain xp from killing mobs. Would that have anything to do with it?
I only have 1 lvl 70 character, but after clearing my KL database, it still doesn't record kills on my lvl 70.