Smart combat log saver addon for World of Warcraft. It keeps track of zones for which to turn on saving the combatlog. It also enables the user to change the combatlog event tracking range.
This is mainly used in conjunction with tools like WoW Web stats: http://www.lossendil.com
In game type /clsaver to see available options. In short:
/clsaver list- Lists zones for which CombatLog is enabled
/clsaver toggle - Toggles CombatLog on/off for the current zone
/clsaver range - Displays current logging range
/clsaver range [50-250] - Sets the combat log range when logging to the given amount in yards
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
Rotha saidI keep getting this error no matter what i do.
clsaver-1.7\clsaver.lua:16: Couldn't find CVar named 'CombatDeathLogRange'
<in C code>: in function `pcall'
clsaver-1.7\Dongle.lua:247: in function <Interface\AddOns\clsaver\Dongle.lua:246>
clsaver-1.7\Dongle.lua:337: in function <Interface\AddOns\clsaver\Dongle.lua:328>
<in C code>: in function `LoadAddOn'
Interface\FrameXML\UIParent.lua:908: in function `UIParentLoadAddOn':
Interface\FrameXML\UIParent.lua:234: in function `CombatLog_LoadUI':
Interface\FrameXML\UIParent.lua:327: in function `UIParent_OnEvent':
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>
- +0
- Thumbs Down
- Thumbs Up
Mendayen saidWhat's the proper zone name for Zul'Aman? I keep forgetting to toggle it on when I get in there.
["zones"] = {
["Karazhan"] = true,
},
- +0
- Thumbs Down
- Thumbs Up
Brelkin saidZul'Aman is, surprisingly:
["Zul'Aman"] = true,
- +0
- Thumbs Down
- Thumbs Up
Linuxrules saidThanks for the advice, I'll check into that.
A related question, what is the actual maximum log range? Wow Web Stats website says 200 yards, DBM sets the range to 150 yards when "maximum" is selected, and clsaver will allow values up to 250.
- +0
- Thumbs Down
- Thumbs Up
disht saidI haven't tested to see what the actual maximum is but Blizzard's APIs accept 250 just fine.
- +1
- Thumbs Down
- Thumbs Up
Linuxrules saidUsing clsaver 1.7 and loving its lightweight design. The only issue I have is that with the log range at maximum (250) I only get a couple of Gruul's growths recorded in the log file. Are there any adjustments that can be made to log them all?
- +1
- Thumbs Down
- Thumbs Up
disht saidThere are other programs that might change the logging range. DBM is one of them. Maybe look into that one.
- +0
- Thumbs Down
- Thumbs Up
teedog saidAre there any particular advantages to using clsaver over LoggerHead?
- +0
- Thumbs Down
- Thumbs Up
disht saidOther than being simpler and much lighter (clsaver ~40KB vs LoggerHead ~520KB), no there is not a big difference between the two.
- +0
- Thumbs Down
- Thumbs Up
Andross1 saidThanks Legorol, that seems to have fixed my problem. =)
- +0
- Thumbs Down
- Thumbs Up
disht saidI have uploaded a new version that should fix or Dongle problems. Thanks for pointing this out.
- +1
- Thumbs Down
- Thumbs Up
Legorol saidI have talked to cladhaire, the author of Dongle. According to him, the problem is with the way Dongle.lua got included in clsaver. Two mistakes were made (independently, both of which would cause clsavr not to work:)
1) An untagged version of Dongle.lua is included in clsaver 1.6, grabbed directly from trunk. This must not be done, because during the tagging process additional code (DongleStub) is appended to the start of Dongle.lua. Therefore authors must include tagged versions of Dongle.lua.
2) The version included is Dongle-1.1, but clsaver is trying to use Dongle-1.0. This will not work.
cladhaire recommends including the latest tagged version of Dongle-1.0, which can be found here: http://dongle.googlecode.com/svn/tags/Dongle-1.0-r871/Dongle.lua
- +0
- Thumbs Down
- Thumbs Up
Legorol saidSame problem as Andross1. At login, get the following Lua error:
Error occured in: Global Count: 1 Message: ..\AddOns\clsaver\clsaver.lua line 1:
Debug:
Examining the Lua files, it appears that the version of Dongle.lua shipped with clsaver 1.6 expects DongleStub to be present.
- +0
- Thumbs Down
- Thumbs Up
Andross1 saidVersion 1.6 doesn't seem to work for me, the slash commands don't register or anything, as if the mod is turned off, but it's looks fine under the addon's tab... and 1.5 works fine... anyone else getting this?