I am a programmer, i’ve programmed in Python 2&3, Cyton, C++ and C# the languages and emulations that make up for WoW’s engine. Therefore i have a firm grasp of the technical limitations of the langague even though i obviously don’t have access to the code.
When i just finished my ICT education, World of Warcraft came out, and i was a hooked player, so when the classic was announced i was ofcourse struck by nostalgia but also intrested as a programmer of how they would recreate it. I’ve both been in awe and in dismay of the developer choices and programming loopholes they made that give us classic.
However i’m also a purist that wants to keep classic as close to vanilla as possible. With the removal of spellbatching you can still sealtwist, as can you still get the double polymorps, however the server / client handling speed is so fast in present era that that will hardly ever occur.
Artificially programming the seal duration so they can overlap, will allow for a gameplay that was never in vanilla, and purely depended on your connection speed if twisting would work for you.
The change also doesn’t bring a rotation or more intresting gameplay. All you have to do is have your swingtimer in your macro and its still the same one button.
All your doing is opening the door for “community driven” changes that have nothing to do with the original game, and are tailored for entitled people that want to show off “daddies” “I’m special” medallion.
I’ve been up against that in other topics, but this one is specificly to adress seal twisting, and the special changes there making to it.
FYI at 70 seal twisting will be even more rediculous since you can then SoB + SoV twist, till 5 stacks and then go SoB + SoC, SoB + SoV rotation as well as probably double judge SoB + SoV for even more out of context TBC damage.