I use the one linked to from the WWS site, it works perfectly fine. You might need to check "load out of date addons" in game, but other than that, it's great.

Does it pick up on new boss encounters? After reading that description it seems like it only applies to pre BC instances.

It works fine in TBC, at least up through Magtheridon. In fact it works a little too well, I turned logging on for some of my first heroics and forgot to turn it off and had a great big log full of (now) irrelevant 5 man content.

ah .. and you can increase the combat log range .. but it does not affect all spells... you get damage done far away but e.g. you don't get seduce notices, counterspell, pummel or polymoph log entries if you are just a few yards away

Just configure it to log in whatever zones you care about.

Sorry to ask a silly question, but how exactly do you edit the config.wtf file to extend the range of your combat log? I know where the actual file is, and maybe I'm dumb (I'm not too good with these things!), but I didn't see a combat log range option to adjust, and assuming it's not even in there and I have to plug it in myself, I don't know the specific command/phrasing of it. So yeah, any help would be great. I don't use any mods, and the idea of having to run two macros to set the range to 200 every time I open WoW seems a little undesirable if I could just figure out how to alter the .wtf file.

But anyway, this thing seems very very cool so far. I've just recently decided that I'd like to start running it for my guild, and keeping track of my own and others' DPS, and how specific/detailed it gets is great. But in all likeliness, I'm going to be the only one in my guild gathering data/using it, so I'd just like to make sure that it's as accurate as it can possibly be, and we're not all relying on it to be... reliable, only to have it not be because my combat log doesn't pick up all the relevant data due to range restrictions. Don't want to be going by something that could be grossly inaccurate on any fight taking place over a large area, you know? But it seems like it's extremely reliable and the range thing isn't a big deal for most people, so I'm pretty excited to check it out on Mag or Hydross or some other DPS fight.

UG this will make Gruul WWS almost impossible to do. Getting 6 people + in my guild all running WWS properly and submitting logs fast would be impossible and they would still miss stuff with people being so spread out.

Can you confirm that this goes beyond the present situation? By that I mean one can kludge mods that overwrite that range by manually entering /console SETs presently in-game. If not then I can only say "aw shit..." because I regularly am the only one logging our WWS data.

Not that I don't believe you, but is there any reference of a posting that says this is not a bug ?

I don't find anything in the ui&macro forum, bug report and test realm forum that says anything about this. Neither does Iriels' collection of changes in 2.1 posting list anything even remotely hinting at a change like this and quite frankly, it doesn't really make sense.

Could it be that only within arena, the range is limited somehow ?

I use an Ace mod called LoggerHead, which is awesome.

You might miss events occurring around some of the ranged dps/healers (like shatter), but any damage done to gruul will still be easy to track by one person.

How do you fit this all in one macro? It's 297 characters (42 over the macro length limit)

You make 2 macros then...

You don't have to be in melee range to record damage done to gruul, just within the combat log range.

Anyone found any proof to this post?

Yesterday was the first time I used wow web stats during our Gruul kill, this is the result:

http://www.lossendil.com/wws/?report=azeh3vfnqmk1q

I noticed a big variance in presence %, has anyone got an idea what causes that? I made sure to set the combat log range to 200 yards using the /console SET commands mentioned above.

I originally intended to delete the .txt combatlog between attempts to keep it accurate, but Windows didn't let me as it reported the file was in use, this is after I turned the logging off. Manually deleting the text inside the log did seem to work, oddly.

Wow web stats also reports the fight as being 21 minutes, so I obviously did something wrong.

@f1reburn
You did not do anything wrong. The reason for your '21 minutes kill' is that your link leads to the "Full Report" of the combat log(s) you parsed. If you use http://www.lossendil.com/wws/?report...k1q&s=757,1231 instead or use the split tab right under the date/time line you can access the real try/kill and the presence-% will be fine, too.

So your log alone is no indicator for a nerfed combatlog range, in the contrary.

My log only, 3.4 million damage inc. to Gruul:

http://www.sigilguild.net/hamlet/WWS...gonkiller.html

Are you doing anything to increase the range of your combat log?

Edit: I had edited my Config.wtf file a long time ago to extend the range, but determined that the modifications were undone by an AddOn and my range had been set back to the default. Couldn't for the life of me figure out what was going wrong, I guess I should have checked the file itself sooner.

Someone just needs to write a universal combat log mod for WWS and distribute it for free if this range issue is going to be so problematic.

My point was that, as far I as can tell, nothing has changed.

Are you running the commands in a macro, or did you just edit your Config.wtf file? Sorry to keep bugging you about this, we're currently working on Gruul and I'm finding the logs to be a great resource in identifying what's going wrong with each attempt.