The SoC double procs are just a consequence of the testing I did a few weeks ago, coupled with this change.

SoC procs on both the application/refresh of Censure from SoT as well as the damage component of SoC, as they are both interactions of the seal with a target.

Here's a list of the procs this change should produce:

SoC:

White: +0
CS: +1
J: +2
Exo: +2
HoW: +2
TV: +1
HW: +0
Cons: +0

SoT Damage:

White: +0
CS: +0
J: +1
Exo: +1
HoW: +1
TV: +0
HW: +0
Cons: +0

SoT apply/refresh Censure:

White: +0
CS: +1
J: +1
Exo: +1
HoW: +1
TV: +1
HW: +0
Cons: +0

From this, additional SoC procs can be seen in the summation of additional SoT damage proc with applications of Censure.

Some people suggest the HoW nerf may be unintended and that it may be dealing physical damage, not holy, and that could be the reason behind the stealth nerf. My account is currently bugged on the PTR, so I cannot test it.

As for the buffs: They all seem very coherent and will solve many issues, however I'm still concerned with our almost non-existant AoE and I feel we should have another HP source, like judgement, only generates HP if used on targets with x5 Censure up, or something like that. And PvP-wise we still lack mobility.

Yes, I meant HoW.

SoC clearly states "each time you swing", thus removing at least the "cast" attacks from eligibility makes sense. Reducing it to just autoattack is also legitimate. Lazy coding and piggybacking it off of seal applications or procs (rather than a combined "did an autoattack land, is the source using a seal, and does the source have the talent" trigger) likely lead to unintended SoC proc behaviour.

I remain leery of any situation that causes unusual/unexpected procs. Anything not clearly detailed (such as in the talent tooltip) always has the chance to be unintended on Blizzard's part. Based solely on my own end user experience, it appears that Blizzard will balance classes for overall DPS based on internal trials and PTR trials. This balance often appears to suffer from "can't see the trees for the forest" - they focus on bottom line overall DPS, not sources of the damage or how every change took effect. Too many times for my satisfaction has something rolled live only to later be identified as a bug, hotfixed out, impacting (if not downright crippling) total DPS. Suddenly the class (not always Ret) is notably under performing compared to all others. Months pass before review/correction occurs (heaven forbid they hotfix more damage to a class).

My comment regarding PvP is that often a mechanic like this is ignored by Blizzard until other players repeatedly bring it to their attention. Other players interaction is mostly in the PvP world being hurt by the mechanic. If Blizzard is both truly clueless about the event and didn't intend it, they "bow to QQ" by fixing what they see is a glitch. However, said glitch fixing also invalidates all previous PvE modeling they'd performed and approved for balance.

Under the hood, the only other mechanics which should change would be items where Censure stack/proc was a valid source to proc the other mechanic. Greater Censure procs, greater procs from other mechanic.

Good point on rolling Censure on flight/movement phases.

Judging a not-sealed target to gain and roll a stack is most likely an overall loss. Recall that the first 4 Judgement would be underpowered, as Censure would not yet be at a 5stack and you would not have the full 150% bonus. To get the most mileage you would likely need to target swap, build 5stack on new target (rapidly) while (if necessary) Judging previous target to retain 5stack. Once both have 5stack, then you could swap back to original target and judge-refresh the old.

This would only be of benefit where both targets needed to die (which is the majority of such situations). In a situation where the other targets are simply offtanked or fullheal (Atramedes trash, for example) the extra seal would just be cheesing meters and not gaining productive additional damage (the time/abilities used to build the stack would have killed the primary target at least marginally faster).

There are numerous possibilities for HoW, from always available and Ret talent (not yet implemented) improves in some fashion (under wings, under 20%, whatever), straight out nerf to reduce its desirability in the priority, to accidental change. Until Blizzard states some given direction (either explicitly via a post/patch note, or a talent/ability difference shows a tooltip change) it's hard to discuss. We don't know the intent/goal (if there even is one), so we can't know how close it is to being reached.

Personally inclined to either accidental change or intentional change to make it de-prioritized above 20% and then go-to at that stage (to "shake up" gameplay when that threshold is reached). They can only buff TV and CS so far before PvP explosion on hit occurs, it may be necessary to lower other items damage to have them de-prioritized.

I believe it's supposed to scale, but it currently isn't due to the way they decided to implement it. I'm just a little suspicious due to the fact that not a single blue post was made about this, or specifically about our new mechanics at all.