Comments on: WoW Nerdy – Managing the WoW Combat Log

By: Klimes

Klimes — Tue, 01 Jun 2010 19:13:22 +0000

wow, nice post, I was wondering the same thing. and found your site by bing, many userful stuff here, now i’m a bit clear. I’ve bookmark your site and also add rss. keep us updated.

By: tburns6

tburns6 — Mon, 14 Dec 2009 20:17:15 +0000

I tweaked your script to just rename and add to the zip file.

rem @echo off
REM WoWLogCleanup.cmd
REM Renames the WoW combat log file with date and adds to zip.
c:
cd “c:\temp\code\junk”

REM Format the date for file name.
for /f “tokens=1,2″ %%u in (‘date /t’) do set d=%%v
for /f “tokens=1″ %%u in (‘time /t’) do set t=%%u
if “%t:~1,1%”==”:” set t=0%t%
set timestr=%d:~6,4%-%d:~0,2%-%d:~3,2%

REM Rename current log.
ren wowcombatlog.txt wowcombat_%timestr%.txt

REM ZIP up datestamped log and add to zip file
“C:\Program Files\7-Zip\7z.exe” a WoWCombatLogs.zip wowcombat_%timestr%.txt

REM Delete unzipped log-file

Del WoWCombat*.txt

By: Broliant

Broliant — Thu, 03 Dec 2009 18:19:05 +0000

@James
Thanks for the tip – the idea of the “leave 0P” is to have chomp remove all of the current contents of the file leaving “zero percent” behind. I am still using the same version of the chomp program that I downloaded back in June/July so if it no longer works the same way, your comment is much appreciated.

I’d be tempted to test various options such as “leave 0.0P”, “leave 0.01P” and so on to have chomp remove the maximum amount possible – I would not really want it to leave me with 150mb. I could do “leave 0.01M” according to the command-line help though if the ‘percent’ based options don’t yield the right kind of results.

Either way, thanks for noting your findings and solutions – hopefully it’ll be useful to somebody who follows in the same footsteps.

By: James

James — Thu, 03 Dec 2009 18:06:46 +0000

@Broliant
BTW… if users copy & paste your above code using the August 09 version of Chomp you get an error which will prevent it from executing. However, I found modifying the following line …

> “C:\Program Files Public (x86)\Chomp\chomp.exe” WoWCombatLog.txt leave 0P /CRLF >> chomp.lst

… to …

> “C:\Program Files Public (x86)\Chomp\chomp.exe” WoWCombatLog.txt leave 15P /CRLF >> chomp.lst

… resolved the issue. Of course, users can choose which size in MB (so, my chunks are 15MB) they want their chunks to be, but the 0 just wasn’t working at all for me. Hope this helps, and thanks again for the pre-work!

By: James

James — Wed, 02 Dec 2009 22:50:50 +0000

@Broliant
Thank you very much for the reply. I’ve gone ahead and configured everything and I’m going to give it a shot. This combat log so far has been a royal pain.

By: Broliant

Broliant — Mon, 30 Nov 2009 02:15:09 +0000

@James This works perfectly well for me under patch 3.2 so I'd say yes. It should continue to work until Blizzard change something fundamental about the combat log again.

By: James

James — Mon, 30 Nov 2009 02:02:26 +0000

This appears to be exactly what I have been looking for. I’m assuming this method has been tested (to some degree) and continues to work soundly with Patch 3.2? I’m not sure why it wouldn’t, but I thought I would ask before going through the process of trying to set it up on my personal machine when I get home!

By: Author

Author — Fri, 28 Aug 2009 20:34:25 +0000

Hi. Good to see someone else making use of “Chomp”. I thought you might like to know that, at long-last I’ve added the ability to “chomp-into” another folder/directory and also to suppress error messages to piping into 7Zip is improved. See v1.04 on the site. I’ve only just hacked the code so if there are any problems pls let me know. Regards MS. Use CHOMP.EXE /? for info on the new commands.