Spell Batching Vs Seal of Command - Bugged Interaction

[Abnoba-kromcrush]

Old videos claiming to be seal twisting without any numerical data or logged data will net you no where fyi.

[Archeon-arugal]

This still hasn’t been addressed 5 months later… is anyone actually working on bugs anymore?

[Nullite-grobbulus]

Probably not.

[Archeon-arugal]

unfortunately seems like thats the case… i mean look at my t2.5 shoulders haha they look like someone left them out in the sun for a few decades… such a blatant graphical bug; which would have been in the dev DB since launch and they still havent been fixed

[Runrunrun-sulfuras]

Of course not lol. just look through this forum and see the # of blue replies. Its probably less than 5 for all of wow classic in this shadowy unimportant section of the forum.

[Archeon-arugal]

this was not included in the original post, fairly clear in what it states…

[Patch 1.11.2]
(11-Jul-2006): Fixed a bug where sometimes casting a spell immediately after a swing would prevent Seal of Command from triggering.

The evidence is insurmountable at this point… I wish there was still a classic team fixing confirmed and identified bugs.

[Kul-earthfury]

Currently Seal of Command is bugged, in a manner where the calculation of whether the spell will actually trigger or not (The PPM Calculation) is being delayed until the next Spell Batch which follows the initiating White Swing, this scripting interaction is incorrect; the calculation of whether the spell should trigger or not should happen instantaneously as the initiating White Swing occurs.

[Patch 1.11.2]
(11-Jul-2006):</strong>  Fixed a bug where sometimes casting a spell immediately after a swing would prevent Seal of Command from triggering.

You are not describing what that fix is. That fix was back in the day they messed up the process so if you cast judgement instantly after attempting to proc SoC it just refused to proc it. I remember when they fixed it.

Seal twisting wasn’t due to coding, it was environmental. Besides even if something is wrong with SoC you aren’t describing it because that bug fix says a spell after an attempted proc, not having the batch delay the proc until the next swing. That wouldn’t be a spell interaction that would be an auto attack interaction.

[Archeon-arugal]

@Kul-earthfury

You are not describing what that fix is. That fix was back in the day they messed up the process so if you cast judgement instantly after attempting to proc SoC it just refused to proc it. I remember when they fixed it.

Did you actually even read anything in this thread at all before posting?

This is part of literally the first post in this topic explaining one of the issues which are still present with seal of command… in effect proving that the bug fix which was documented and implemented in vanilla has not been implemented in classic.

@Archeon-arugal

this means if you change Seal, cast Judgement, or are dispelled prior to the spell batch parsing then your character will never perform Seal of Command no matter what, an interaction which does not reflect the original game or the recorded documentation we have of it.

@Kul-earthfury

Seal twisting wasn’t due to coding, it was environmental. Besides even if something is wrong with SoC you aren’t describing it because that bug fix says a spell after an attempted proc, not having the batch delay the proc until the next swing. That wouldn’t be a spell interaction that would be an auto attack interaction.

Based on what evidence? Anything other then your opinion? This is quite funny considering throughout this thread there have been countless points of actual documented evidence which directly and irrefutably prove you wrong please actually research and become informed on a topic before voicing an uninformed opinion on it.

If you had gone through this thread and actually read anything at all you would have fairly quickly found the evidence irrefutably proves that seal twisting was a direct and undisputable function of spell batching.

The bug has been described in extreme detail, the problem is that you spent zero seconds actually reading any of the information surrounding the bug and then posted an un informed opinion.

You have literally no understanding of what you are talking about or what this thread is about, or any of the current bugs with the mechanic which presently exist in the game… understandable considering your character is level 30 priest; I would assume this post is a fairly blatant attempt to troll and derail given the lack of understanding or substance.

[Kul-earthfury]

Or you know I know how system design and procedure works.

You haven’t actually given any credible information either.

Not my fault you can’t generate enough mental power to understand the implication of what is actually happening within the new client and why things work the way they do.

Just keep posting your “evidence” I’m not concerned, as it will never be fixed because it isn’t broken.

I would assume this post is a fairly blatant attempt to troll and derail given the lack of understanding or substance.

That’s because you live in delusion or would you like to take a trip down memory line on the dozens and dozens of paladin “bugs” that were not bugged and were never fixed.