Which basically means 18-20 sec from HoL cast alone since you’d probably had one cast in the last 2 seconds.
Also this just hammers in the point that the extension was pointless because it would reset to 8 anyway…
It would only matter at the end and soo what’s the point of a 4sec extension over 20sec vs 4 over 8, it’s not impactful.
It was already balanced, for 1 cast.
It went through the beta and the first 2 weeks as it was.
That’s not a coincidence that it happened to make sense at this value for 1 cast, that was the intent.
If Sacrosanct is useless than so is SoV, it’s the same mitigation amount of mitigation (15%+ x2 over a minute vs 30% every minute + vers scaling).
Fact is, 15%+ is not useless and you know it, it’s passive mitigation attached to a damage button/defensive CD, you don’t need to do anything to profit from it.
It has less use for Ret but will always be fully used as Prot paladin.
That goes back to the first point, for the majority of Shake the Heaven effect you wouldn’t have been casting other spenders so what’s the point of it?
What’s the point of having it start at HoL usage instead at the end of the 12 second window if this is what they wanted/intended?
It doesn’t make sense, especially when it does make sense when it’s meant to just be 1 cast.
That’s why it’s in " ".
Point is, you’re not supposed to have 12% haste buff have above 50% uptime.
The tuning was already DONE on this, which it why it makes sense, AT 1 CAST.
All the talents didn’t need tuning, as you suggest, they were ALREADY TUNED FOR 1 FREAKING CAST.
Except, again, it doesn’t make sense that it would because then the window could overlap with Wake CD, which is freaking stupid design wise.
When it’s available ONCE in the next 12sec and when Wake is on CD for 1 FREE cast, it doesn’t have this problem.
All those weird issue disappears, poufff, almost as if it was intented for it to be 1 cast…
So strange…
If your answer to all those self-evident issues that broke the tree is to conclude that its all those talents that are “poorly tuned” instead of recognizing that it was just the first node that was bugged than you’re not correcting misinformation, you’re spreading it.
If something weird happens that makes it so that all the talents needs to be retuned, the problem ain’t those talents, it’s the bug.
You’re not gonna remake an entire city street grid because someone chose to make a car twice as wide as the normal ones to accommodate it.
You’re gonna fix the stupid car.
Well fine then, but don’t go saying that it didn’t break the tree as it was.
It did.
If you have to remake the whole thing to make multiple cast a thing, then it was breaking the initial one.