Comments for Broliant Writes...

Comment on RealID – Convenience That Costs You Your Privacy. by Mike

Mike — Tue, 29 Jun 2010 00:51:41 +0000

Exactly what I have been thinking myself. Advertisers have discovered gold in social networks and blizz is after part of that pie.

From blizz’s perspective, the best group to use this feature, is not the real friends only types… it’s the casual “friender” with a 200+ facebook friends, half of which the person knows from online and not very well.

Comment on RealID – Convenience That Costs You Your Privacy. by WoW Player

WoW Player — Mon, 14 Jun 2010 16:06:07 +0000

Was googling to see if other people felt like I do, and I absolutely agree with your statement. I will not be using this system, mainly because it conflicts with my privacy and reveals all my characters. I have several alts that I play and level from time to time, when I feel like being more alone in the game.

Comment 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.

Comment on Patch 3.2 Killed Level 39 Twinking Stone-Cold Dead. by Anonymous

Anonymous — Sun, 07 Feb 2010 22:07:44 +0000

Unfortunately for me, I just decided to make a 19 Twink and after finally gearing him out and expecting some good Twink on Twink action, I was whispered and told that as a 19 Twink, I would never get into any WSG. I wondered why and gave it a shot. I sat in the WSG queue (XP off) for upwards of 4 hours without so much as a hiccup. Twinking has been killed, slaughtered, nerfed, destroyed. While I didn’t exactly want to go in and senselessly kill undergeared players, I did expect at least some sort of action as I thought the Twink community was pretty active. Guess I was wrong, which sucks. Oh well, back to mindless raiding on my 80′s.

Comment on WoW Nerdy – Managing the WoW Combat Log 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

Comment on Single Minded Focus: Raiding with Combat Post 3.1 by jeadaroescono

jeadaroescono — Sun, 06 Dec 2009 21:41:21 +0000

“Stay cool, guy. The shit’s really going to hit the fan tomorrow. Lots of changes coming.”
——————————————
создание сайтов москва внсъд

Comment on WoW Nerdy – Managing the WoW Combat Log 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.

Comment on WoW Nerdy – Managing the WoW Combat Log 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!

Comment on WoW Nerdy – Managing the WoW Combat Log 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.

Comment on WoW Nerdy – Managing the WoW Combat Log 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.