![]() |
Moonkin WWS Thread
There is a rather large number of people just posting a random WWS from a random night or a Patchwerk kill. Since most of the threads for moonkins are actually trying to accomplish spreading information, I figure we should create a single thread to post your parse in.
Feel free to ask for tips, etc in this thread, but lets try and keep the other moonkin threads as informative as possible. This will also help for the number crunchers who want to sift through all the WWSs out there by compiling them all to one post. |
You might also want to list some of the ways to read a WWS report, or point to a site that says what to look at.
I am not an expert on them, and would love to know how other people use them. |
Wow Web Stats
Patchwerk WWS, how to read this: I am not a super expert but I can offer a few things: General information - the meat of a report is the dmg. out portion. It will list the abilities you used during the reporting period and how much damage the accounted for. It then breaks these numbers out into percentages and other breakdowns of each specific spell (how man crits/hits/misses). Taking a look at mine I used 6 different abilities during the fight:
After the general break up, if you click on the total damage of an ability, it will show you more detailed stats, using my Starfire as an example we see some pretty good information: I had 19 normal hits, 37 crit starfires, so in total I casted 56 Starfires. The next line shows percentages, 34%normal, 66% crit rate on starfire over this period, On the next line we see average amount, my average non crit starfire was hitting for 5,959 damage, while my average crit was hitting for 11,826 damage. The final line is simply your max hit, for normal and critical strikes, so my max normal hit was 6,966 damage and my max critical strike hit for 14,547 damage. An important thing to watch here is in the "Missed %" column, if you are getting anything in there (aside from treants) you are not at the hit cap and want to fix that quickly. Moonfire uptime - This fight was 2min 40 seconds or 160 seconds, I had 157 seconds of DPS time, since moonfire ticks every 3 seconds, there is a total of about 52 moonfire ticks. If you look at the ability moonfire you can see there 48 ticks. These numbers should always be pretty close since we want moonfire ticking as much as possible. The "Gains, Buffs, and Debuffs" tab: This is a quick way to look over some general statistics on what people are using during a fight, taking a look at the first area the box is for energy gained. Of course we don't have energy so it uses mana. When a moonkin crits, we get mana back, from this ability I gained 22,252 mana back on 52 crits averaging 427 mana back per crit with a max of 428 back on a crit. Replenishment provided me with 7,837 mana during the fight, through 138 ticks averaging 53 mana per tick and a max tick of 54. This section continues on until mana regen abilities have all been listed. The next section here is the "Buffs Gained" this is good to see what buffs a person had that helped them do a certain amount of damage, looking at mine it shows 55 Nature's Grace procs, the next two buffs only affect melee abilities so we can skip them. The next buff is eclipse, so during the fight I had an eclipse proc 5 times. Now is the time, and Mark of the War prisoner are the trinkets I was using for this fight, and you can see how many times the proc'd here. Further down you see the speed buff, which means I used a potion of speed during the encounter. The last section here shows debuffs, the only gained is Exhaustion, from receiving the Heroism buff. The breakdown tab is a simplified view of overall data. Patchwek put out a total of 794,158 damage in 210 hits averaging 3,781 per hit with a max hit of 14,547 damage. The heals portion shows that I had Beacon of light, so all the pally heals that healed the someone else also healed me for this fight. There is more to WWS a LOT of information can be found by browsing the log file as it provides second by second details of what actions occurred so you can truly find what someone was doing during the encounter. However it takes, extreme patience to be able to read through the log file, which is why the summary provided by WWS is so helpful. Hope this helps! Edit: Wow Web Stats This link shows you syntax for browsing the log file, very helpful to filter everything out and find just what you are looking for! |
Quote:
Average damage per cast/tick (particularly DoTs and non-crit nukes) gives you a good feel for gear level and buffs. DoT uptime% (3*MF ticks divided by fight duration). DoTs per cast. Dots being clipped? Missing out on SF glyph bonus? Hits/FoN? FoN behind the boss (parries)?Hits/Starfall. Eclipse management: - Time between eclipse procs. - Getting the right eclipse? - Number of SF casts during eclipse. - Time between eclipse proc and first SF landing. Signs of mana stress? (Innervate, mana pot). Really the biggest difference is often %time spent doing something useful. In a "perfect" fight (assuming you aren't responsible for FF) that lasts x seconds: - You would have Floor(x/24) MF casts. - Floor(x/14) IS casts. (Note: I don't recommend refreshing IS during Eclipse) - Ceil(x/180) FoN and Starfall casts - Ceil(x/120) On-use trinket procs (depending on trinket). The rest of the time should be spent casting your nukes. On an unhasted basis the time available for nukes was: (x + 12s (bloodlust) + 0.5s* NG buffs gained) * haste - 1.5s * (number of MF, IS, FoN, Sfl casts) The unhasted time spent casting your nukes is 3*SF count + 1.5*Wrath count. How much time was lost? Try to find out why it was lost. Moving out of the fire is good. Stopped nuking while watching the pretty starfall for ten seconds is not good. Filter WWS to show just SF. How much time was there between SF's during obvious SF spam? The above list is always enough to tell me where I have room for improvement. I think at the top end, timing FoN (just before Bloodlust), on-use trinkets, and potions will make a difference. I'm not there yet, and I think the other items I listed would be a bigger boost to my own DPS. Edit: Looking at just a couple of these things in Elit's post: Filter the log file for just MF. He managed to clip a few MF ticks. Also, his last MF only got four ticks (that is ok. If it was only three ticks, it would probably be better to just let it fall off and cast another SF or Wrath). Filter the log file for "all=Eclipse and all=Starfire". It looks like his per-Eclipse Starfire counts were (unless I messed up) "7 4 6 6 8 7", and he sometimes managed to land a Starfire within three seconds of proccing Eclipse. I would call that very good Eclipse management, although he might want to try and figure out where that "4" came from. For time spent doing something useful: 240s fight (add 12s for Heroism, and subtract 27.5s for 55 NG's). At zero haste (other than bloodlust) he would have had time for 149.7 GC's. He actually did 150 gc's worth of offensive casting, meaning his haste effectively canceled his latency. I haven't looked at his gear, but I don't think that is a bad tradeoff. |
Quote:
1. For clarification you should change the above Starfalls to Starfire (not trying to be a jerk, but it honestly might confuse someone) 2. The 4 starfire eclipse is a good point, it was a slow reaction by me (I got two wrath casts off AFTER eclipse proc'd) then after I think 2 SFs my moonfire fell off, it was rather early in the eclipse so I decided to refresh MF and get the last 2 SFs in during it. The slow reaction and refreshing MF appear to be the issue, I still feel that refreshing MF in the middle of a Eclipse is the right way [never at the end of an eclipse] but I don't know if anyone out there is 100% sure it is the proper way to handle it. |
Finally another non-laggy Mal'Ganis evening:
Patchwerk : Hamlet I played it pretty cleanly, just flubbing a few Wrath casts (I still do that here and there due to NG clipping). Any comments would be welcome. One thing to note is that I'm not Moonfiring quite as much as some other people--I've been meaning to get a more detailed discussion going at some point about exactly when DoTs are best refreshed during the Eclipse cycle. |
1 Attachment(s)
Haven't made it to a guild Patch run in 3 weeks (various reasons), so I don't have a parse to share, but I figured I'd drop the Sheet I wrote up here since it'll be relevant.
|
The main things I've used WWS for is to check DoT uptime, and to see why I died and such.
Here is my most recent WWS report with Patchwerk. WWS Loading... I plugged the numbers into Adoriele spreadsheet. I think my dot uptime is decent 80% for IS and 84% on Moonfire. My percent casting though seems pretty low at 86%. I am putting up FF so it is a little higher then what it says on the spreadsheet, but even if I add 3 or 4 casts to the spreadsheet I'm still less then 90%. What do you guys think. |
Quote:
|
Here is my 2 pennies : Wow Web Stats
If we kill him next time quicker i might do a bit better, plus i messed one eclipse proc to wraths instead of starfires. We had elemental shaman, i didn't have power infusion since our disc priest wasn't there and i had focus magic on me. A question, how can you see the time up on dots from wws report? And in general activity on a boss? |
Quote:
|
Quote:
In WWS to see just a single boss fight, go to "Split" and then select the boss. If you only want to see the damage on a single boss (rather than a single boss fight), I don't know how to do that in general. However you can filter a "Browse" screen with something like "... and target=Patchwork". |
I just put my last Patch WWS into Adoriele's spreadsheet and got values as follows:
Percent casting: 52% (is it me, or this seems low?) IS uptime: 59% MF uptime: 87% I start to think that this 52% might have something to do with me not being able to go over 5k. What worries me tho I don't know why it's like this. |
Quote:
e: whoops, read the question wrong, although you still look at your IS uptime. |
Quote:
|
| All times are GMT -4. The time now is 8:39 PM. |
Forum Infrastructure by vBulletin 3.6.12 ©2000-2007, Jelsoft Enterprises Ltd.