It seems apparent that you havent really looked at any of the threads posts or topics surrounding this issue…
Fortunately how this game is was or will be scripted isnt based in any way on what you consider as a change to the game, but rather how the game actually functioned… something which I am definitely happy about. All of which can and will be verified against the original client now that seals are finally being redressed and fixed.
Its good to have an opinion but as the saying goes everyone’s got one, just try to do some research before you post yours, information is important… opinions arent.
Im not going to post massive chunks of the first post which relate to the initiating swing the point of incident of ppm calculation for SoC, the point of calculation on-hit damage applicators such as sob and sor, the implication related to White Hit => SoR => SoC => SoR or at the least White hit => SoR => SoC (broken down against buff existance and uptime in the original videos), either you havent read it, dont understand it or are intentionally ignoring it either way you are all opinions and no evidence, ill leave the discussion here regardless.
I look forward to Blizzard finally redressing Seals based on the actual scripting and function, something which paladins have been long awaiting and looking forward to in classic wow. And while this workaround may not be a 1-1 recreation; it is definitely a step in the right direction and will in effect facilitate seal twisting and its interaction for the rest of classic and moving into TBC in essence (although it should have been here already since day 1 of classic). From the initial dev talk of classic it seems that the documentation and backups of the TBC back-end server were far more consistent and frequent, then its Vanilla counterpart so will provide a great framework to provide an accurate game in the future, and will offer some effective balance between horde and alliance should alliance not receive Seal of Blood with SoC-SoC twisting; in-spite of Horde Paladins still being far stronger with SoC-SoB and associated mana gain, and arcane torrent haha .
Cheers Blizzard Devs, Nice work, we have been looking forward to this Paladin Bug Fix for a loooong time haha.
The current batching also has subtle differences compared to the old one.
The order of events this time isn’t nearly as consistent, for example, sapphiron used to always apply the aura in a way that the reapplication clipped the DoT. The current batching was a toss up of which simultaneous event occurred, so the ptr saw a large damage increase until they reworked the ability like they did in WotLK.
This current spell batching priority seems more randomized than the old one, so now not only would you be trying to time things to the correct batch, you then need to hope that the game prioritized your move in the order you wanted.
The consistency likely won’t be anywhere near what people are expecting.
No, I just illustrated with my example that the only way to consistently ground anything is to do it more than 400 ms before the end of the cast. If you do it in that 400 ms window you are rolling dice that the next batching window will resolve before the cast completes and not after.
Excuse me? Shadow Word Death breaks work RIGHT NOW on retail without 400ms batching.
Can this please go live already? It’s been over a month since it was announced, Naxx progression is firmly over with multiple DMF weeks for speedclears.
It would help keep interest in the game until pre-patch. I don’t want to raid or PVP another day without it.
Can we get this patch already? REALLY tired of waiting on it. And now with TBC launch officially coming and a pre-patch for it, a lot of people would like batchless Classic for a bit before pre-patch.
Is there any update on this? It’s been over a month, is this even going to come before the pre-patch? Is the removal of the 400ms batching ever going to be a thing on Classic servers?
We could really use a little communication here if possible.
.