I think this wasn't addressed on this thread yet. When I try to split a log I always get an error. Say for instance at Kael'thas I only want to see the charts for the weapons phase. I go to Timeline & Splitting, click where the weapons first appear, drag it till the advisors reappear, click split. This is what I always get:

"An error occured while loading your report. Please try again in 30mn. If the problem persists, please report the bug on the forum."

This is the same if I want to see only vashj p2, etc. Any ideas how to make this work?

The website is showing as down for me at the moment, but I'm fairly sure Presence is essentially the Five Second Rule, if it applied to anything combat-log-able a player does. Or, put another way and don't be too literal with this, time spent spirit-regening is essentially non-present (presence).

Hi Golias,
Can you report this error on the WWS forum, if it is not resolved please.



Hi Llilyth,
This not so "straigth" (i don't know if the term is correct), the major reason of a decreasing presence is the range, if you made an action during the 5s cycle you'll not be afk, neither a death in fight or loot time, etc.
But since the splitting system is active, splitted periods decreases the Presence's algorithm accuracy. This will be updated in a later time to be more efficient on a defined period.

I've tried putting those lines in my config.wtf . But, after launching the game, and going back later to check, those lines have been removed. Any idea why they dont stay in the config?

I've since created macros to do it manually, plus I've downloaded LoggerHead and will give that a try.

Does anyone else have issues with fights that take place in large areas (Lady Vashj is the main example) being logged improperly?

I think it may be beacuse the fight's extremeties are farther than 200 yards away. I know an ingame channel synced program always lists our damage and healing numbers differently than a single-person WWS parse.

The person doing the uploading isn't merging any logs with anyone else, and plays a rogue. He does have combat log range set to 200. Perhaps he's on the other side, and is more than 200 yards away?

I haven't done any testing so I don't know if that's the case, but has anyone else experienced that?

I don't know if combat logs are automatically trimmed during combat, but I know that out of combat I can see a rogue gain and lose stealth at the entrance to Gruul when I am halfway between Gruul and Maulgar.

I've heard tell of a "death replay" function in WWS.
How does that work?
Are there any guides for getting some of the more advanced information out of WWS?

Thanks.

--edit--
One other thing. Does a successful application of sunder armor actually show up on the combat log? Taking a look through ours, it looks like our tank's sunders ALL were missed or parried or dodge.

It's one of those easily overlooked features of WWS, all you need to do is click on a player and you'll see something similar to "1 Death : 13:43 (Gruul the Dragonkiller) ". If you click on the time you'll get the last 30 seconds before the player died .

See Wow Web Stats :: View topic - [New] Death replay for more info.

A successful Sunder Armor doesn't appear in the combat log as an ability cast by a player, you just get Mob X is afflicted by Sunder Armor.

You just need to click on a person. However this only works on the server hosted version.

My own testing found that having a low view distance prevented combatlog reporting things that happened out of your vision range. I commonly get that on void reaver.

Thanks.

I posted a bug report on the forums. I'm sure they'll get right on it.

According to this post he's not getting accurate parses for RoS either.
You can see his parse seems to be missing some data (Each of the souls has the same hit points normally right?) and is split into 3 "attempts" on different bosses.

What I've found with RoS is the only good way to go is to parse out your log separately for each phase of the fight. Search for the "Essence of Anger dies", then search for "gains aura of anger" then work your way up cutting chunks out for the 3 phases. It's a pain in the ass to do, but is the only good way I've found.

Note that you won't be able to find "essence of desire/suffering dies" so I just pull from the last reference to that boss.

Alternately have a shaman drop a marker totem between each phase.

I logged our SSC run last night and I merged 2 different logs. I'm almost positive they weren't picking up everything. Here's our Lurker kill:

Loading...

First thing that indicated something was wrong was that our SWStats of that fight was different... The two locks, Loocifus and Tricodin were much higher on SWStats. I noticed that their dps time was much lower on WWS than the third lock, Fallenx. I know these two locks were doing damage the whole time, cause their adds on their islands were dying and obviously, they were attacking Lurker... especially since their dots are ticking the whole time he's above water.

I'm guessing that another addon maybe the culprit and is resetting the combat logging range (both of the loggers had edited their config.wtf file to extend it to 200 yds). The addons I use are: Deadly Boss Mods, Omen, SWStats, Sorren's Timers, Atlas Loot, and CTMods. The only one that I've seen mentioned in this thread as maybe causing a problem with this has been Deadly Boss Mods. I know the mage that was logging was also using DBM.

Does anyone know for sure if DBM resets the logging range and if there's a workaround for it? I've seen some people recommending Loggerhead. Has this worked for any of you? I'd like to make these reports as accurate as possible, so any recommendations that you fine folks have are appriciated!!

Have any of you guys had problems with DPS time% recorded in the WWS logs? I personally am trying to figure out why even though I have great DPS, my DPS time is about 15-20% below other raiders. For example, on Lurker, as a destro lock I spam SB the whole time. I can guarantee that I didnt miss a beat on DPSing, yet my DPS time % was about 63% where as the mage on my platform was at about 85%. Why isnt my DPS time up there and is there anything I can do to increase my DPS time %? I use quartz and on lurker I DPS while in the water of course. I wonder if its an internet connection problem, but quartz should take care of that. Any clues?

Thanks for the help Vorda. I had a hunch about the fireball dot difference, but the logs you found helped prove that. In my guild I dont really have anyone else to compare with in how we output dmg so thanks again for the log links.

Spiderella essentially got to the bottom of it. From my experience the combat log has a larger range for damage done than for healing so if you compare it to damage meters you will find the damage done to be more or less exact while the healing done to be off.

Interestingly enough we kept finding that the total healing done was the same between WWS and SWstats but the effective healing done was way off. We finally figured out that if the target being healed was out of range of the person logging the combat log then those heals were being counted as overhealing.

Edit: Using two combat logs cuts down on these type of discrepancies.

Is there a way to remove Trash from the WoW Web Stat report besides manually stopping /combatlog during Trash?

Ok, So I have skimmed most pages of this post, and do not recall seeing the answer to my question.

How exactly does one ensure that the combat log change 'worked'? Is there a place on the WWS log/tool that shows this?

My thanks to all who have contributed here. I was seeing some glaring differences between the WWS log, my Recount damage report and the Recount damage report of our Hunter.

After some discussion with our raid leader I learn't that his range was set to 100, not 200 as my Recount is. I have directed his work web trolling efforts to this forum.

Is there any way to work around this? I have one more than one occasion frustrated myself by logging an entire instance, and then swapping in an alt for the last fight and losing all the data I had collected that night >.< It's not good for my blood pressure! (this is on a mac, though I can't tell from the comments if it's exclusively a mac thing or not)