Getting the most out of WoW Web Stats - Page 11

Raencloud · 06/26/07, 9:09 PM

Does loggerhead automatically set the combat range to 200 or will I be forced to do it manually? I did install this and I tested it in Dun Morogh but I don't remember it changing combat logging range and I couldn't figure out any way to adjust anything, even zone selections (since I wanted to remove the zone I was testing).

P.S. I know how to change the "very high" setting to 200 across the board, its the sliders that causes the problem, as they will only go to 100. So when I select very high setting (200 yard range) it only will go up to high. If anyone can take a look at the code and figure out how to make the sliders go up higher that would fix it I would assume.

Apate · 06/28/07, 1:07 PM

Is there a way to view an individuals performance across multiple raids? Our tank wanted to see Stalwart vs. Nightbane across all the logs that we have uploaded.

Malan · 06/28/07, 1:09 PM

I don't believe there's a functionality for that - although if you still have the log files you could maybe roll all the nightbane logs together into one parse?

Arnath · 06/30/07, 7:11 PM

Has anyone ever tried merging a log from a PC with a log from a Mac? The two times I've tried, merging gets some way through and then just hangs and starts using up all my clock cycles. I feel like the PC/Mac thing has to be the issue at this point because I know I've merged logs before. Anyone have any insight on this?

Malan · 07/01/07, 2:23 PM

Originally Posted by Arnath

Has anyone ever tried merging a log from a PC with a log from a Mac? The two times I've tried, merging gets some way through and then just hangs and starts using up all my clock cycles. I feel like the PC/Mac thing has to be the issue at this point because I know I've merged logs before. Anyone have any insight on this?

Works fine for me. I'm on a mac and have had several people on PCs send me logs that I've merged.

◊ Kyth · 07/01/07, 2:57 PM

I merge mac/PC logs each day. Although I'm having some problems, I don't think they're related to the platforms.

Apsalar · 07/07/07, 8:56 AM

There is one question i have about WWS. I'm a rogue with 22%+ hit, but according to WWS i'm missing 4.3% of my SS and 5.2% miss on white attacks. I'm lost as to why i have 4.3% miss with SS while i'm only missing 5.2% white attacks. Does WWS count dodge and parries as misses?

• Chicken · 07/07/07, 9:00 AM

If you haven't fiddled with the configuration and thus have everything showing with default settings, the miss column is a total of all attacks that failed to hit for any reason. So yes, in this case it counts dodges and parries for miss. You can, however, enable it showing dodges, parries and misses separately by pressing the 'config' button.

That's assuming you're using WWS hosted on Lossendil's site, I can't speak for how things work (or don't) on a locally generated WWS.

Apsalar · 07/07/07, 9:46 AM

Yes I use the Lossendil site. Thanks for the info

Letters · 07/09/07, 1:27 AM

Was it ever confirmed that you cannot increase the range of the combat log anymore? And if you can, what's an easy way to test it.

sovelis41 · 07/09/07, 1:42 AM

Originally Posted by Letters

Was it ever confirmed that you cannot increase the range of the combat log anymore? And if you can, what's an easy way to test it.

Everything I've parsed this week has been accurate and I only use my logs, so I assume it still works.

Zindel · 07/09/07, 5:57 AM

Originally Posted by Apsalar

There is one question i have about WWS. I'm a rogue with 22%+ hit, but according to WWS i'm missing 4.3% of my SS and 5.2% miss on white attacks. I'm lost as to why i have 4.3% miss with SS while i'm only missing 5.2% white attacks. Does WWS count dodge and parries as misses?

Yes. Dodge/Parry/Resist are all counted as misses.

◊ Cadfael · 07/09/07, 6:38 AM

Originally Posted by Letters

Was it ever confirmed that you cannot increase the range of the combat log anymore? And if you can, what's an easy way to test it.

Apparently it wasn't possible on the PTR 2.1 - it works fine on live realms though. So: No, you can still increase the log range. Get yourself some macros handy to set it to 50 or 200, switch your combatlog on/visible and take a friend to do some effects that show up in your log. Set the log to 50, let him do the effect. Walk away until you don't get it anymore, expand to 200, see it again. Easy to test.

I've recorded a Void Reaver kill from last week here http://www.lossendil.com/wws/?report=s4zv62iiglsqu

Even though as a Shadow Priest, I have to go more to the center area due to range restriction from Mind Flay, I'm pretty sure that I wouldn't have recorded all events from everyone, if I didn't expand the log range. (Unrelated: Yes I know that I suck by eating that much orbs, I was there the first time, still got some problems with running correctly, but I did far better than some of the new recruits we were bringing along that night)

Now for comparison, here's the very same fight taken by one of our Hunters, who stands at max range away:

http://www.lossendil.com/wws/?report=t4lxu3y2kyzxq

He *also* had log range expanded. He wouldn't have seen anything beyond Void Reaver because he tries to stay at 40 yards away and definitly wouldn't get the players opposite from him at max distance.

The stats are identical (well mostly, a bit leeway for different settings and different quality of the parsers, his logfile is done with the german client, while I play with the english client).

So once and for all

Yes, you can currently increase the log range, and you should do so in any case if your system and network connection can handle it. I found that when I do the stats with extended log range, I don't need to merge logs with anyone else, it doesn't change a thing.

Apate · 07/09/07, 2:42 PM

Originally Posted by Cadfael

Apparently it wasn't possible on the PTR 2.1 - it works fine on live realms though. So: No, you can still increase the log range. Get yourself some macros handy to set it to 50 or 200, switch your combatlog on/visible and take a friend to do some effects that show up in your log. Set the log to 50, let him do the effect. Walk away until you don't get it anymore, expand to 200, see it again. Easy to test.

Cryect posted both the discovery of the range limit on PTR and the confirmation that it did not go live. So, if you are the trusting sort, you can find it via the search engine on these forums.

Redslayer · 07/09/07, 8:41 PM

Originally Posted by Whiteknight

I paid for a 3 month subscription for the ultimate version of the online hosting. Cost a whopping $27. And I'm really really happy with it so far, I no longer need to manually trim the combat log before uploading - I just host the full 30mb log file for our entire dungeon run and it splits everything out nicely for me, including boss attempts that don't result in kills and trash. The additional features are totally worth such a small fee in my opinion.
Just take a collection from folk in the guild if you don't want one person covering the entire cost, or have folk take turns in paying for a month.

I see my small contribution as incentive for Lossendil to keep making improvements, which I feel is totally worth the cost.

Do we have to have a paid account to use this splitting feature? Or an enhanced version of it? Because in the paid account info it doesn’t state it as a paid feature.

Schnappi · 07/10/07, 12:09 AM

Originally Posted by Redslayer

Do we have to have a paid account to use this splitting feature? Or an enhanced version of it? Because in the paid account info it doesn’t state it as a paid feature.

It's free. Paid versions skip the queue and keep your logs for a longer period, but the base functionality is the same.

Althir · 07/10/07, 2:03 PM

Originally Posted by alcaras

There are several posts in various threads that mention WoW Web Stats, but there isn't a thread dedicated to getting the most out of this wonderful tool. Hopefully this can be that thread.

WoW Web Stats, for the uninitiated, is a Java-based combat log parser. To get it to work, a player edits their WTF file to set their combat log range to max (I believe 200), then types /combatlog (to start logging), engages a boss -- or an entire instance, and then types /combatlog (to stop logging). They then fire up the Java-based combat log parser at http://www.lossendil.fr/serendipity/ and upload the HTML output to your guild's webspace. There's more, as you might imagine, but that's the gist of it.

My questions are several:
- How do you use WWS in your guild? (e.g. do you parse just boss fights or entire instance runs? what are the advantages of parsing entire instance runs?)
- Any tips for using it, or useful UI mods? (e.g. AutoCL, hosted on lossendil's site, will automatically turn on your combat log when zoning into an instance -- is there a similar mod that will turn it on when engaging a boss?)

We've just started using WWS recently; for example, last night's (somewhat messy) Gruul kill: http://humility.subcreation.net/raids/20070424-gruul/ Right now I've only been logging boss fights and parsing those, but it's a bit of a pain to both remember to turn on the combat log and later extract the appropriate boss fight from the log manually.

In any case, I hope this thread can blossom into a rich discussion of how to get the most out of WWS

As inexperienced as I am with WWS, I think it's an amazing tool, especially for "casual" guilds trying to break into difficult content (Making the Karazhan --> 25 man leap).

I have two questions, that may have been answered already, but I'm at work and can only browse.

1) How do you edit the WTF file to make the maximum combat log range 200 yards?

2) If you type /combatlog to start the log, then /combatlog to turn it off... if you type /combatlog a 3rd time, does it start a NEW log, or does it merely resume the previous one? I'm curious if I need to go delete the log for each raid, or if it will automatically start a new one.

Samadhi · 07/10/07, 2:21 PM

1) How do you edit the WTF file to make the maximum combat log range 200 yards?

I recommend you use Loggerhead to handle this automatically for you. Otherwise, the instructions are on the WWS site.

2) If you type /combatlog to start the log, then /combatlog to turn it off... if you type /combatlog a 3rd time, does it start a NEW log, or does it merely resume the previous one? I'm curious if I need to go delete the log for each raid, or if it will automatically start a new one.

It resumes the previous one. You can archive or delete the log as you wish.

Whiteknight · 07/10/07, 4:07 PM

Originally Posted by Redslayer

Do we have to have a paid account to use this splitting feature? Or an enhanced version of it? Because in the paid account info it doesn’t state it as a paid feature.

It requires the hosted version, but you can use a free account.
Local WWS parses don't have this functionality - you have to split the combat log manually.

Abbi · 07/10/07, 9:56 PM

Originally Posted by Samadhi

I recommend you use Loggerhead to handle this automatically for you. Otherwise, the instructions are on the WWS site.

It resumes the previous one. You can archive or delete the log as you wish.

Except on the Mac, where a new /combatlog will overwrite the previous one.

Malan · 07/10/07, 10:45 PM

Originally Posted by Abbi

Except on the Mac, where a new /combatlog will overwrite the previous one.

Odd, that's not how it behaves on my power mac, it pauses/resumes logging to the same log.

Abbi · 07/10/07, 10:55 PM

Originally Posted by Malan

Odd, that's not how it behaves on my power mac, it pauses/resumes logging to the same log.

Hm. I was inaccurate; I blame the fever I'm running.

On my Mac, it appends until you log out. At that point, if you log back in and do /combatlog, the old log is overwritten.

I even tested it this time. Phew. Could be a PowerMac vs. Intel difference.

Ngita · 07/10/07, 11:33 PM

On my Intel imac it overwrites the current log if you log out. I have a few times ended up overwriteing it from forgetting that.

Malan · 07/11/07, 12:34 AM

Well yah, if you log out and back in, it overwrites the file completely. But if all you do is /combatlog over and over, its just appending to the end of that file. Same behavior on mac and windows I should think.

Mulva · 07/11/07, 12:55 AM

On windows no matter what you do it keeps appending. I once wasn't paying attention during AB weekend and I was logging for basically an entire weekend straight with 200 yard range. The file was a little over 150 megs by the end of it, and spanned 3 days, and probably a dozen sessions. Guess I deserve it for accidentally saying yes to logging when I first zoned into AB after installing loggerhead =).