Currently Seal of Command is Bugged, how it seems to work at the moment is you swing, and then the server doesn’t calculate whether or not the attack will trigger Seal of Command until the next server batch,
How it should work is you swing, the server calculates whether or not the swing will trigger Seal of Command or not instantly as the white swing occurs, and then the 0.5 second delay occurs/server batch for the following Seal of Command proc / yellow swing to happen.
In Classic this bug can cause a number of broken interactions for paladins, where Seal of Command can be interrupted by stuns/fears/ccs if the cc hits the paladin as they white swing, and the following Seal of Command hit which should occur will never end up hitting the target… this is on top of interrupts due to cc which can occur during the 0.5 second delay between calculating if the seal will proc and the swing actually occurring, definitely broken.
There are multiple points of evidence and reference for this, firstly everyone knows how Seal Twisting worked in the TBC with the current version of bugged Seal of Command, this mechanic wont work, how it worked was as the white hit landed you would swap seals and the new seal would be applied to both the white hit and seal of command.
Secondly we have actual video footage where you can see paladins seal twisting, swapping the seal before seal of command procs, and seal of command still going off. So we know for a fact this is how the seal should work, however if you repeat this process on classic, it doesnt function like that… if you swap seals in classic after the white swing but before Seal of Command procs, Seal of Command will not proc.
Please fix this spell, currently it is definitely bugged, theres video evidence of it and its implication in classic are that paladins are potentially being robbed of seal of command attacks every time they are cced as a swing goes off… Just look at videos of the actual gameplay…