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.

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.

Well this thread certainly is a godsend for me.

Last year I used to manually break down our boss kills into single WWS events to publish them here. The way I would do it is by searching for the bosses death event then scrolling back until the pre-pull buff events occurred. You generally know how long a boss kill takes which makes it pretty easy to do this but it was still a regular pain in the arse. I haven't really made more than a token attempt to do the same for TBC raids mainly due to my own laziness. I eagerly look forward to trying out the auto log splitter.

Also over time it becomes apparent that the historical data isn't stored in the most efficient of manners. This is most noticeable when first loading the Data.xml file (which in my case has grown to well over 1MB in size) and also with the various small images that are uploaded for every single raid rather than referenced to a central path.

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?

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?

About Combat Log ranges...

I changed the config.wtf file, and it did nothing - even if the file said 200 or 150 yards, it logged only to about 50 yards.

I then tried the combat log range option in Deadly Boss Mods. With that setting at its maximum, I was able to catch things up to 100 yard away, but no farther (tested with a priest friend).

This makes a solo logger barely adequate for Gruul - the room's big diameter is about 100 yards, but if you include the mouth of the tunnel, from the fence to the other end of the room, that's about 120 yards. It will be fine for most encounters, though.

You would be pretty viable if you have a position thats somewhere near the center - usually i stand at fireblast range for max dps, but I've logged from the side too.

I don't use any boss mods or any other mod that tweaks the combat log. I'm guessing that DBM will change the range-setting to a new value, maby something lesser than 150-200.

Yeah, some Ace mods like to mess with your combatlog range themselves. I know Squishy used to--DBM as well?

I believe oTweaks can set all your range options to 200 yards. I don't have to deal with merging any logs that way.