How do you enable in your combat log the timings of when other people finish casts?
Just play around with the settings.
also also, arcane barrage is actually a relatively slow moving spell
Name : Arcane Barrage (id=44425) [Spell Family (3)]
Class : Arcane Mage
Velocity : 24 yards/sec
1 Like
You still just get a sequence of things that hit you. Execute for example has a longer swing timer than mortal strike. You still just see that execute hit you, you don’t see the order of when it pressed in sequence to when you pressed something. If two warriors are dueling each other and their global timers are perfectly in sync, one casts execute 250ms before the other casts mortal strike, it’s still just going to look like x cast mortal strike, y cast execute in that sequence. It doesn’t actually tell which one cast the ability first.
What about starsurge and sunfire?
starsurge is 45yd/s and I don’t believe sunfire/moonfire have a travel time. However, in that post you linked the sunfire was likely just a ticking dot, and what they were referring to as bypassing turtle was the goldrin’s fang proc, which has a travel speed of 20 yds/s. It triggers off starsurge, and you can just barely see the starsurge icon as dealing damage before turtle. Not sure if goldrinn’s fang triggers when starsurge is cast or when it does damage, but regardless, the starsurge landed before turtle was pressed so it doesn’t matter there.
How are you determining that starsurge was cast before turtle there?
because its icon is literally above turtle, meaning it was not only cast before turtle, but it also landed before turtle.
This one
You can’t. You can only make the assumption based on the ability landing and not being deflected, that it was cast before turtle was pressed. With a travel time of 45 yards/second, the druid had to be more than 27 yards out for it to land in >.6 seconds, which is in the realm of possibility.
1 Like
Hunter waited until the lethal spell was mid-air before turtling and then died to it.
Many such cases, etc.
Exactly. You can’t. You have to assume that an invisible game mechanic works properly with abilities that are provably bugged in other scenarios.
That’s why I asked for a combat log link. For the scenario with your melee attacks, melee attacks (except for execute) generally do not have a travel time and the damage is dealt the moment the ability is pressed regardless of animation. Execute for some reason has some kind of windup time before dealing its damage. Don’t know why but I only started noticing it in shadowlands.
Yeah, just chopped a spriest through dispers for 100k a few days ago. 
2 Likes
That’s my weekend project. I’m going to see about getting an addon or something and test this pretty rigorously with (hopefully) a better tool. I will 100% post findings and either be right or wrong. I do not mind doing a science and proving myself wrong.
And is this in metadata anywhere? Because this has been my theory with turtle from the beginning. Like other “instants” with built in delays, swing timers, etc.
Last time it just resulted in pivoting the discussion in a direction in which you weren’t, though.
No, It proved that I tested blade flurry incorrectly and not the fail condition that I thought I was testing. I was even like super transparent and quick to admit that I was wrong.
best you’re going to get is what I already linked, being the simc spell data dump. Execute doesn’t have anything in its spelldata to shed light on its delay.
I could’ve just linked the github again but I wanted to link my post because it made me feel special
1 Like
So, we know that instants with delays exist. We know that the delay is not described or listed in the spell’s metadata for any of them. But we DEFINITELY know that turtle or tranq doesn’t have one.
Do you mean instants with travel time? Because no, turtle doesn’t have a travel time.
Delay of effect. You know how like you can observe that execute takes longer than other instant melee abilities, but it’s not listed in the metadata anywhere. When turtle became turtle from deter, it got a significantly longer spell animation, and this grey-area window started happening a lot more. Theory being that there is a nonzero period of time (like with execute) between when you press the button and when the spell actually does it’s effect.