Getting the most out of WoW Web Stats - Page 18

Abbi · 05/29/08, 6:29 PM

Originally Posted by Unravel

As for creating a plot for from each stack, I'm not quite convinced that that scales well with 60 plots or so created, but I will think on it.

Well, 25 (assuming you just split DPS or HPS)... but yeah. I'm not convinced of that either. The scaling seems like it'd be wonky.

Barring that some sort of easy selection of a specific source or dest would be nice -- if I want to pick out just Bob it's a bit tricky at present.

Unravel · 05/29/08, 6:35 PM

Well, you can Tab / Shift-Tab through them, but I know what you mean.

Abbi · 05/30/08, 10:52 AM

Originally Posted by Unravel

Well, you can Tab / Shift-Tab through them, but I know what you mean.

Oh! That solves the problem OK for me. Thanks!

Okerhs · 08/10/08, 6:55 PM

Originally Posted by Nidaa

Hello, my first post on EJ's forum

I didn't try your app because I didn't know about it, I wrote myself a similar app in Tcl (I used to write lots of scripts/app with that so ..) it split your big 200mo WoWCombatLog.txt with one file for each raid (it write a new file when 2 lines are spaced by 2 hours)

source: http://bouyou2.free.fr/WoWCombatlogSplitter.tcl
compiled .exe file (with zazoutcl): http://bouyou2.free.fr/WoWCombatlogSplitter.exe
Virustotal. MD5: c657ebdd9b0170c3b125b6b0c59d163e

Just put it on World Of Warcraft/Logs and run it, it will save your time for upload logs to wws

Thank you for this little app, I used to upload the combat logs for my old guild to wws and when i joined my new guild I forgot about keeping the log to a reasonable size.

Our usual uploaders were not in the raid this evening so I just had to go through a 2 gig CombatLog which would not open in notepad, wordpad or textpad and kept freezing up my pc by using all 4gigs of memory trying to open it....

Asmodeu · 10/15/08, 11:25 PM

I'm sure I'll get in trouble for bumping this up but I didn't know where else I could get a decent answer.

Lossendil has not posted on the wws forums since june 26. The current WWS engine does not work for 3.0, and there has been no response in terms of updates.

Any idea on whether we should cancel the subscription now or wait a bit; and whether or not there is anyone trying to work up a decent replacement or pick up the reins of WWS incase he has gone for good?

dcwarlord · 10/16/08, 12:29 AM

Asmodeu - Yea I am getting the feeling WWs is dead for now. The forums are loaded with people complaining about not being able to host their logs and many have paid for the service.

I was poking around here looking for another way to host this data.
We are very interested in seeing data from our 1st BT raid after the patch.

Anyone know another way to parse the combat logs and achive similar results to WWS?

Ramsden · 10/16/08, 2:16 AM

Same here. I saw something on a chinese website (I think) that people were using for beta stats. Anyone have any alternatives if no news from Lossendil?

Midnight · 10/16/08, 7:23 AM

I used stasiscl (link) for my betalog of Naxx (example of Patchwerk: link). It´s not as easy to use, needs to be hosted by yourself (or watched locally) and doesn´t show as much details as WWS does, but at least it works.

Chtoll · 10/16/08, 11:13 AM

Someone made a small tool that turns your logfile into something that WWS can process : Convert your combatlog from 3.0.x to 2.4.x

As for an alternative, WOW Meter Online - More logs!!!!!! seems to be getting more popular now.

racy · 10/16/08, 12:17 PM

Originally Posted by dcwarlord

Asmodeu - Yea I am getting the feeling WWs is dead for now. The forums are loaded with people complaining about not being able to host their logs and many have paid for the service.

I was poking around here looking for another way to host this data.
We are very interested in seeing data from our 1st BT raid after the patch.

Anyone know another way to parse the combat logs and achive similar results to WWS?

You can use my parser, Wow Log Parser.

Wow Log Parser - Addons - Curse
or
Wow Log Parser forums

The HTML output function gives this kind of results, but you have to host the files yourself somewhere.
They in TK 080929

Skyblaze · 10/17/08, 11:18 AM

There is a statement now in the Bug Forums:

3.0.2 Log files will be OK soon

Wow Web Stats • View topic - 3.0.2 Log files will be OK soon

Kjallstrom · 11/11/08, 5:36 PM

I see in the thread history a few people have purchased accounts. I've purchased a guild alliance account for use by our raid leaders and class advisors. Do those of you that have the alliance account publicize the report-listing URL to all of your members, or keep it officers only?

On the one hand, I want people to want to check up on their own performance... but on the other hand, we don't want people getting obsessed with performance (we're pretty casual, a "guild that raids", not a "raiding guild") nor obnoxious with eachother about numbers. What kind of availability do you use? (We do link individual reports to individual players when a class advisor is helping them understand their performance.)

Isin · 11/25/08, 11:56 AM

As an individual raider, it is useful to be able to look at stats, even if not just to compete for performance. For example, if I get a new trinket with a strange proc on it, wowwebstats will tell me how many procs I got over a long fight, and it helps me improve my gear from day to day.

That being said, WWS seems to be completely unusable for most fights right now. The chinese alternative mentioned above is not parsing my log files either.

Namuh · 12/24/08, 11:04 AM

What is the format for the WWS Timestamp?
HH:MM:SS:SSS (hour, minute, second, 1/10ths)
or
MM:SS:SS:SSS (minute second, 1/10ths, 1/100ths)

Seems it would be the second to account for the sheer # of hits going in

04:21'04.184 Icecicle gains 71 health from Coralirodeth Vampiric Embrace. (71 Overheal)
04:21'04.219 Icecicle gains 478 health from Hawkslayer Judgement of Light. (478 Overheal)
04:21'04.235 Icecicle Rune Strike hits Patchwerk for 3344 Physical.
04:21'04.625 Icecicle gains 46 health from Coralirodeth Vampiric Embrace. (46 Overheal)
04:21'04.771 Patchwerk Hateful Strike hits Icecicle for 22817 Physical. (1844 Absorbed)

Fireye · 12/24/08, 12:20 PM

Originally Posted by Namuh

What is the format for the WWS Timestamp?
HH:MM:SS:SSS (hour, minute, second, 1/10ths)
or
MM:SS:SS:SSS (minute second, 1/10ths, 1/100ths)

Seems it would be the second to account for the sheer # of hits going in

04:21'04.184 Icecicle gains 71 health from Coralirodeth Vampiric Embrace. (71 Overheal)
04:21'04.219 Icecicle gains 478 health from Hawkslayer Judgement of Light. (478 Overheal)
04:21'04.235 Icecicle Rune Strike hits Patchwerk for 3344 Physical.
04:21'04.625 Icecicle gains 46 health from Coralirodeth Vampiric Embrace. (46 Overheal)
04:21'04.771 Patchwerk Hateful Strike hits Icecicle for 22817 Physical. (1844 Absorbed)

I'd imagine (just looking at the timestamp) that it's:
HH:MM:SS:MS (millisecond)

... seems like the most logical way to break it down.

bigwadds · 12/31/08, 2:28 PM

Last I checked WWS still had issues with DK pets and some other things. I have been working on a combat log parsing site and it's finally complete enough to let people try it out. The site is called Big Picture and it's at http://www.wowbp.com

I'd love to get any feedback from people and I setup an email address at wowbpbugs@gmail.com so people could get in contact with me. There is a sample fight on the front page so you don't have to sign up or upload a file to check it out. I would love for people to upload files though as that is the part I am most worried about working right now.

Feist-Mok · 01/02/09, 7:51 PM

Originally Posted by bigwadds

Last I checked WWS still had issues with DK pets and some other things. I have been working on a combat log parsing site and it's finally complete enough to let people try it out. The site is called Big Picture and it's at http://www.wowbp.com

I'd love to get any feedback from people and I setup an email address at wowbpbugs@gmail.com so people could get in contact with me. There is a sample fight on the front page so you don't have to sign up or upload a file to check it out. I would love for people to upload files though as that is the part I am most worried about working right now.

Upload feature doesn't seem to work atm with a zipped combat log for me. It uploads, but then I go to the portal and nothing's there.

I'd love a viable alternative to WWS, and WMO is... well, a clusterfuck from what I can tell, so best of luck to you.

For those that are also looking, I've also been playing with Home | DejaWoW.com the past few days, and the UI is promising, but it feels pretty unfinished, and seems to have issues here and there as well (Not seperating a patchwerk wipe from a subsequent patchwerk kill for instance).

bigwadds · 01/03/09, 12:46 AM

Thanks for letting me know. I will take a look at it, I definitely see what you are talking about and I will let you know when I can get it fixed up. I know there have been quite a few people sign up and send me comments after reading this, I appreciate everyone's input.

Schneeb · 01/06/09, 3:37 PM

Not hugely on topic but im lost as the documentation for stasis seems pretty sparse!

Looking at Archavon there is each fight in the 'raid' listed when hovering over the current fight. How do you achieve this? Im currently using abbi's php history page (Raid History) but no parses seem to get added together in such a way (the fights I want are usually the only thing in the log.txt, fresh log each raid)

Im running stasis like so: "perl stasis add -dir wwwfolder -ver 2 -year 2009 -file "loglocation"

I've tried -overall and -collapse but not knowing exactly what they do is frustrating (do i need to use -attempt too?)

Finally found the comments I was after (in the stasis file not parserdotpm)!

You may provide various options after the action. Some of them will be
required and some will be optional, depending on what action you select.

B<-file>      Specifies the combat log to read.

B<-dir>       Specifies in which directory the generated HTML is living
           or will be written, depending on action. Default is the
           current directory.
           
B<-server>    If present, Armory links will be included using this server.
           Only works with the US armory for now.

B<-version>   Either 1 or 2. Pre-2.4 combatlogs should be parsed with
           version = 1, post-2.4 combatlogs with 2. Default is '2',
           the new post-2.4 style.

B<-logger>    Name of the logger, optional argument only used when parsing
           version 1 combat logs. Default is 'You'.

B<-minlength> Exclude encounters less than this amount of seconds.
           Defaults to 30 seconds.
           
B<-attempt>  Include a parse for boss attempts (not just kills).
               
B<-trash>     Include a parse for trash mobs (all sections of the log that
           were not part of a boss encounter).

B<-combine>   Include a parse that rolls up all attempts and kills on each
           particular boss (one extra parse per boss).

B<-overall>   Include a separate parse that rolls up everything in the log
           file.
           
B<-collapse>  For boss attempts and kills, collapse all mobs that have the
           same NPC ID and all pets with the same name and owner. This
           is always done for trash parses to save space, but by
           default is not done for boss parses.

B<-nav>       Add a cross-split navigation menu to each parse.

The option I was after was -nav, which does throw up a forwards compatability warning but its working for now.

Alamir · 01/11/09, 10:23 AM

I have a mod that measures uptime on buffs. I used it the other day to calculate uptime for Berserker on mh white damage. It is very simple and I have validated results several times by watching the mod tick appropriately when the buff was active or inactive.

Anyway, I ran an approximately 2.5 hour test, which resulted in a total Berserk uptime of 24.36%. I used WWS to parse the combat log file, however and got an uptime of about 19.6%. I am baffled by this inconsistency.

To calculate the berserk uptime from WWS, I just took the total seconds dpsing (10160) from WWS and divided by the total uptime of Berserk (calculated as number of procs * 15 secs) and then divided the two numbers.

So, from WWS, the calculation is (133 * 15) / 10160 = 19.63%.

I am confident, however, that the real number should be closer to 24.36% and am very confused. Could I be losing data somehow in the combat log? Is WWS inaccurate? Did I do the calculation wrong? Anyone have any ideas?

Here are the WWS stats Wow Web Stats

a civilian · 01/14/09, 8:10 AM

If berserk (or any buff) is refreshed while already active, this is not counted as a gain in WWS.

• Kalroth · 01/14/09, 8:53 AM

Originally Posted by Alamir

I just took the total seconds dpsing (10160) from WWS and divided by the total uptime of Berserk (calculated as number of procs * 15 secs) and then divided the two numbers.

So, from WWS, the calculation is (133 * 15) / 10160 = 19.63%.

The short answer is; both you and WWS are wrong.

In the logs you had 182 procs, but 49 of those were refreshes. 182 - 49 = 133, which is what WWS counts (as already stated in above post).

Your uptime calculation is incorrect because Berserk can refresh itself: Berserk buffs on Alamir

05:45'41.856 Alamir gains Berserk.
05:45'45.043 Alamir's Berserk is refreshed.

This is two procs, but only a total uptime of ~18 seconds.

• Koban · 01/15/09, 8:37 AM

If you manually browse the log you can see the refreshes as well.

WWS Loading...

Alternatively, to determine the uptime for something you can also upload your log to WMO.
They recently implemented tracking uptime for buffs/debuffs and as far as I can see this does take into account refreshes.

example:
WWS Loading...
6 Berserk gains
Wow Web Stats
12 Berserk procs

WoW Meter Online - The Best World of Warcraft Combat Log Analyse System!Fully support Wrath of the Lich King!
"Buffer" tab
Berserk: 12 procs, 126 seconds for a total of 68% uptime during that fight.

If I'm not mistaken they also do parses for the heroic training dummy.

zushiba · 02/05/09, 5:41 AM

I've been messing around a bit with stasiscl, I want others to be able to upload their own logs so I wrote a quick uploader that allows them to upload a .zip, it decompresses it for them on the server and then parses it. The problem I'm having is how incredibly slow it is!
A standard Naxx run, full clear is taking 15 - 20 minutes to parse, is this normal or have I done something wrong? The log file itself is say ~126 MB, 9megs zipped.
Is it a problem with PHP's exec() just being lame because I don't recall it being quite this slow from the shell.

Schneeb · 02/06/09, 11:11 AM

I run a windows batch file at the moment (so a direct 'perl' command), a 150mb log file only takes 5 minutes max for me (core2 E6600/4gb of ram); do you not see the logs appearing one by one?