they were trolling me about Seal Twisting as well being an “exploit or abuse” while championing Totem Twisting as legit and intended lol
watch the video - it’s queued up right when Kevin Jordan is asked my question about Totem Twisting by Countdown to Classic:
I know, I’m just saying; totem twisting + seal twisting are one thing, and exploiting server latency with /sit to get unintended procs is something else entirely.
it all flows back to my original point - if /sit RECK, Seal/Totem Twisting were considered to be abuse or an exploit - they would have either been fixed during Vanilla itself or CMs or Devs would have made everyone WELL AWARE that it was not to be used
that’s all I’m saying
A) History does not agree with you. Blizzard regularly leaves unintended interactions in place for long periods of time.
B) They DID fix reckoning charges off sit, when they changed sitting crits to not proc crit-based abilities. Their fix just had an exploitable bug and they didn’t have time to fix it before Vanilla ended.
no they CHANGED the talent completely for TBC into a flat 10% chance to proc off of any damage to make your next 4 attacks proc twice
And that has…absolutely nothing to do with anything.
We can guess at their motives, but the fact is that they made a change during Vanilla that was explicitly intended to prevent you from getting Reckoning charges while sitting.
That change had a bug in it.
They didn’t fix that bug during Vanilla.
Their intent was pretty clear though.
which flows back to the 2nd part of my point - all they had to do was to write a sticky thread in the Paladin forums titled,
“DON’T USE /SIT RECK MMMK GUYS”
Please, please play elemental in PvP. I’m alliance and your free HK get me to grand Marshall that much faster.
Name one single time, in the entire history of Blizzard, that they have EVER made a public announcement “Here is a bug, here is how to reproduce it, don’t do it”.
They might have theoretically ever considered making a vague reference to it, but the idea that they would have ever made a directly on-point announcement about it is ridiculous.
That would have done nothing but encouraged players to do that though.
It also assumes it was a priority for them in some way.
you don’t remember the Seal of Truth bug?!?!?
I don’t remember it, no, but those also appear to be completely irrelevant as they are
a) from post-Vanilla
and
b) not what I asked for
cataclysm and yea it was a pretty big deal
yeah I misread the patch number, I somehow managed to read 4.3.2 as 2.4.3
I didn’t really play during Cata, I quit shortly before Firelands came out.
TLDR - basically a dev added an extra decimal place to the DoT from Seal of Truth or something to that effect
which caused it to literally proc off of itself ad infinitum until mobs/bosses just died right then and there OR the server would crash cause of the inifinity loop
i think it took a few days for them to fix it iirc and Blizzard put out a public notice asking players not to use Seal of Truth until the fix went live
Sounds like a major bug. Seems like a very different case though, since you didn’t actually have to do anything to generate it and you might have it happen by accident, and it could crash the server.
So there was one time when they announced it, but you know what I mean; they basically never announce it. They almost never even mention that a bug even exists until after they’ve banned people for using it.
https://www.engadget.com/2009/01/04/mage-solos-naxxramas-military-quarter/
I remember that one. But I don’t see the relevance?
this happened during Vanilla as well - I remember cause my guild had just entered Naxxramas, had killed Anubrekhan, cleared the trash before Patchwerk and were about to try this strategy when the server got taken down for “emergency maintenance”
Sure. There were bugs. It happened a lot. Some of them got fixed, some of which were hotfixed, and some didn’t.
That’s not a point of debate, though and it’s not actually at all relevant to the points being debated.