theckhd wrote:Footer:
- Code: Select all
enemy_initial_health_percentage=20
(this just keeps us in execute range the entire time, so we get a larger variation between results and thus more accuracy)
I remember bringing something like that up a while ago. It's nice to see that there's an easy way to do that now. :)
theckhd wrote:Holy Prism has an absolutely abysmal DPET for a L90 talent. It's worse than Holy Wrath and Avenger's Shield, on par with HoW. I'm not sure what caused it to get such a large nerf in WoD, but whatever it was, it made this talent fairly weak. The new Resolve mechanics mean that it's raid healing side-effect is basically useless. It's still useful as a self-heal and AoE snap aggro, presumably, though we're not testing either of those here. We're just testing single-target damage and splash self-healing, and it's pretty pitiful. And it has very little effect on TMI. So, to the back of the priority list it goes.
Any chance to include both versions of HPrism somehow, to see the differences in use, as if they were different talents? Considering HPrism's primary use is snap aggro, people may have it macro'd to cast on self. They're basically 2 different things depending on use. I guess the same could be said for ES as well.
theckhd wrote:Ultimately, I decided that the "safe" rotation here was CS>J>HW>AS>HoW>LH>Cons. It was min TMI, and second-best DPS. We'll keep "HW>all" in the back of our head for when we're developing a max-DPS queue for the tiny gain it'll give us, but especially for less advanced tanks I think the CS-J cycle is worth maintaining.
It might be interesting to see how CS>J>AS+GC>HW>AS>HoW>LH>Cons holds up to that rotation.
theckhd wrote:Again, we see that the single-seal configuration (insight) wins the day for TMI. Of the three-seal queues, (CS-HW)>IRTd>(AS-IRTe) ekes out a DPS victory at a cost of a few thousand TMI. IRTd>Base>IRTe is a close second though, and does slightly better in TMI. The (CS-SS)>IRT(u/d)>(Cons-IRTe) queues are the lowest-TMI of the three-seal options, but with a DPS loss.
That... is interesting. If they make the talent so that keeping multiple buffs up is not the most efficient use, it stops being the horrible aberration that most people claim it to be. If it's like "Ok, I'm going to taunt the boss in 3 seconds, so let me switch to my TMI seal." and "My co-tank took the boss now, so let me switch to my DPS seal." then it's not the GCD consuming horror that people make it out to be. Whether that's intended or an unexpected result is open for discussion.
However, I checked the Sample Sequence Table, scrolled down until after Bloodlust was gone, and noticed that the rotation mostly cast 1 judgment per seal, which is wholly inefficient. By only casting 1 judgment per seal, you keep the buffs at 20 seconds, rather than upping them to 26 seconds by double judging. I did some napkin math in the general WoD thread:
Thels wrote:Rotation: SoR > JoR > SoT > JoT > SoI > JoI > repeat.
This requires us to cycle the rotation every 20 seconds on average. If one cycle takes us 25 seconds for various reasons, we only have 21 seconds for the next cycle.
Per 12 Judgments, we spend 12 GCDs on Seals.
At low haste values (I honestly have no idea of our haste values at, say, HC Dungeon gear level), we can't get more than 1 Judgment off per Seal. Once we start to get into higher haste levels, perhaps we can try squeezing in a 2nd Judgment. Let's check a couple of rotations...
Rotation: SoR > JoR > JoR > SoT > JoT > SoI > JoI > SoR > JoR > SoT > JoT > JoT > SoI > JoI > SoR > JoR > SoT > JoT > SoI > JoI > JoI > repeat.
A 2nd Judgment every 4th seal would push the timer up to 26 seconds for that Judgment. We then have to wait 3 Judgments to refresh it, wait another 4 Judgments to refresh it again, and finally wait another 4 Judgments to refresh it twice back to 26 seconds.
Covering the first part with 3 Judgments shouldn't be an issue (we need to do that anyhow in the basic rotation), so we should reliably push 6 seconds over towards the other 2 gaps, which means we practically have 23 seconds for each gap of 4 Judgments. A 4 Judgment gap takes 18 GCDs.
23 seconds gives us 15.33 GCDs at 0% haste. We need 18% haste (from all sources) as the bare minimum for this rotation.
Per 12 Judgments, we spend 9 GCDs on Seals. Compared to the 1 Judgment per Seal rotation, this frees up 1 GCD every 4 Judgments (or 18 GCDs).
Rotation: SoR > JoR > JoR > SoT > JoT > SoI > JoI > JoI > SoR > JoR > SoT > JoT > JoT > SoI > JoI > repeat.
Naturally, a 2nd Judgment every 3 Seals wouldn't work out, as we'd keep extending the same Judgment. But what about a 2nd Judgment every 2 Seals? After pushing it up to 26 seconds, we have to wait 4 Judgments to refresh it, then wait another 4 Judgments to refresh it again. This actually has the same requirements as above, but requires a lot less GCDs for changing seals. Again, we'd need 18% haste (from all sources) as the bare minimum for this rotation.
Per 12 Judgments, we spend 8 GCDs on Seals. Compared to the 1 Judgment per Seal rotation, this frees up 1 GCD every 3 Judgments (or 13-14 GCDs). Compared to the 2 Judgments every 4 Seals, this frees up 1 GCD every 12 Judgments (or 54 GCDs).
Rotation: SoR > JoR > JoR > SoT > JoT > JoT > SoI > JoI > JoI > repeat.
Naturally, we have to check if 2 Judgments every Seal can be a thing. For that, we have 26 seconds to cover a gap of 5 Judgments. However, instead of bumping this Seal to our disadvantage, we could pick when to pop our seal, and if we use it at X1 or X2, it means it'll only be 22 GCDs away until the next Judgment, rather than 23 GCDs.
CS-J-X1-CS-X2-J-CS-X3-X4-
23 seconds gives us 15.33 GCDs at 0% haste. We need 44% haste (from all sources) as the bare minimum for this rotation.
Per 12 Judgments, we spend 6 GCDs on Seals. Compared to the 1 Judgment per Seal rotation, this frees up 1 GCD every 2 Judgments (or 9 GCDs). Compared to the 2 Judgments every 2 Seals, this frees up 1 GCD every 6 Judgments (or 27 GCDs).
18% is not a whole lot, if you consider that the talent itself gives us 10% already. Does the raid buff Haste apply to us? Then we only need to cover 3%. Otherwise, we'll have to cover 8%. Doesn't sound like too much of a stretch, if we focus on it. Macroing SoR>J>SoT>J>SoI>J will cause you to lose a GCD every 13-14 GCDs, which might be rather punishing.
44% is quite a lot, especially if you also want to build a bit of an error margin. It would require very close to 50% haste, and you have to make sure that you do everything correctly. As I described above, you NEED to refresh the Seal in X1 or X2. X3 or X4 would require exactly 50% haste to pull off, with zero delay in the rotation.
I'll see if I can run some more tests to optimize that myself and see if it makes any difference, though I'm not sure if the current builds are representative, and I don't have anything to compile with myself.
