FFXIV Mythbusters #7! How Interrupts ACTUALLY work, TBN Barrier Priority, LB Cancelling and More!

[@Kpsla]

I've had a player in my FC complain regularly about how TBN wouldn't proc when someone plays SGE. I try to tell him that this isn't the case and that problem is actually that the SGE is giving him a near constant mitigation with Kerachole/Taurochole, and that he is simply taking less damage and not that the SGE shield is deleting or prioritizing over his.

[@CaetsuChaijiCh]

Yeah that sounds like a reasonable cause. I am a bit surprised that 10% Dr would be enough to cause issues, but Indeed as you said, it is absolutely not the sage barrier! 😊

[@PipPanoma]

​@@CaetsuChaijiChIt is 10% on top of the usual mitigations, so it has stacked multiplicatively.

[@IKMcGwee]

Good to know! I like maining sage and I get worried that my shields are messing with their TBN. I feel better now knowing that their TBN won't be wasted of I help em.

[@MiMi-xc7ks]

I noticed this in a dungeon run as SCH. I tend to put down sacred soil and adlo for tank busters but I had one instance where the DRK’s TBN didn’t break consistently so I stopped doing it for the rest of the run. But another DRK’s TBN broke when I did the same thing, same dungeon, different run. I think it’s a good case of why tanks and healers should try understanding each others kits and plying around mit.

[@EPICZEUS.]

From what I can tell, mobs that are interrupted _still have to finish their cast time_ even if interrupted, and that's where the hidden 'stun' effect comes in. Whereas with a stun effect, they don't have to finish the cast time.

[@CaetsuChaijiCh]

Indeed! It does make sense, but seems so unintuitive without seeing it happen!

[@BlackMarluxia]

Wouldn't that mean that the ideal play would be to use a stun as late as possible into the cast to make use of both the mob not doing anything while casting and then also not doing anything due to being stunned?

[@CaetsuChaijiCh]

@BlackMarluxia yes, stun as late as possible, interrupt as early as possible 😊 and since stuns could be used at any Time but interrupts only work at certain times, interrupt should of course take priority!

[@SampoPaalanen]

@@CaetsuChaijiCh Well the way I'd consider it that if you interrupt a mob, they're there standing wondering why their spell failed for the rest of the cast time, but with a stun they known the spell failed and thus hit you straight after it.

[@sayori3448]

one thing you seem to have gotten wrong about TBN but is very obscure/niche knowledge. it seems after level 84, reaper's Arcane Crest has a higher priority over TBN, but before 84 TBN has higher priority than arcane crest. AFAIK its the only shield with higher priority than TBN.

[@CaetsuChaijiCh]

Oh wow, that is an incredibly specific detail! I hadn't even considered arcane crest since that would require the dark knight to put the shield specifically on a reaper! That is very interesting! I can see WHY the priority changes, since that's when arcane crest gets it's healing over time payoff. And it makes sense that it takes priority since it is the reapers own shield, the reaper (probably) would want their own shield to pop first! 😅 Thank you for the correction!

[@Dw7freak]

I think the reason is because Arcane Crest can only be applied to the RPR that cast it while TBN is given from the tank. As Arcane Crest is small and TBN is smaller on dps, it's not as big a deal, as a normal EX/Savage raid buster would break them anyway. The only time I can think of that not happening is if the RPR pulled a mob during a dungeon and the DRK put TBN on them instead of just hitting/Provoking the mob(s).

[@BlueQmas]

I already knew the Interrupt thing but this weekend taught it to a main tank friend. Fun seeing it in mythbusters. Easy to notice the difference in a place like EO. Lethargy really makes you see how they stand there with the "interrupted" cast doing nothing.

[@CaetsuChaijiCh]

I could imagine so! The lethargic slow really really emphasizes it! 😁

[@MightyMoonWorm24]

Great finds here, I didn't know about TBN taking priority over other barriers OR the interrupt interactions. This is a great series, thanks for your hard work!

[@CaetsuChaijiCh]

I'm glad to hear when people learning something new! Thank you! 😄

[@Rellow2]

I think the reason interrupt works the way it does compared to stun is that interrupt basically cancels the actual effect from the cast, but keeps the enemy stuck in a casting state until it would've normally ended. Stunning by comparison ironically actually interrupts the cast allowing them to be actionable as soon as it's over since they're back to neutral.

[@CaetsuChaijiCh]

That is a pretty funny twist yeah when you put it like that! 😁

[@AaronWGaming]

Petting the lalafell will get you approval of the Lala...

[@CaetsuChaijiCh]

As long as it is consensual head pats! Otherwise it can sometimes bring bad luck! 😂

[@javi7636]

Great mythbusting! So my takeaway for enemy cast bars is that you want to Interrupt early and Stun late. You interrupt asap for the reasons you explained, but stunning late will let you actually delay auto attacks for the duration of the stun--ideally having the stun last past when the original cast would have finished.

[@CaetsuChaijiCh]

Thank you! And precisely! Naturally, if you are faced with an interruptible action, interrupting it would always be superior, since you can always stun the mob once they're done staring at you! But if interrupt is on cooldown, simply stun as late as possible as you said! 😁

[@ZZValiant]

IIRC, TBN did not have priority when it was first added, but they changed it relatively early on. So I can see where that myth came from lol Neat video!

[@CaetsuChaijiCh]

Yeah I could imagine! There's also the part that a lot of players simply assume that intuitively, barriers are spent in the order they are applied, without ever checking! 😊 Thank you!

[@TheCrazyhusky]

The reason why interrupts make enemy stand there longer the sooner you interupt it, is because it locks the enemy for the rest cast time then the interupt timer starts. Meaning the interupted enemy won't start another action until the full cast timer is done despite they wont do it. Unlike Stunning which resets actions. So the later you interupt the enemy the less cast time left before it can attack again. As Caetsu said it is better to interupt an enemy ASAP.

[@CaetsuChaijiCh]

Precisely! 😄

[@NomoregoodnamesD8]

while interrupts prevent auto attacks until the cast bar would end, it does not root enemies. Perhaps the claim came about because interrupting an enemy causes them to immediately start pathing into melee range of their target.

[@CaetsuChaijiCh]

Oh that could be! I didn't consider that! I'm guessing if an enemy is interrupted the mob just walks up to you and glare at you until it feels like attacking? 😅 That could certainly cause the claim to come about too!

[@purplefreedom1631]

One of the best mobs to see the "glare at you MENACINGLY" after interrupting is DR savage ghost boss.

[@Xbob42]

I think the interrupt thing was changed so that people didn't feel they had to hold their interrupt until the very last second (like in WoW, where the longer you let something cast before interrupt, the longer they spend doing nothing) -- this way people are encouraged to use their interrupts and not risk wipes (in the few challenging encounters that use interrupts) by holding on to them and letting latency ruin the day. You can see how this works by the length of time "INTERRUPTED!" is displayed on-screen. The cast bar doesn't disappear until the cast would have completed naturally. There is a minimum amount of time this is displayed, so if you interrupted it at the very last millisecond, it'll still show for a moment, but if you cast it at the beginning of a super long cast, the cast bar WILL stay on-screen until when the cast would've roughly finished. You can even observe this in your video! Stun, on the other hand, immediately removes this cast bar, letting you know that the stun is the only thing keeping the enemy in check. This is partly why I keep my enemy cast bars (including focus cast bars) very large and where I can see them. I believe at least some of this was mentioned in the patch notes for when they gave interruptable casts that pulsing graphic, but it's been a while, so I could be wrong.

[@blahpy]

I can’t remember what it was, but there was an enemy somewhere with a super long interruptable cast that would just stand there and do nothing for like 30 seconds if you interrupted it early. I think it’s designed specifically so that auto attacking resumes again after the same amount of time from the beginning of the case no matter when the interrupt happens, but I haven’t verified this

[@CaetsuChaijiCh]

Indeed, this was also my observation, and if there is such a specific example, that pretty much proves it! 😁

[@purplefreedom1631]

DR savage ghost boss

[@blahpy]

Yeah that's a really good example@@purplefreedom1631

[@pedroscoponi4905]

It's pretty natural to want to stun late if a mob is visibly not auto-attacking while it casts something (The big griffin in Lapis Manalis comes to mind), so I had no idea Interrupt works the other way around. That is very strange! 😅

[@CaetsuChaijiCh]

Indeed! It just makes sense to interrupt late, so it would be unintuitive to assume the alternative is better! I can't imagine many would have taken my word for it with no proof! 😂

[@steakbaby_]

I knew the LB3 thing had to be false!! But I see why people thought it was true, and why the timing on it was so tight now

[@CaetsuChaijiCh]

Yeah looking into it, it made perfect sense you couldn't skip the animation lock, because of how weird it would be if you could! 😅

[@Elvie_Takodachi]

great video again! Didn't know interrupts were handled that way since I come from Lord of the Rings Online where it makes a difference if you early or late interrupt. But for that I would have loved to see a split screen with both casts starting at the same time to see the difference. Just to visualize it better then just a timer on screen. Keep up the great work!

[@CaetsuChaijiCh]

Thank you! Yeah I get what you mean. I considered that as well, but since I got both in the same clip, I felt the timer made it feel more... Hmmm... "real"? In a way? 😅 That I literally could demonstrate it there in one shot!

[@lizardizzle]

If you stun a big pack of enemies (like with holy), do their auto attacks all sync up leading to massive damage on a single tick instead of easier to manage tickles over time?

[@CaetsuChaijiCh]

A good question! The answer is yes! 😊 However in a pack of a variety of mobs, they all tend to have different swing timers, and other things can cause them to drift again (such as them having to shuffle into range of you again) so for the most part it is fine. But Indeed, this also means that if the white mage stun locks the pack for a clean 7 seconds, they all smack you once it ends. And if the whm instead spreads their stuns into a 4, then a 2, then a 1, to get "max stun value", it means you might get the full smack down three separate times! 😅

[@Scerttle]

8:40 I get the feeling that interrupts work by cancelling the cast but not changing the mob action, where as stun stops everything and so resets the mob after the stun is over. They're standing around during the cast duration because it was always going to stand around for that duration regardless. That's just a guess, though.

[@CaetsuChaijiCh]

It seems to be working like that yes! 😊

[@silverhairedelf09]

As the guy who actually sent the LB3 cancelling question a few mythbusting videos back, well, I WAS LIED TO BY MY FRIEND AAAAAAAAAAA (no harm done) I would still do this on specific situations like after Bonds 3 healer LB since the next mechanic after needs a lot of movement and the healer that just LB3'd might be in an awkward spot. Good to know!

[@CaetsuChaijiCh]

Oh yeah, you can still use rescue to save someone if lb has to be done, just remember that the person is completely at your mercy to put them at the right spot! 😁😂

[@coaster1235]

It was a common courtesy for me to rescue the cohealer if they lb3’d after bonds 3, and likewise them for me, to get moving in time for wings 2, and I swear it enabled movement just fine there and made it much comfier

[@fluffyfang4213]

​@@coaster1235 This seems incredibly odd to me. Having usually been the one to LB3 after Bonds 3, I always found I had plenty of time to get back to the center before seeing who got the wing tethers. Keep in mind that the animation lock time starts as soon as the cast bar finishes. It takes 3-4 seconds for the revived people to start acting and Rescue takes ~2 seconds... so if they're rescuing about the time that everyone starts moving, you'd be able to move around the time the Rescue finishes anyway, giving it the illusion of breaking you out of the lock.

[@coaster1235]

@@fluffyfang4213 probably it was the power of placebo then!

[@HyugaUeki]

You can think about the interrupt as mobs trying to still cast their skill but they are silenced, thats why is better interrupt sooner, they Will be "stuned" for their remaining duration of the cast (and a bit more), same as late interrupt, they Will be "stuned" for their remaining duration of the cast but you wasted like 1 second on your CD, but at the end the mob will be the stuned for the same duration Early interrupt=little cast + remaining cast bar Late interrupt=longer cast + little remaining cast bar (Sorry for my english, trying my Best :B)

[@CaetsuChaijiCh]

Yes exactly! And since interrupting sooner has no negative effect, but will give your interrupt cooldown back sooner, it is just overall beneficial!

[@ymmj13]

Which is probably why stun works like that. My guess is that stunning the mob "cancels" the cast. So the enemy hits immediately out of stun. While interrupt forces it to finish casting even if the attack will have no effect.

[@lolthesystem]

The first one USED to be true back in the day (I want to say it was changed back in Stormblood, but I don't fully remember the exact date). There's also the issue that using TBN on a DRK who already has TBN up will overwrite it and therefore end with 3000 MP wasted for the first DRK to use TBN, which can be very frustrating when you get paired with a DRK who doesn't know this.

[@CaetsuChaijiCh]

Yeah, my best advice if you have two dark knights is to never TBN the other dark knight unless you can see they don't actually have mp to do it themselves! 😂 It happens too often that you mess each other up as a result!

[@TheKabukimann]

The difference between a stun and an interrupt is easily explainable with the animation lock. An interrupt just stops the cast while not stopping the animation lock. A stun puts the target into a different animation lock. That's why they start swinging immediately after the stun ends.

[@CaetsuChaijiCh]

That also works as an explanation yes! 😁

[@Xbob42]

Ha! And I was so sure of the LB thing, too! Thanks for clearing it up with cold, hard and unrelenting FACTS!

[@CaetsuChaijiCh]

Yeah I was also surprised myself when it didn't work! 😂

[@iambecomegameend2972]

I thought it was better to interrupt late since that’s what I saw other people do. Nice to know i can interrupt early and not risk letting the attack go off

[@CaetsuChaijiCh]

Indeed! Personally I thought so too for ages because of the logical reasoning I described in the video! ("if enemies act logically, they'd attack immediately!") 😁

[@tarultoyarto]

I don't have any proof, but it feels like: Stuns stop an enemy completely, causing them to resume their script as soon as the stun wears off. Whereas interrupts cause a skill to fail without interfering with the enemy's scripting. Meaning the enemy is "stunned" for the cast time and end lag of the interrupted skill, and then pick back up again for their next scripted skill. Stuns cause them to "recalculate" their actions and start attacking again as soon as the stun wears off.

[@shadowofchaos725]

I'm guessing for the stun the server has the logic to tell the mob to restart its auto attack cycle for its script when afflicted with stun. While interrupt is something else entirely. Who knows if implementing it in Shadowbringers has something to do with it and how it's handled.

[@CaetsuChaijiCh]

According to some people, interrupts work exactly the same way as they did before shadowbringers (back when it was a one second silence, plus no flashing cast bar), it's just the presentation that changed. I can't speak to whether it changed or not because it's too long ago and it could easily be that people remember wrong! 😅

[@titaniumvulpes]

I believe Reaper's Arcane Crest has a similar priority effect as TBN because of its HoT secondary effect, I've never seen mine not pop. Though since TBN can be placed on other players, now I'm curious which takes priority between the two....

[@CaetsuChaijiCh]

Others have mentioned that arcane crest takes priority over TBN, which makes sense since arcane crest is only usable on yourself, and the reaper itself would probably like their own barrier to break first 😅😊

[@Jaridavin]

It took 7 episodes for one thing I didn't actually understand to show up (interject) unless we count weird SMN opening thingy. I dunno if that's good or bad. But I guess that's why I was still here to see. Still not letting the shark hunt speak tho.

[@CaetsuChaijiCh]

Just in case! The interject thing basically is that it appears the mob "continues to cast" for the full duration of the spell whether you interrupt it early or late, so interrupting early simply means you get it on cooldown quicker, at no loss! 😁 I don't know if it is good or bad, but yeah, there are some weird interactions in the game! 😊

[@Jaridavin]

@@CaetsuChaijiChI meant good or bad that it took 7 episodes to find something I was incorrect on. I know I originally once apon a time believed the LB rescue thing too (I never thought it'd skip lockout like some people, but did think for a while it let you move until someone did it to me). Still these are helpful. If anything, to point at when topics come up.

[@bobseesall]

Tbn taking shield priority and the Vengeance/Arms length section in #6 seems to indicate a priority system on buffs. It doesnt seem to matter too much, but it is interesting to see if other abilities have this property.

[@CaetsuChaijiCh]

Very true! I wonder which other buffs might care about order in such a way! 😊🤔

[@bobseesall]

@@CaetsuChaijiCh Arcane Crest on reaper is one I would assume.

[@CaetsuChaijiCh]

Indeed, someone else mentioned that arcane crest actually has higher priority than TBN, but that also makes logical sense, since the reaper probably prefers if their barrier they applied breaks before the outside one from the dark knight! 😊

[@asdsad17]

ready your rescue for the chrysalis LB. lol.

[@CaetsuChaijiCh]

Ready to cancel the one that is aimed at the actual boss! 😂

[@Cloud7050]

Potential myth idea: Whether tank stance increases any of the enmity generated from provoke

[@CaetsuChaijiCh]

I actually fiddled around with provoke in episode 1! 😊 Heres a link, although specifically the detail about tank stance isn't stated directly: kzbin.info/www/bejne/aKPFpYSadtqeq8Usi=DKkSeDKmLbeEWp29 Tank stance multiplies all enmity generation by ten, including provoke. I also went and tested this just now with a friend to be sure 😁

[@Cloud7050]

​@@CaetsuChaijiCh Thanks, very good to know! Pretty sure I watched the whole series but I must've forgotten. So for a more effective provoke, I should turn stance back on first...

[@CaetsuChaijiCh]

@Cloud7050 Indeed! And also no worries. I had to look through my video notes to find which one it was I talked about it too, it's been a while! 😁

[@praus]

My guess about interrupt, is that their auto attack goes on a sort of GCD. This would make sense why they start attacking again at around the same time, no matter when you interrupt. The GCD started when they started to cast the spell and the interrupt “finishes” the spell with respect to the GCD. Stun doesn’t let the spell actually “finish” with respect to their GCD, so they just start to attack as soon as the stun ends. Do players act the same? When we’re stunned in the middle of a cast, does it keep our GCD from happening? What if we’re interrupted?

[@CaetsuChaijiCh]

Interesting hypothesis! It does make sense! For players, to my knowledge, your auto attack timer continues through stuns, so you auto attack immediately after the stun ends if the enemy is in range. There are no known ways for a player to get interrupted. And if players had interrupts in PvP (We don't), it is worth pointing out that auto attacks don't exist at all in PvP! ^^

[@praus]

@@CaetsuChaijiCh ahh, I didn’t know that about PvP. Never done it in this game. I suppose it makes sense. Would be pretty annoying to get interrupted on top of stun.

[@zantar04]

The interrupt late in the cast come from Warcraft I feel like. As mobs in Warcraft will instantly start casting a spell again after the interrupt goes off.

[@CaetsuChaijiCh]

Absolutely correctly. I imagine if other games have similar mechanics, logically mobs would start attacking again immediately, so the intuitive process is to interrupt late. It is funny, because it means that it is better to interrupt early because of such a ffxiv unique interaction! In wow spells that need interrupting also have a tendency to be a lot more catastrophic if you don't! 😅

[@aedif9566]

Hmm, regarding LB3 animation cancelling. I thought it was a similar situation to where you can gap close out of resurrection movement lock. In LB3 animation cancel case you'd need to get rescued, and then also gap close immediately after. Probably just copium though 😅.

[@Cloud7050]

9:00 I wonder if WHM doing a 3rd holy stun (1s) may result in enemies doing more autoattack damage? Am I understanding it right that stun "resets" the swing timer for enemy autoattacks, making them do it immediately? Or does that only apply when stunning an interruptible castbar?

[@CaetsuChaijiCh]

It is simply that the stun prevents the mob from performing their auto attack even if the swing is ready 😊 A white mage spreading out their stuns can make enemy attacks feel more bursty as a result, and may sometimes make the stun do nothing (if the mob wasn't going to attack in that one second anyway for example) but it won't make enemies do more damage 😊

[@Cloud7050]

​@@CaetsuChaijiCh After running more tests, I think I finally understand the last 2 myths. Interruptible castbars seem to pause autoattack swing timers for their full duration, even if the castbar does get interrupted. So interrupting early isn't going to make the swing timer resume sooner, and so there's no need to wait. Meanwhile, stunning causes the swing timer to resume immediately, so you don't get the benefit of interrupt pausing the swing timer. This is definitely gonna change the way I interrupt. What I'm not sure about is whether the enemy will just afk for the rest of the duration of the interrupted castbar. Or if they can actually move around or use other attacks while the swing timer is paused.

[@CaetsuChaijiCh]

@@Cloud7050Based on what others have said, the mob should still chase you around while they have been interrupted! Another person also said that there is a specific mob in Eureka Orthos who regularly uses a mini tankbuster, and it appears that mob continues to use that mini tankbuster while it has been interrupted, so there are some rare cases where it might not be beneficial to interrupt early. On the other hand, with a long enough cast time, interrupting early could enable you to consistently interrupt the dangerous attack every time, so maybe it is worth the trade off?

[@GrimmyReaper69]

the interupt thing is dependant on the mob/boss some stop attacking all together for a set while.

[@CaetsuChaijiCh]

it's usually related to how long the cast was itself, but it certainly doesn't work *better* to interrupt later. I can say that for certain because I've been intentionally interrupting super early on a lot of things and only seen things stand and wait after being interrupted 😊 But yes, the key is when you interrupt, the mob ends up standing there for the remainder of the cast time 😊

[@ProtoTototo]

​@@CaetsuChaijiCh isn't it the same then? Since the mob either stands casting or waits while it would have been casting

[@CaetsuChaijiCh]

@ProtoTototo in terms of total time the mob spends doing nothing, yes it's the same. But if you interrupt the cast one second sooner, then your interrupt is ready again one second sooner. And the enemy will use their interruptible action after the same amount of wait just the same, so interrupting earlier = more interrupts in total! 😁 But if it is all about one interrupt and only one, then yeah it makes no significant difference!

[@ProtoTototo]

​@@CaetsuChaijiChah yea that's true, I was thinking of mimics in EO or similar where their pox cooldown matches interject, so you can always interrupt it again regardless of when in the cast you use it. But I suppose if we're thinking of dungeons or any other multiple mob scenarios that extra second or two could gain you some in total!

[@GrimmyReaper69]

​@@CaetsuChaijiCh good to know, I haven't payed much attention to those much, not sure if the boss in ktisis works differently as he seems to cast something straight after being interupted(could be the timer tho), i'm just glad when people interupt instead of ignoring it.

[@Rondart]

Hi Caetsu, I have a weird experience that you might be interested in. I was soloing The A Rank (Zanig’oh) in Southern Thanalan as a Warrior at level 50. Now Zanig’oh casts a cleansable paralysis debuff. I died and returned with Spine Drops, which is a Paralysis-cleansing potion. To my surprise, it *didn’t* cleanse the Paralysis. You could say I didn’t read the fine print where it does say “most instances of paralysis”, but that particular debuff had the marker where it *can* be cleansed using Esuna (or its Bard equivalent). So my question is, do some cleansable debuffs only work with Esuna and not potions? Because this is largely not true since you can cleanse Deep Dungeon Silence just fine with Echo Drops (and is in fact recommended to bring as the person with cleanses). Requesting intrepid and curious adventurers to investigate! Thank you in advance.

[@CaetsuChaijiCh]

Yes, it turns out that a LOT of paralysis debuffs specifically ignore Spine Drops for no good reason. I don't think this problem exists for echo drops, although uncleansable silence seems to be a lot more rare as well! I don't think there is any indicator or any system in what is and isn't cleansable so unfortunately, I can't give you any super helpful advice on it, other than, you'll have to try spine drops on each individual effect to be sure Thank you for sharing!

[@Rondart]

@@CaetsuChaijiChAs I once said after this ordeal: “This is the last time I’m buying potions from Honest Hohone’s Discounted Wares!”

[@Zoltri]

I think the interrupt/Auto interaction might just be a carry over assumption from people who played WoW, because that is 100% true for that game, its always better to interrupt late to lock the unit down for as long as possible, atleast it was when i played, hard to say for modern wow.

[@CaetsuChaijiCh]

I very much agree. That's actually the case with a surprising amount of myths about ffxiv that have no source: "but it works this way in wow!" 😂

[@BurnCorpoStuff]

I swear as recent as this expansion I have had whatever shield was applied last break first for Dark Knight.

[@CaetsuChaijiCh]

I can assure you that the only shield that appears to break before TBN specifically, is arcane crest! 😊 All other barriers seem to let TBN go first. And arcane crest is very specific since it has to be TBN put on the reaper!

[@laidweiss]

Strange fact: reaper's shield is the only shield that has higher priority than TBN.

[@CaetsuChaijiCh]

It is strange yes! It makes sense since naturally the reaper would like their own shield to break first I suppose! 😅

[@notGeist]

Love the theory videos! Really works for your way of teaching. The jobs guides not so much!

[@Cloud7050]

Do enemies autoattack during their castbar? (I think players don't.) If not, would a very long interruptible cast (longer than the autoattack cooldown) delay autoattacks when interrupted late?

[@Cloud7050]

Or maybe I'm understanding it wrong. Does swing timer not count down during an interruptible castbar, regardless of when the castbar was (or wasn't) interrupted? Since you mention the difference includes the seconds between when the interrupt happened. Maybe the Iksalions in Fractal Continuum normal with their long interruptible casts would be helpful to test.

[@CaetsuChaijiCh]

Enemies don't auto attack during casts. We know that player character swing timers pause while casting so it is likely the same for enemies 😊

[@Cloud7050]

@@CaetsuChaijiCh Thanks for clarifying! I did some tests as BLM on a training dummy, and also tested the boss of T9. I indeed found that autoattack swing timers for players/enemies pause while casting.

[@CaetsuChaijiCh]

@Cloud7050 in that case a bit more clarification! Player swing timers actually start again once the slide casting window starts, which means your auto attacks resume around the last half second of each cast! This was particularly important when paladins were figuring out their new optimal rotations with the rework, as it decided whether holy spirit hard casting was worth it or not, which is why we have quite well detailed information on this subject! 😁

[@Narlaw1199]

Isn't the LB rescue about cancelling *before* the end of the cast, at around 0.5 sec?

[@CaetsuChaijiCh]

This is an interesting question, I wonder if this makes a difference. I can say for certain I have not heard about this addition before that it has to be specifically in the slide casting window (which of course absolutely exists for limit breaks too) I went and tested this with a friend just now, and given the latency precision there is a small chance that we simply failed the timing, but based on my tests, even if you rescue during the half second there, the same as you saw in the video happens. You still cannot move, although rescue still is of course able to force you somewhere! 😊

[@Narlaw1199]

@@CaetsuChaijiCh Oh, ok, thanks for the testing again and clarifying!

[@Jay-lf2bm]

Tbn breaks after arcane crest and before everything else, it's not absolute highest in priority. This only matters if you external a reaper obviously but making it sound like it's highest priority is incorrect.

[@CaetsuChaijiCh]

That is fair. I had missed this particular interaction due to how specific it is 😅

[@medivh1035]

Interesting. I thought shield is consumed based on the order they are applied

[@CaetsuChaijiCh]

It is the intuitive assumption, but it also makes perfect sense a few shields take priority simply because they care more about being broken! 😅

[@Kyginbo]

Your video and script has conflicting info. So does adlo's crit shield get eaten 1st or 2nd? Sch main so i want to know

[@CaetsuChaijiCh]

Adlo crit shield is eaten first! This makes sense specifically because it means it protects your regular shield so you can deploy it! 😁

[@sarajohnsson4979]

"First" as in "first if adlo is the only shield because the crit part gets hit before the regular shield", "second" as in "second if the target is also TBN'd, as TBN gets hit even sooner but the regular adlo shield gets hit later still (third)". No contradiction

[@KINGOFTHESPARKS755]

First 📸

[@CaetsuChaijiCh]

Dun Dunn! 😂

[@Lolihazard]

Actually, point 4 heavily depends on a simple thing... a cast time. Yes, this is nitpicking, but in EurekaOrthos, under a lethargy pomander, a dread beast will channel for 20 to 30 seconds without aa'ing you at all, while swinging at ~7s intervals if you interrupt it early. Yes yes, this is an extreme example, but devil is in details :P

[@CaetsuChaijiCh]

That is weirdly specific! I've heard others say they've found interruptible casts that are ridiculously long, and if interrupted early, the mob just... Stands there. I wonder what would make this particular one behave differently 😊

[@Lolihazard]

@@CaetsuChaijiChthat most likely depends on the monster as well.. I mean in EO it is likely that mobs would just stand looking at you, but instead use their "tankbuster" which is instantcast and not actual aa :hmm: Interesting moment.

[@CaetsuChaijiCh]

@Lolihazard yeah, the fact it swings every 7 seconds makes it sound like it has some separate trigger set up that happens while casting too (but simply fails if it is busy), but this sounds like almost more like a bug or an exception!