Spell Batching Vs Seal of Command - Bugged Interaction

[Delimicus-heartseeker]

Kevin Jordan talking about Hunter traps having special case coding, like he thought interrupts did, so that they couldn’t be run over without without triggering. Admits he has no idea the tech involved:

https://clips.twitch.tv/BrightAntsyHorseradishPeanutButterJellyTime

Bug report thread from 2006, multiple people complaining about players/mobs running over traps and not triggering them:

https://web.archive.org/web/20060527102237/http://forums.worldofwarcraft.com/thread.aspx?fn=wow-bugs&t=53523&p=1&tmp=1#post53523

Kaivax confirming the same thing:

@Kaivax

Traps can sometimes not be triggered if a player moves over them very quickly (i.e. a Warrior’s Charge ability). This behavior is consistent with the Reference client.

QA confirmation that spell batching isn’t even the culprit for the issues with Hunter traps. Further proves that Kevin Jordan was right in admitting to not knowing the tech, because traps obviously didn’t have special case coding:

@Kaivax

Q: Spell bactching seems to be causing problems with aoe abilities such as people being able to run over hunters traps and it not going off or running through mages blizzard spell and not getting hit or slowed by it and many more aoe abilities… are there any thoughts about lowering the spell batching delay or another way to fix these issues?

A: This is actually not related to spell batching. Traps and AoE abilities check for the presence of targets during a heartbeat update. If the target moves through them between two heartbeat updates they will not notice the target. This is how it was in the original 1.12.

I think it’s time to admit that the reference client Blizzard uses isn’t a myth, and they’ve confirmed that spell batching is working correctly.

Celestalon saying interrupts were on the batch:
https://i.redd.it/za5hs503nyn11.png