Yes just once per loading WoW.
I did tests with a warlock guildie to see if adding to the config.wtf did indeed work. We went to the Elemental Plateau. He would start dot'ing mobs and I would start at 40 yards (information gathered with Cartographer). I would then slowly move back, to my suprise(gasp) 50 yards was the limit.

I then executed the macro at 40 yards. I then slowly moved back and got to around 125 yards clearly reading all his dmg in my combat log. I ran out of room to try the full 200, and was truthfully to in a hurry to restart it all. 125 was a suffice distance to prove that it can work with a macro.

I do not know if others have had luck with adding it to config.wtf or not. This is just my personal experience.

Yes, config.wtf is loaded once on startup. Any change during run time of the game in this file is discarded since WoW overwrites its content on exit. Just edit it when the game is not running and you'll be fine.

When the game is running you have to use the macro command and when you quit afterwards, you will have the entries in your config.wtf.

In short:
- game running: use macro, addons use the SetCVar call.
- game not running: edit config.wtf

I have no idea where the comment in bigwigs comes from that it wouldn't work anymore. I run around with 200 all the time and I get a hell lot of info from afar which I don't get when I turn it down. Works for me I guess *shrug*

I just wanted to add to the thread that changing the global variables holding the log strings also change your combat log so it's not seperated and sw_fixlogstrings also affects the combat log.

Does anyone have newer version of AutoCL or something similar to auto log combatlog?

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

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.

BTW, one thing I noticed people haven't stated yet it seems is that the combat log range will no longer be settable in 2.1.

Its really annoying and I didn't even realize at first on the PTR but your combat log files individually are pretty worthless. So, you will need to get multiple people to log the combat and use them with WWS (it will auto merge them).

This is all the aftereffect of a really bad hack to fix people being able to see combat log messages in arena during prep time (instead of actually fixing the real server code so you can't see the messages during that time).

This will also have the result of breaking a lot of boss mods that weren't syncing.

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.

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 ?