But there is an action causing an effect... That's what the check is checking for?
I won't debate what proc means with you. I'm aware that I'm probably wrong. I will tell you what I would approve of though, because I'm certainly not wrong about that.
A proc set should be anything that requires a check... Basically anything worded similarly to "If _____, then _____."
The only things that should be allowed in a non-proc environment are constant unconditional bonuses.
Whatever the "technical truth" may be, I do believe what I described to be the intent of the change. If anything I think things like Pariah are the very most egregious procs because their values are so conditional dynamic and slidey it just procs rechecks reprocs rechecks and reprocs constantly.
I'm sorry you went through a lot of work to acquire a set that doesn't work... But you aren't the first. There's no rhyme, reason, or list to their decision and that is a source of frustration for many of us.
By the very nature of both sets, being that neither set gives you their bonuses until a specific condition is met, both sets are in fact procs.
The only thing that would make them not procs is if, at all times, you received their bonuses. Which, is clearly not how they function. The act of needing to meet a condition makes them a proc. Pariah working seems like an oversight. The amount of time spent farming the set is immaterial.
The_Titan_Tim wrote: »By the very nature of both sets, being that neither set gives you their bonuses until a specific condition is met, both sets are in fact procs.
The only thing that would make them not procs is if, at all times, you received their bonuses. Which, is clearly not how they function. The act of needing to meet a condition makes them a proc. Pariah working seems like an oversight. The amount of time spent farming the set is immaterial.
Semantics. Pariah has been working since its creation. We are just now getting sets similar to it, so to say that the Coral Riptide shouldn’t work, let alone Pariah, you’re including Ancient Dragonguard and other sets like that? Because it switches from Damage to Resistance? That set works too in no proc too, and scales based on missing stats.
The_Titan_Tim wrote: »By the very nature of both sets, being that neither set gives you their bonuses until a specific condition is met, both sets are in fact procs.
The only thing that would make them not procs is if, at all times, you received their bonuses. Which, is clearly not how they function. The act of needing to meet a condition makes them a proc. Pariah working seems like an oversight. The amount of time spent farming the set is immaterial.
Semantics. Pariah has been working since its creation. We are just now getting sets similar to it, so to say that the Coral Riptide shouldn’t work, let alone Pariah, you’re including Ancient Dragonguard and other sets like that? Because it switches from Damage to Resistance? That set works too in no proc too, and scales based on missing stats.
Pariah did *not* work during the no-proc rule set testing pre-Blackwood. Only 19 sets worked fully, and that was not one of them.
Dagoth_Rac wrote: »The_Titan_Tim wrote: »By the very nature of both sets, being that neither set gives you their bonuses until a specific condition is met, both sets are in fact procs.
The only thing that would make them not procs is if, at all times, you received their bonuses. Which, is clearly not how they function. The act of needing to meet a condition makes them a proc. Pariah working seems like an oversight. The amount of time spent farming the set is immaterial.
Semantics. Pariah has been working since its creation. We are just now getting sets similar to it, so to say that the Coral Riptide shouldn’t work, let alone Pariah, you’re including Ancient Dragonguard and other sets like that? Because it switches from Damage to Resistance? That set works too in no proc too, and scales based on missing stats.
Pariah did *not* work during the no-proc rule set testing pre-Blackwood. Only 19 sets worked fully, and that was not one of them.
Anything and everything that had a condition or calculation involved was disabled originally. ZOS seem to have made some backend adjustments to push through certain sets on a case-by-case basis. Pariah seems to be one of them. A few of the buff sets, like Medusa and Mighty Chudan, were even disabled at first because while they seemingly give a flat bonus, named buffs cannot stack. So the game was continuously calculating whether you already had Minor Force or Major Resolve to make sure they were not stacking. They eventually changed that on the backend.
Maybe Coral Riptide should be one of the sets that gets looked at for a manual exception and be included in no-proc campaigns. But it is definitely a proc set by ZOS standards.
Lol come on man not the google definition.
I looked it up too but decided it wasn't a relevant definition since ESO kinda went away from percentage based luck procs and went instead for cooldown managed guaranteed-on-action procs.
By THAT definition the only proc sets are like... Valkyn Skoria and Bloodspawn.
And I don't agree with that at all, but there you have your answer. If I had my way Seducer would work. -shrugs-
As has been said before... I agree that Pariah and Coral are the same. And I agree that they should be treated the same. Since Pariah is allowed I can absolutely see why you find it inconsistent and foolish that Coral isn't.
But since I would prefer a truly no proc Ravenwatch I would rather see Pariah go than Coral come. It Coral gets added then you're happy with the set you farmed but the non-existent list of things that do or do not work continues to need testing because there's no real sense behind it. If Pariah, and other currently working proc sets get removed, then we can at least understand what proc means and no longer waste time farming sets for a place where they won't work.