It does not have a space, I triple-checked. Does your code care if it's UNIX or Windows line endings in the file? It's Windows. I don't seem to be allowed to post attachments, or I'd put it in here.

SplitLog1.txt is an exact copy of WoWCombatLog.txt.

One thing I realized is I use autoCL to start/stop logging when I zone into or out of an instance. Would that affect your program? Since WoW doesn't actually close the file handle, I wouldn't think so...

I wrote a small Java app a while ago to help split up combat logs for WWS. It's available at http://wow-en.curse-gaming.com/downl...0/logsplitter/. If you have Java, unzip it and run it with "java -jar LogSplitter.jar". Open up your combat log file, select the combat sessions that you'd like to save, right-click, and save.

There might be a more user-friendly way to implement it, but Java is quick and easy for cross-platform GUI apps. If someone wants to implement the ideas for something else or whatever, the basic idea was that certain things can't or shouldn't be done in combat, so chop up the log based on that (priest/pally rez, AB, AI, GotW). Also, if nothing at all happens in the log for 30s, split on that too. Then remove combat sessions under a certain duration of time or actions (to filter out actions between rezzes and buffs). Then try to figure out labels for each session using who you damaged and sort those based on how often the mobs die in the log. It isn't really healer-friendly, but if there's interest I can fix that.

I'm not trying to compete or show off or anything like that; it just sounds like something that doesn't depend on remembering to use a marker ability might help some people and it sounds like WWS didn't fully achieve the goal of combat log splitting.

Edit: put in the new URL

Just gave this a quick run through, and it worked brilliantly! Stats match up very well with the hosted WWS splits. You should look into uploading it to Curse or some such site.

As someone else said in this thread, once Lossendil lets people permanently host reports with a history page (or distributes the server-side version), I've basically got a blank check for him Certainly not trying to take advantage of his hard work. But until that time, this looks like a great compromise of features/hassle.

This is exactly what I've been working on in perl. I may abandon it and swipe your java implementation, though.

I don't want to deal with marker spells, etc. when this actually should be pretty trivially deterministic, especially since a human is reviewing the data at the end anyways.

Is there any known issues with xp pro x64?

Every time I try and run it I get a error when Ihit about 98%

Go to your actors page, find "Verypatient", and click remove selected. I find this happens a lot when I forget to type /combatlog at the end of the raid, and end up getting a few people not in the raid.

If this person is indeed supposed to be in your raid, then just add "Notpatient" to the actors.

I have a question about general /combatlog usage. I am trying to test this out while soloing, just to get a idea for how everything is put into the log. However no matter what I do combatlog.txt under \wow\logs\combatlogs.txt is empty.

What needs to be done to initiate data capturing?

Thanks in advance

-Srg-

To start logging
/combatlog

To end logging
/combatlog

To view the log you must either /console reloadui or logout; because the client will not write the file until either is done. (There is a third way to force a write)

Will it log solo activity as well or does it have to be in a raid setting? I just tried soloing a couple things and then reloaded my UI. That did not seem to pick up any data.

anything input into the combat log I believe will be shown.

Apologies if this has been answered already:
Has anyone found a way to filter 'shatter' out of the entire process of DPS/Damage calculations?

After some extensive testing I'm pretty sure the log only gets written on logout or when 128kB of data has been buffered. Do AV or so, and you'll notice that you get constant updates to it. If you're soloing you will only see updates after a long while.

I've never seen ReloadUI() or triggering garbage collecting work when less than 128kB of data was buffered.

No it doesn't care about the type of newlines, as glibc doesn't. But I think the problem is that you dont have an ending newline in marker.txt. I've got a new version that doesn't care about ending whitespace anymore. Tell me when you're still interested.

I came to the same conclusion that there is some lower bound on the amount of data buffered before it flushes to disk. No amount of reloading or garbage collecting would reliably force it.

Are you saying I need a blank line at the end of marker.txt, then? I'll try that. And I'll be happy to try your new version, too, if you post it. My day job is testing software, so I get a perverse bit of fun from this sort of thing .

Edit: Yeah, I added a newline and it just split up my old combat log nicely. Thanks for the tip.

okay, Curse doesn't like jar files, so I updated it a little and put it up inside a zip file at http://wow-en.curse-gaming.com/downl...0/logsplitter/

I updated it so that non-dps can use it too.

Can you explain this bit more? I'm unclear what your meaning is by this statement.

Originally, I wrote it for myself without thinking about anyone else really. So what I did to identify the mobs for each segment was search with regular expressions like "Your \w+ hits ([\w ]+) for \d+", and likewise for crits and melee hits/crits, extracting the thing in parens as the mob name. Normally, you wouldn't think that it matters too much if a combat session is labeled, but I found that I would get some combat sessions with junk (no combat at all) if I allowed sessions that didn't have any identified mobs in them. However, if you don't actually hit/crit anything on a boss fight (like say your die on the pull or you're a pure healer), then no mobs would be identified and that heuristic would filter out all of the sessions, cause it thinks there aren't any mobs.

Now what it does is builds a list of players based on who received buffs. Then it looks for the pattern " (\w+)'s \w+ hits ([\w ]+) for \d+", where the first group must be in the list of extracted player names. It works just as well on the logs I tested, though player names were coming up more (it seems a few people were casting while spell reflect was up or dpsing MCed folks)

What I might look into doing in the future is not only tagging lines I know to be out-of-combat, but also lines that I know to be in-combat. That way I might not be so dependent on guessing the player list to decide whether or not anything interesting happened in a combat session.

Is there anyway to go about making this more accurate for a solo combat logger? Tonight I used it, and the stats are signifigantly different from what SW Stats put out for healing.

How can I increase the combat log range, is there anything out there to make it smoother/more accurate?

There are a few methods of increasing the combat log range mentioned earlier in this thread.

One trap I fell into was disabling the default target damage in the WoW UI options including periodic damage. I think it was just after installing SCTD for the first time. Even if you have target damage disabled, you need to keep the periodic damage option switched on otherwise all DoTs and HoTs are not included in your WoWCombatlog.txt. I would think this would affect SWStats as well but who knows (the actual terminology the WoW options use for these settings escapes me at this time as I am at work and cannot check.)

An example of this stuff up on my part is here. Notice no HoTs for Priests or Druids and no DoT damage from Warlocks.

Otherwise, I can't think of any reason for your stats to be different in WWS and SWS. Did you double check all of the actors are configured correctly? I.E. friendly PCs are not set as Mobs etc.

Yep, http://www.lossendil.com/wws/?report=e2chwkbuioqog

Healers were saying the readout was far different from what SW Stats was showing them. HoTS are all there, perhaps I just need to increase the combat log range.

I'll try downloading this AUTOCL thingy, but other then that I don't see much I can do in this thread about increasing the range of my combat log.

Change 150 to what you want. 150 might not be enough for Gruul if you stand at max range. Either that or my config.wtf have been acting up

I see a lot of people talking about extending the combat log range to 200 yards, so I still felt comfortable about doing it, but now some guy in another forum told me that since 2.0 all of the settings which try to extend the combat log past 30 yards have no effect anymore and he pasted this from the BigWigs readme:

r33241 | rabbit | 2007-04-20 20:42:22 -0400 (Fri, 20 Apr 2007) | 1 line
Changed paths:
M /trunk/BigWigs/BigWigs.toc
M /trunk/BigWigs/Plugins/BigWigs_Plugins.toc
D /trunk/BigWigs/Plugins/Range.lua

BigWigs: Remove the Range plugin, since tweaking these settings have no impact any more.

Do you guys have any idea whats the deal now?

Gruuls room should be something like - 100-120 yards in diameter. I pick up everything happening in the room standing on my side of the room. I have all ranges set to 200 yards - so I assume thats good enough for me. Range can be adjusted in my opinion.