One problem with a LOT of the analyses I see here:
82% SnD uptime. SnD uptime by itself is 100% meaningless. You have to compare SnD uptime to target uptime. His combat trance uptime is 86.1% and his deadly poison uptime is 86.7%. This puts his SnD uptime over 90%. It's still low, but not as low as people are suggesting. If you stand /afk for half a fight, your SnD uptime will be only 50%. This may be bad, but keep in mind, these buff uptimes are based on in-combat time, so if you are slower to hit the boss, then, well, your SnD uptime is gonna take a hit. Comparing SnD uptime to combat trance or deadly poison uptime is more meaningful than just looking at SnD uptime.
The logger went out of phase during one fury the destroyer proc, but here's something telling that shows something is wrong:
Code:
[23:39:53.348] Kaleel gains Fury of the Destroyer from Kaleel
[23:39:53.593] Kaleel casts Sinister Strike on Ultraxion
[23:39:53.720] Kaleel Sinister Strike Ultraxion 10406
[23:39:54.102] Kaleel afflicted by Fading Light from Ultraxion
[23:39:57.459] Kaleel casts Eviscerate on Ultraxion
[23:39:57.796] Kaleel Eviscerate Ultraxion *73294*
[23:39:58.593] Kaleel afflicted by Heroic Will from Kaleel
[23:39:59.355] Kaleel's Fury of the Destroyer fades from Kaleel
Your rogue cast sinister strike during a fury of the destroyer proc. Judging by the times though he very well could have hit the sinister strike button before the proc (latency and all, he only hit it 200ms after the proc), but his only eviscerate during the proc happened 4 seconds later. This suggest to me either poor reaction to procs, poor energy management, or both. Bad timing for Fading Light though.
The revealing strike thing that people have pointed out is pretty bad though.
Originally Posted by
Pikapika
Couples pieces of wrong information here. Saving KS for deep insight hasn't been worth doing since t11, current consensus is to get to 5 points before you use it to ensure you're as far into BG as you can go without eviscerating again and wasting cooldown reduction. Agi/hit always in blues, not just if you actually need hit rating, that's what reforging is for.
You don't necessarily always put agi/hit in blue sockets. If the EP value between gemming for and ignoring the socket bonus is close but in favor of socket bonus with blue-quality gems, then using epic gems you ignore the socket bonus. As an example, say you're in T11 BiS and you want to gem the T11 legs with epic gems, using T11 BiS EP values, gemming straight agi in T11 legs is 216EP, gemming for socket bonus is 220EP, if you use blue-quality gems. If you use epic gems, gemming straight agi is 270EP but gemming for socket bonus is 261.5EP, so if you use epic gems you ignore the socket bonus.
If you gem for socket bonus in the valor belt, you're actually LOSING 5 agility compared to gemming straight agility, thing is the 25 hit you gain in return generally more than makes up for it. In the case of blue-quality gems it's the same agi either/way so even if ALL of the hit were white hit and not spell hit, it'd still be worth gemming for. (as it stands, gemming for socket bonus in that belt for white hit is still worth it even at epic gem levels because white hit has more than 1/5 the EP value of agi).
For that reason the OP needs to ignore the socket bonus in his ring (and this is ignoring the fact that overall his gemming is generally pretty bad). In fact, the blue socket in belt, yellow socket in legs, and yellow socket in tier shoulders are the only places where the gem should not be straight agi.