Hmm, it's possible I'm an idiot! Let me look closer at this later.

Sure enough, I'm dumb. Alright, that's good then -- I hadn't poked around the XML,.

When generating logs, do you guys all use the trim feature to get the data for a specific boss fight? Do you typically have /combatlog enabled for the entire raid, or just for the boss fights? I'm still figuring out what all the options mean, and I must say the auto-split feature of the hosted reports is really nice. Haven't been using WWS for very long, and I'm sure I'm just missing something obvious here.

This is something I was wondering about. I was thinking there might be a way to get the locally saved reports to split like the hosted ones do, but I don't know how to do that.

On encounters that have a larger-than-usual combat range we've used multiple people to log at the same time and then used the script to combine them; this stabbed us in the back when Gurgthock played detective and found out that my system clock was different than Sebudai's, causing some things to be logged twice and creating a lot more work for Seb in redoing all the old logs.

When I did log, however, I had /combatlog on all the time and extracted the appropriate boss encounters by highlighting and scrolling up in Notepad (which took a good 5 minutes per boss). Is there a more efficient way to do this? I'm not totally familiar with all of the intricacies that come with the program.

I've found WWS to be invaluable for comparing my damage with the other Warlocks. The number of DoT ticks is what interests me the most, for instance trying to max out the number of ticks you can get on Leotheras without pulling aggro after a whirlwind, or just seeing the difference in the number of ticks of each DoT.

Just a quick question, is the combatlog that gets generated affected by combat log mods? Also do you have to have all the options checked off to track everyone?

That's kinda what I figured, given the fact that wow.exe locks the log file even when logging isn't enabled (preventing you from renaming the file and starting a fresh log). I'm sure it would be possible to replicate the hosted log split feature, where you just feed in a single log from the whole raid and get a bunch of files that correspond to each boss kill or attempt. From reading the WWS forums, it sounds like this won't ever be added to the standalone WWS parser, so it'd have to be a preprocessing step before you fire up WWS.

I think what would be helpful is if a veteran user of WWS could come up with a best practices type of post to help the uninitiated. Something along the lines of what do you change in your WTF folder for the combat log range, how often do you need to do this, do you rename each combat log and if so what is the easiest way to do so, etc.

I know that this info is already here on these boards in a myriad of posts but since this thread is specifically about WWS it might not be a bad idea to collate all that info here.

/combatlog is entirely external from the game's interface. Nothing you do to the interface will have any effect on what does and doesn't get recorded in the log file. It simply records everything you're in range of.

Sebudai can probably go into greater detail, but here's a basic rundown of what we do:

Before each attempt on a boss Sebudai drops a Sentry Totem. That way each attempt is separated by "Sebudai gains Sentry Totem." in the combat log, and that's a string that should never appear during an actual encounter. If/when the boss dies, the log will have "[Boss Name] dies." so you search from that, up to the last Sentry Totem gain, and that's your log.

Anyone else who was logging mails their section of the log to Seb, he deletes Rikktor's log immediately, then runs the WWS parser, saves it locally, uploads both the wws-history and the new wws-YYYYMMDD-HHMM folders to our server and that's it. Actually all you really need to upload from wws-history is the updated .xml file in that folder, I believe, but whatever!

Unfortunately the hosted version of WWS is rapidly becoming a lot better than the "local" version, because I would really prefer to have all our logs on our own server, with the History index like we have now.

Owned.

http://elitistjerks.com/showthread.p...171#post331171

At the time of this error, Rikktor was using a machine which was only getting 2fps, so it WWS could have had trouble syncing up the events (as they were recorded at different timestamps).

Great tip. I've been thinking about finding some ability i never use normally and try that. Mind Vision would work if i didn't use it to annoy our rogues so much.


How long range on the combatlog do you people use? And how many logs?