As of Patch 1.3.0:
> - Seal of Command - The damage effects can now be **resisted** instead of **dodged**, **blocked**, or **parried**.
Link: `https://wowwiki.fandom.com/wiki/Patch_1.3.0`
This has been going on for too long.
Also (a bit offtopic though), it feels quite fishy that you guys "couldn't get anything more recent than 1.12", yet a seal is working like the times in which we still had *Seal of Fury* instead of *Righteous Fury*.
Upper part of the thread is wrong, I’m leaving this up for a bit for ppl to see it before I ask for it to be deleted.
As the blue tracker linked here: http://blue.cardplace.com/cache/wow-realm-test/391.htm SoC was tested to be changed into a pure spell category but considering that it would lose 50% crit damage, the change never passed up to live even if the patch notes still list it. My bad, I tried to find out all before opening the thread and just found the patch notes without the explanation which was more hidden that I imagined.
Now I flagged it for being deleted, hopefully that doesn’t come with a ban for me with it.
If you can backup it with said videos then we can talk. Anyway in 1.12 the change was already stable, we already had Greater Blesisng from the patch before and the spell damage scaling on judgements.
Then at this point it becomes a matter of them wanting to fix it (like they wanted to “fix” Reckoning), which I’m not really hopeful for considering their past actions.
This is a flawed way of looking at patch notes. Here’s another example.
Patch 2.2.0 (2007-09-25) Earthbind Totem no longer breaks stealth.
What does this mean? Did Earthbind BREAK stealth in Vanilla? No, but at some point during BC before 2.2.0 it did and it was then removed/fixed in 2.2.0.
And how is that the same as the Seal of Command case?
We are playing in a “time” after the change I am discussing so we are supposed to have that (EDIT: or either have a Blizzard comment about SoC being parried/dodged/blocked being as it’s supposed to be even if patch notes said otherwise). If we were in TBC then your argument would be valid.
it means that just because something was true for one patch it isn’t necessarily true for patches before or after, even when there’s no patch suggesting otherwise.
You are mistaken, it means it will be resisted instead of the following ones. The “can” means that it has a chance to be resisted instead of a chance to be dodged, etc.
What they said is that maybe the change didn’t came into being at thatexact moment because some changes were made functional not exactly at the patch release. You seem pretty pristine and arorgant in trolling basic english and logic.
I am telling you that the word CAN means just that, it can be resisted. It never say will, or can only, or anything like that. And on top of this you have actual video evidence that prove that this is what it means and how it worked.
These hotfix and tooltip wording are sometimes not easy to understand. Maybe you are right? Who knows. But we do know 100% sure how it actually worked in Vanilla retail.
Anyway, a patch note from 1.3 is irrelevant. Classic is based on 1.12.1. A lot happened to paladins between those patches. We know for a fact that patchnotes did not have all info in early Vanilla, not all updates was posted either and that data is not saved. The 1.3 data is forever lost.
Did some more digging and I am mistaken indeed but not because of what you said (I will add the further part to the main thread to make it visible while it lasts).
As the blue tracker linked here: http://blue.cardplace.com/cache/wow-realm-test/391.htm SoC was tested to be changed into a pure spell category but considering that it would lose 50% crit damage, the change never passed up to live even if the patch notes still list it. My bad, I tried to find out all before opening it and just found the patch notes without the explanation which was more hidden that I imagined.