Getting the most out of WoW Web Stats - Page 9

Abbi · 06/08/07, 3:31 PM

Lossendil has announced the fees for hosting. The original post is here; here's the summary of the levels:

1) Free. This account is ad-supported. Reports are hosted during 15 days.

2) User : $2/month. This account is ad-free and get a high priority in the loading queue. Reports are hosted during 15 days.

3) Guild : $5/month. This account is ad-free and get a high priority in the loading queue. Reports are ad-free, get a high priority in the loading queue, and are hosted during 30 days.

4) Unlimited : $9/month. This account is ad-free and get a high priority in the loading queue. Reports are ad-free, get a high priority in the loading queue, and are hosted while the account is active.

All reports hosted on a high priority account always are viewed as high priority reports -- i.e., if I shell out nine bucks a month, anyone looking at my logs gets the faster load.

Cel · 06/08/07, 4:17 PM

Originally Posted by Abbi

Lossendil has announced the fees for hosting. The original post is here; here's the summary of the levels:

All reports hosted on a high priority account always are viewed as high priority reports -- i.e., if I shell out nine bucks a month, anyone looking at my logs gets the faster load.

If guilds could get a history page like the one generated with the locally hosted reports, but with the extra features of hosting on Lossendil's server, that would be really attractive.

Abbi · 06/08/07, 4:25 PM

Originally Posted by Cel

If guilds could get a history page like the one generated with the locally hosted reports, but with the extra features of hosting on Lossendil's server, that would be really attractive.

Funny you should ask. You have to log in with an account to host a report now, and it collects all logs posted on that account onto a history page. In some ways it's better, since it also collects individual kills and posts them on the same page. It doesn't include the Player feature the way the locally hosted ones do, though.

Belenos · 06/08/07, 4:54 PM

Originally Posted by Shaker

I'm just starting to use this - and I'm having an issue. I use the log splitter to split up our various attempts, and when I update them, the pages generate great, but the history page gets overwritten.

So last night we had 5 HKM pulls, the 5th being the kill, and 7 Gruul attemps. When I generate the report for Gruul1, it works fine and shows up in the history ... when I generate the report for Gruul 2, even though the timestamp is different, it replaces the Gruul1 row in the history report. New directory, new everything else... destroyed history page.

Any tips?

I read somewhere that if two attempts/reports are within a half-hour of each other, WWS will only keep one of them in the history file. So if you log each attempt separately instead of just logging the kill attempts or whatever, the history page entries may get wiped. I don't know of any way to override this.

Nite_Moogle · 06/08/07, 5:58 PM

Originally Posted by Tehehe

Does anyone have a good way to deal with really huge combat log files? I have a mod (LoggerHead) that auto turns on the combat log in raid instances I want, but it is making the log file huge. After a couple days of raiding, I've found myself stuck with a 65mb file that I cannot split in any editor (just lags up and freezes) and is too big for WWS to parse.

I was thinking it would be nice to have a little utility that would run through the log file and split the log into seperate files each time there's a ~1 hour gap of no info. That way I can run the log in raid instances all week and at the end of the week run the log file through the utility and have it spit out a file for each night's raiding.

http://www.noobschoolbus.com/wow/WoWLogSplitter2.zip

Source code included (or will be when the stupid cache on the site gets the right version posted, I stuffed the wrong file in by mistake the first time). Should chop a standard combat log file in to either daily or hourly segments and place them in the same folder as the original file. I only had one combat log on hand to test it with so it may not work, let me know if you have trouble.

Will require the .NET 2.0 Framework if you don't have it already, but WAU also requires it so I bet you'll have it.

jurgen · 06/10/07, 1:18 AM

Curious as to how I can expand my combat log range to 200 yards and/or confirm it's been done once I have. thanks in advance

edit: if this has been answered before I'm sorry

Tehehe · 06/10/07, 6:04 AM

Originally Posted by Nite_Moogle

http://www.noobschoolbus.com/wow/WoWLogSplitter2.zip

Source code included (or will be when the stupid cache on the site gets the right version posted, I stuffed the wrong file in by mistake the first time). Should chop a standard combat log file in to either daily or hourly segments and place them in the same folder as the original file. I only had one combat log on hand to test it with so it may not work, let me know if you have trouble.

Will require the .NET 2.0 Framework if you don't have it already, but WAU also requires it so I bet you'll have it.

Thanks, this is basically what I wanted, but I made a small change to it. Because sometimes our raids go over midnight and the log for one fight may span two days I made the following change to line 87.

from:

if (thisHour > lastHour && checkBox_hourly.Checked == true)

to:

if ((thisHour - lastHour)%24 > 1 && checkBox_hourly.Checked == true)

To split the file when there is a gap larger than 1 hour in the log file.

srg · 06/11/07, 4:43 PM

My log splitter that was posted in here a while ago has become less and less reliable. Can someone please link me a combat log splitter that can parse 2.1 logs without a problem. For some reason mine locks up and does not allow me to split it up. Normally I'd just do it manually, but that takes a lot of time, and with multiple attempts on a boss it makes it nearly impossible.

Regards!

Whiteknight · 06/12/07, 6:06 PM

Is there a convenient way to strip out the DPS contribution for a player-damage spell? For example, I'd like to see the DPS done to raid mobs in Vashj, but I don't want the DPS numbers polluted by the Static Charge damage (which one player does to nearby raid members).

Same deal with Shatter (Gruul).

• mutagen · 06/12/07, 6:20 PM

Originally Posted by Whiteknight

Is there a convenient way to strip out the DPS contribution for a player-damage spell? For example, I'd like to see the DPS done to raid mobs in Vashj, but I don't want the DPS numbers polluted by the Static Charge damage (which one player does to nearby raid members).

Same deal with Shatter (Gruul).

While WWS lists stuff like Shatter damage on each player screen the total damage numbers shown are "Damage done to foes", it doesn't include the Shatter damage.

http://www.lossendil.com/forum/viewt...hp?p=2862#2862

Crepe · 06/14/07, 3:37 AM

What's the difference between "Miss%" and "Resist%" for damage-out spells cast by the player? Partial vs. full resists? Interrupted spells (mana, canceled, etc.)?

Polleke · 06/14/07, 5:37 AM

For direct damage spells the miss% is are the full resists (countered by +hit gear). And the resist% are for partial resists (countered by +spell penetration, warlock curses).

For DoTs they were recently removed because while full resists do show up, not all applied show up.

Solstice · 06/15/07, 11:32 AM

I'm curious as to how accurate the reports I've been getting are. I have my combatlog set to 200 yards range - I added the lines mentioned earlier in this thread to my config.wts file, and made it read only to prevent bigwigs(?) from reverting it to default.

However, I still seem to be missing rather alot of data. Take our last Vashj kill for example:
http://www.lossendil.com/wws/?report=avf6zlyd6pdpk
The hunters, dps warriors and erm, a lock + mage were dpsing elementals in phase 2. If you click dps time you'll note that these 6 all have low dps time %s, which skews the report somewhat. I obviously missed alot of their data somehow, although I'm not sure whether it was a range issue (the room surely doesn't span more than 200 yards) or something to do with LoS.

Anyone have any tips as to how to improve accuracy without merging more logs?

Nomad_Wanderer · 06/15/07, 4:06 PM

Originally Posted by Solstice

I'm curious as to how accurate the reports I've been getting are. I have my combatlog set to 200 yards range - I added the lines mentioned earlier in this thread to my config.wts file, and made it read only to prevent bigwigs(?) from reverting it to default.

However, I still seem to be missing rather alot of data. Take our last Vashj kill for example:
http://www.lossendil.com/wws/?report=avf6zlyd6pdpk
The hunters, dps warriors and erm, a lock + mage were dpsing elementals in phase 2. If you click dps time you'll note that these 6 all have low dps time %s, which skews the report somewhat. I obviously missed alot of their data somehow, although I'm not sure whether it was a range issue (the room surely doesn't span more than 200 yards) or something to do with LoS.

Anyone have any tips as to how to improve accuracy without merging more logs?

Um, why not just merge more logs? Get one of your melee, preferable even your MT to send you the log (zip + email)

When I was doing our guild uploads, I asked a few healers and the MT to submit their data. So I had usually a total of 3-4 logs.

Every log adds data. Granted the 4th log usually only added 1-2%, but over a 4 hr raid, imo even 1-2% can be worth looking at.

It's not like merging them is difficult. The author has done a good job.

Malan · 06/16/07, 10:41 PM

Does anyone know if the WWS author is planning on making the outputs from the local hosted versions start looking a bit more like the paid-for hosted ones? Even if not as "pretty" with all the java scripting going on, I'd appreciate if the stat rollups were at least calculated the same way.

• Miles · 06/17/07, 12:19 AM

Not sure if it's worth a new thread as the project is just getting started, so replied @ WWS @ interface forum.

[semi off topic]

I'm not too fond of projects going commercial, so I used the last two days to lay the foundation of a WWS replacement. Ever increasing free reports queue times, logs deleted after 15/30 days, I think it would be so much easier if people can host it themselves.

I just recently discovered the tool, and while it does a lot of good things out of the box, it still can't compete with Recap in stats gathered, for example. But I'm going off-topic on my own post now :P

The problem with WoW and combat logs is that alot of people can code pretty well, but they are scared by the work involved to deformat the combat log. For example, WoW has 21 different ways to say a is immune to b's c attack. For those I have good news, I'm past the point where logs can be decomposed into a large, machine readable array - our first Gruul kill for example. A sample 'hit' event:

  280 => 
  array (
    0 => '6/3',
    1 => '23:25:16.268',
    2 => 'hit',
    3 => 
    array (
      'source' => 'Zalamander',
      'victim' => 'Gruul the Dragonkiller',
      'skill' => 'Scorch',
      'amount' => '1522',
      'element' => 'Fire',
      'isCrit' => true,
      'isDOT' => false,
      'isSplit' => false,
    ),
  ),

As you can see, all lines are transformed into a parserLib (@wowace) compatible format, see sct\libs\ParserLib\ParserLib.lua, line 160-183 for details. After that, you can run pretty much any filter you want on the data. It shouldn't be hard to generate a WWS-like output with much more data at your disposal. One of our tanks suggested a Threat & Rage used plugin, others want to graph the dps, tps, damage done etc, against time.

It's written in php + mysql, with an Access .mdb (+odbc) as pattern config frontend. Because the php-part uses some libraries from my work, it's non releasable yet. I think I'll just keep it simple and release the base text -> parserLib format converter asap and let other coders dream up applications. License will be MIT as usual.

Suggestions, questions, inquiries: pm / mail (booink at gmail dot com). I'm not sure people appreciate this thread going off topic even more.
[/semi off topic]

Apate · 06/19/07, 1:34 PM

Is there a way to view reports that are attached to a single guild but uploaded by two different users? (do paid accounts make a difference?)

IE, I upload for one group, someone else uploads a second group, but we both input Apatheia - Khadgar as the Guild - server.

exarkun · 06/19/07, 5:55 PM

Originally Posted by Miles

Not sure if it's worth a new thread as the project is just getting started, so replied @ WWS @ interface forum.
.
.
.
Suggestions, questions, inquiries: pm / mail (booink at gmail dot com). I'm not sure people appreciate this thread going off topic even more.
[/semi off topic]

Sounds like a great idea to me. the wws site is getting slower, and the queues longer every day. Local hosting for guilds would be great.

Renalia · 06/19/07, 6:28 PM

Do you guys have any tips on what to do if one of your raiders has the same name as a boss?

One of our warlocks happens to be named Nightbane, and you can imagine what the WWS site looked like after a night of attempts on said named flaming dragon.

Corinthian · 06/19/07, 6:32 PM

Originally Posted by Renalia

Do you guys have any tips on what to do if one of your raiders has the same name as a boss?

One of our warlocks happens to be named Nightbane, and you can imagine what the WWS site looked like after a night of attempts on said named flaming dragon.

There isn't much you can do, as WWS can't tell them apart based on the combat log. Hunter pets with duplicate names cause the same issue.

You could always report the player for violating name policy... :P

Renalia · 06/19/07, 6:37 PM

Originally Posted by Corinthian

There isn't much you can do, as WWS can't tell them apart based on the combat log. Hunter pets with duplicate names cause the same issue.

You could always report the player for violating name policy... :P

Well, technically Blizzard stole his name, since he's had it since before TBC, but what can ya do. I figure we'll just stop bringing him.

Morrigan · 06/19/07, 7:37 PM

The warlock himself could do the combat logging, then he would only appear as "You" in the combat log and you can substitute it with another name (WWS does this for you).

Apate · 06/20/07, 6:30 PM

Originally Posted by Renalia

Well, technically Blizzard stole his name

You can still petition if it is a better option than not bringing him.

• Erongg · 06/21/07, 11:52 AM

If I want to extend my combat log range to 200 for accurate WWS reporting, will this screw up my Grid 40-yard 'Out of Range' fading?

Malan · 06/21/07, 12:07 PM

Originally Posted by Erongg

If I want to extend my combat log range to 200 for accurate WWS reporting, will this screw up my Grid 40-yard 'Out of Range' fading?

No you'll be fine.

Question - Is WWS unable to parse Demo Shout being applied to a mob? None of my local hosted ones show it and I'm curious if it just can't pick that up or if my warriors are really that lazy.