Back to home
Showing posts with label Blogsourcing. Show all posts
Showing posts with label Blogsourcing. Show all posts

Saturday, May 2, 2009

Blogsourcing: How can I gain 118 times SD with 93 crits?

Synopsis
We switched from WWS to World of Logs. If looks much nicer. Was just looking at our 10 man Hodir wight where I was MT and noticed something weird about SD.


Here is the link:
Worls of Logs

If you look at the tab Buff Gained you will see that I have 118 times gained SD. If you look at damage done I did 93 crits.
Now 2 things can be here. 1 the data is not 100% correct. Though I find that strange. So how is it possible?

Also I can't find how often it is removed and total damage absorbed. Anyone less blind then me or is it not in there?

[edit]
Thanks to Yrkoonia; it is the lacerate ticks which in the statistics show no crits, just an average. 25 crits in 63 ticks seems about right.
[/edit]

Wednesday, April 8, 2009

Rotation study (Blogsourcing)

Synopsis
Since I had so much trouble with the 12 second mangle rotation I tried some more and this is what I found.


I started out dpssing, again on a lvl 80 dummy, and not berserking ever. Berserk will screw up whatever you are able to call a "rotation".

This is the DPS is did over a LONG time (calculated form white damage hits it is 45 minutes).


At the start I was at 3450, that then got to 3650. It went a bit down after some screwups in rotation, but it is a good average. 3.1 PTR servers are in America. Meaning that I did suffer a bit from latency. Renewing Rip and Rake had to be calculated. Do it at 0.5 seconds left, not too soon or the last tick won't get through, not too late or there is a too long period without Rake/Rip.

Below I will tell you what rules I tried to dps by which resulted in this. I ask you the same, if you are possible and willing. Tell me what you found on ptr (not using Mangle glyph). Don't Berserk and upload a screenshot (or post it on you own blog) and link it in as a comment. Judging from white hit damage there is a good comparison to what your total dps to mine would be. If yours is higher i'll try to find out why.

The rules I tried to live by:
Ability strategy:
  • SR always up. If it is down and have no CP get 1 CP SR up at least. Then depending on Rip uptime do a 4/5 CP SR.
  • Mangle over Rake. Rake does nice damage but Rip does a lot more. Mangle increases that with 30%. Mangle doesn't always have to drop before renewing.
  • FB is overrated. It doesn't always crit. Rather keep the 5 CP to keep up SR and Rip then to let one of those drp.
  • SR > Rip > Mangle > Rake
Energy strategy:
  • WAIT! If SR, Rip, Mangle and Rake are up you have all the time of the world. Stock up on energy. Don't let it get too high because OoC procs a lot now. You should spend as little time as possible at 100 energy. (I'd like to be rogue and have 110 or 120 energy to have more time.)
  • Don't get to 5 CP asap. Wait to see what happens. If Mangle and Rake need a refresh soon, stop at 2/3/4 CP, get engery refresh en and then wait for SR or Rip to drop to renew it.
CP Strategy:
  • Try to go for 3CP SR. It is about the same time Rip takes. That is a way to go for a normalisation in Rotation. It will not always hold up and you are seldom able to do it, but it if the choise it is available do that. You will have max time to be ready to renew Rip (where a 2CP SR could have the SR needing refreshing before Rip. Als a 3CP SR gives you that little extra time to build a new 3CP SR after you have renewed Rip.
  • The 3 ways to spend CP are SR, Rip and FB. FB should be avoided as much as possible. Saving up on energy and Mangle + Rake to get to 5CP might leave you with a lot of energy (having OoC).
  • When to FB? Only when you have plenty of time left on Rip and SR. I find that to be about 12-14 seconds. It will not ensure having SR and Rip up 100% of the time, but the alternatives are worse. (As you see in 45 minutes I only did FB 33 times vs the 4 per 3 minutes I did before, not counting the extra FB I did after a Berserk).
  • When not to FB: 1: Less then 12-14 seconds on SR only. Wait till the last moment (is having 100 energy) and refresh SR. If Mangle and Rake both drop, do it earlier. so Mangle and Rake are not of or at least not a long time. It is worth it to wait for 70 energy to be able to SR + Mangle + Rake immediately as a combo.
  • When not to FB: 2: Less then 12-14 seconds on Rip only. The same as above. Try to avoid this situation. With high time left on Rip (10 sec) you should get the last of the 5 CP's from Mangle and Rake so you dont have them down or are forced to do an early Rip to refresh Mangle + Rake
  • When not to FB: 3: Less then 12-14 seconds left on both, Rip to expire before SR. Wait till rip is expired and refresh. 1CP SR (or more if possible) right after.
  • When not to FB: 4: Less then 12-14 seconds left on both, SR Expires before Rip. Depends on how long the difference is. If the difference is up 3 seconds you can refresh Rip just before SR drops. (Then 1CPSR after). If the difference is higher, refresh SR immediately (overwriting 10 seconds or so) and use the remaining seconds to get 5CP Rip asap.
This is kinda it. Would love to hear your input and see your tests.
PS, this is not a strategy I did when testing on live (3.0.8) servers. So applying this strategy on live servers can not be compared to my previously posted live dps test.

Thursday, April 2, 2009

Maim my ass off... (Blogsourcing)

Synopsis
With not much melee around there is a good chance you will be maiming in Ulduar.


Last night I was in PTR in Ulduar, testing General Vezax. There was no thrash this time, but compared to last time we only had 1 rogue. The people that could interrupt were that rogue, 1 DK, me and an other druid in catform. I never was in a raid as feral, so I don't even know if Maim could interrupt spellcasts on bosses before 3.0.

Anyway it sucks! For kick a rogue only needs 25 energy. For maim we need to have Combopoints and it costs us 35 energy. A major DPS nerf. When it is your time to interrupt you want to be able to do that immediately. And you have to be ready!. That meant that it sometimes took 20 seconds of waiting time. 20 seconds of keeping GCD ready, 20 seconds of seeing your energy being full, 20 seconds in which you see Rip, SR, Mangle and Rake all drop off from your target... So fair to say my DPS was not optimal. That plus there was a dps nerf about 700 dps for cats on that boss. Well I think it would be about 700 dps even if I didn't interupt.
Also TellMeWhen still isn't fixed and instead of only showing my debuffs it shows debuffs casted by others too, though mine has priority, meaning it will show my rip with 2 seconds left before the other druid's rip with 16 seconds left. But after my Rip is gone it will show the other druid's Rip.

My dps could have been higher but the bossfight itself is totally unreliable too. We were playing from Europe and the server is in the US. That meant we had a .325 latency. Meaning I see the spellcast when it is already going and the boss knows I maimed him somewhat later too. So I had to keep GCD ready.

But it is my thought the boss is bugged. Because of a special shirt GM's provided us for this fight we were all hitcapped and my maim did always hit. The split second I saw the spell being cast I maimed but often the boss kept on casting his spell anyway. He also has the tendency to, after having a cast go through, cast 2 more after that, without others being ready for that. So that was a definite wipe every time.

Now the blogsourcing part of the post; I have a question for you on why maim doesn't always work.
Also I checked combat log and I wonder how that works too. My combat log showed me casting maim and doing x damage. 2 lines below that I saw the General Vezax his spell hit me. The thing I want to know on how that works is: Is the combat log local or server side? For instance, chat is server side. When you type a message and there is a lag you will not see the message. The message has to be processed by the server first and then will be given back to you (and whomever it may concern) and only then the message can be read. Does the combat log work the same? If you maim does the server have to process it and then you will see the maim in your combat log or will the combat log show it the second you cast it, not considering whether the server has received the maim?

PS in this case it could have been that the cast was ready before I maimed and that during those 2 lines I mentioned earlier the spell was traveling from him towards me. Still the change for that is really small, because since I was in melee range the spell (aoe) would have to hit me immediately.

Monday, March 23, 2009

Blogsourcing: Malygos DPS

Synopsis
I am asking you to take a look at my malygos tries and tell me what I did wrong or if druid dps at the moment really sucks.


So we did Malygos 6 minute tries tonight. Now you must know as soon as we knew it was fail we stopped, well at least didn't do the last phase. Last try we were able to get him to 50% before he went in the air the 2nd time. We failed in phase 3 though. I got 2 beams and a cloud I didn't notice soon enough and I died way too early. 6:30 was the time we used.

A couple of things. I was the only feral druid (meaning I had to mangle). I tanked in phase 2... and I am melee. The dps buff things were not placed optimal a lot of times for melee. You can see rogues struggling too. And we can't dps when he is in the air. Well not optimal anyway.

So I am gonna leave this to people who can compare to their own experiences. I am a lonely druid in my guild. One joined us recently but wasn't on this fight. How did I do? Outsourcing on my blog.. blogsourcing. I hope you people can help me.

Some other information. I was in full cat spec and full cat gear. Only switched my main hand when I was tanking in phase 2.

Numbers say more then gear. So Rawr tells me that my unbuffed damage with my current gear should be doing 2963 dps. If you want to check my gear you might be able to see my gear on my armory profile (see left for link) but I am often in tank spec and in tanking gear.

WWS Link

Would love to hear you tell me where I suck! ;)