No White Mage wants to fail casting Benediction due to macros, we want to successfully cast Benediction and put it on cooldown but the heal lands too late so the tank dies anyway.

Weird/interesting Features: 1: In Shadowbringers, the Gremlin enemy insults you by using Bad Mouth which inflicts the Misery debuff on you. This debuff can be removed with Esuna, but it also can be removed by a player using the /comfort emote to you. 2: In the Palace of the Dead deep dungeon, there are hidden traps, one type of which transforms you into a frog for a time. Any snake enemy can one hit KO you while you are in frog form.

Worth noting that the time between an aoe action being cast and receiving its effect can be delayed based on the number of people between you and the caster. For example, in an alliance raid, if you're at the edge of the arena you might notice a raidwide hits you quite a while after the animation went off, which is because all 23 other players need to register the hit before you take the damage. This also affects most (if not all) aoe heals, and that small time gap has killed me in savage before lol

Funny story about the buff application thing. My group found out first hand that it's proximity based when we were helping someone do the 5.3 trial for the first time. I accidently hit tank LB just a touch too early but somehow timed it so it was expired when me and my co-tank (who was right next to me) died to the insta kill while everyone else still had the buff. Healer's were pretty quick to recover though and we still cleared but it was pretty funny in the moment and I still sometimes get teased for that moment.

@ 7:40 "There really isn't a reason too...", in UCOB if your team has a good Twin kill time you can start a Gnashing combo right as Twin's killed. The transition into Nael is just shy of like 25 seconds ish. This means you can bring the rest of that Gnashing combo into your Nael pot window, AND because the cooldown for Gnashing is on the first skill by the time you complete the combo you can immediately do another under that same pot.

Snapshotting was definitely a weird concept to learn. But now it feels pretty good to confidently walk into attack animations and not take damage, except the odd times where you still take damage lol.

My favorite snapshot is when I cast arm's length, put it on cooldown, then get thrown into the death wall anyway as I see the cooldown timer tick down over my corpse

Shield application is even weirder because this also depends on a case-by-case basis. Succor and E-Prog, for example, will apply to everyone at once, but Sage's Panhaima will ripple out amongst the party and can be up to a second between the first and last person to get the shields. Futhermore, similar to the Divine Veil example, because the shields on Succor and E-Prog apply before the heal, you can end up shielding a raidwide and then healing up after with the same spell if its timed perfectly. And thats before we get to TBN's very slow application and ability to 'break' for a moment after its worn off.

#2: I'm convinced the single-pixel hitbox is partly why there seem to be so many lalafells in savage raiding. It's just easier to determine your true position. #6: The 3-second tick also affects MP regen, and (at least in the past) when certain states are checked. This was notably used in A4S when people were trying to cheese Royal Pentacles with Healer LB; by watching MP regen ticks, they could figure out when to jump through two AOE circles and soak both of them despite dying to the first one. #10: Enrages can be applied like this too. I've had hairline clears where some of the party members were dead from the enrage.

Note on the hurt boxes: this quirk goes back to 2.0 days. In 2.0, player hurt boxes used to be based on the width of the character. This meant that if you had anything hanging over the AOE marker on the x-axis plane, no matter where it was on the z-axis plane, then you would be hit by the ability. The 2 issues that caused the devs to change to a single pixel were due to latency and fairness. 1) Latency issues in the early days meant players would not see the AOE marker immediately upon its engagement. Therefore, they would react to move out of the way upon client sight, which was not in sync with the server clock. As such, players would be fully out of AOE markers when they saw the ability commence, yet still be hit with said ability. This has been resolved with optimized servers, but it was a real issue in 2013/2014. 2) Fairness: this one is almost laughable. By using character models as the basis for being hit by an AOE, a movement tax was enacted on Roegs, with Lalas getting dodge benefits. There were videos showing characters of different races standing on the same pixel when an AOE went off, only to see the wider models get hit because a Roeg foot was inside the orange when a Lala foot wasn’t. To avoid some arbitrary unknown width of a hurt box, the decision was made to make it centroid of the x-axis plane under the character. Both changes were beneficial to the player base and attractive to new players learning the game, which at the time was fairly new with AOE dodging.

15:55 The reason for applying aoe effects over time, to target/targets. Is server stability and overall game health. Many mmo's suffer from an abundance of instant gameplay related latency spikes, caused by hitting thirty targets at the exact same time with an attack thus applying on hit effects and everything that comes along with that. By staggering the applications, both the servers and your computer can take this process in steps rather than a massive text dump. The result is that rather than WAR needing to time bloodletting (waiting below half health) to get 'maximum value' you get a consistent healing over time effect, that is overall less punishing and more enjoyable.

that delay during AoE propagation is how my static once cleared p7s AFTER the enrage cast went out. her animation went off, the screen went black, we really thought we'd lost...and then we were greeted to the sight of two chests and four people dead on the floor!

A weird feature in the game is if you use the dancer ability that rushes you forward (En Avant) to go off of a ledge you immediately appear at the bottom and do not take fall damage. I use this often in PVP, if I am defending somewhere that is high up and attacked by a group I will rush away to escape safely and not take the fall damage that would often cause problems for other classes.

I always thought that trait was a direct "explicit in game text" to show the change from way back when their damage scaled with vitality. Which was inherently inferior for people that knew the game inside and out so much that people stuck to using Level 60 Heavensward non-tank accessories that were equippable to tanks that gave strength during Stormblood. The gap between the casual player and the hardcore player was super huge from what I heard back then that it caused tanking issues in dungeons because people tried building for STR just based off hearsay.

For Combo Timer, I would add Dancer to that. If you're saving up all your resources for when Technical Step is used, you can find yourself running out of your combo timer if you have one going at the time. You get so much gauge during the buff that you can do upwards of 4-5 Saber Dances during it - add in Starfall Dance, Tillana, Standard Step and the extra procs from Flourish into that and you're finding yourself with so many more powerful abilities to use then your standard 1-2 combo that it falls off.

Another weird one is how the time after pressing a skill until the enemy is hit is on a skill-by-skill basis. You can for example on DRK use an Edge of Shadow and instantly consume MP before the on-hit effect of Blood Weapon on a Bloodspiller actually takes effect. The only other case I know of this being used is that MNKs will sometimes use a delayed skill right at the start like 1-1.5s prepull and then use a macro to immediately cancel AAs because logs only start when the boss is hit. I've actually died on DRK before because i chose to use Bloodspiller at the end of my LD and the hit delay was long enough that I died before I got healed by it.

WHM, Liturgy of the bell is also weird. it checks the whm's healing bonus before every pulse. unlike the rest (asylum, physis2...) they check at the moment they're active. Like in P3S where the boss let the healers to soak the puddle to get 300% bonus healing. WHM can actually place the bell before taking the puddle and the healing bonus also apply. while other healers have to wait for the bonus then start healing after that. pretty sure it is the only healing skills that does this.

Fyi the backwards cast (#4) you can still get snapshotted if the split second you press your cast the mechanic goes off, even if your character looked away. You will get snapped as the "backwards cast" is more like ur character turns to face the boss to start its cast then turn very quickly to continue the cast. The odds are VERY slim but it can happen.

Talking about the AOE thing, I believe dancer's tech step has some kind of weirdness based on how close they are to the enemy and that affects who and how it's applied to at what point.

In last of #10, I believe the damage is applied as usual as well not as the numbers come out. Back in Shadowbringers people were low blowing or interjecting the raid boss to land the last hit before it disappears/dies to skip the delay, and they changed that when moving into 6.0 so that only the numbers but not the actual damage/healing is reflected immediately.

The funny thing about buff/shield application is that shake if off was notoriously slow when applying to the party it was common for half of the party not to get it applied for the mechanic happening. Just a few patches ago, it was buffed to apply nearly instantly as well as giving a HoT.

Hi. Since this is your newest released Video on your channel i, as a newcomer to FF XIV want to say thank you a lot for your content. Specialy your Job-guides made me and my friends get a quick grip and a baseline understanding on how and what to do in order to be at least somewhat efficient. Keep it up, your tone of voice wich is always very calm makes it very easy to understand what you try to explain. Calm and Clean Step by Step explanaition. Bug thumbs up 👍

It's funny, I clicked this video because I was hoping you'd mention the mechanic with barriers/shields, and you did! I play SGE a lot, and I've noticed that sometimes I can pop a shield a very short time before the damage hits, and the shield still gets absorbed. This always feels great, especially when I compare it to, say, the amount of time I have to wait at times before I can start casting after moving/being moved by an attack, or the couple times I have died casting Superbolide just as a damage tick was coming in. I've had several moments during raids where I was able to save a player from dying using a shield, and I always feel thankful to the devs for the apparent leeway they granted me in that moment :D

Lol the ending bit about plenary indulgence reminds me of the pet ghosting and delays summoner/scholar had to deal with ShB. I did UWU with friends and to properly align stuff like fey illumination 1 or 2 GCDs earlier or else it wouldn't apply until after the aoe.

Raidwide damage from bosses is also applied individually. It's possible for a bosses enrage cast to kill some players, but some others survive to land the killing blow. Very weird, but moments where that happens are always very satisfying. Dunno if its intentional or just a design quirk, but I hope it stays like that so we can always have those just barely scraping by moments.

When you consider that framerate varies across locations, content and devices, planning for caster tax at around a minimum of 30 fps can still be risky and yet increase all of your estimated hardcast times by a whopping 0.166+ seconds. It surely doesn't matter if you just follow guides on the internet, but it makes a world of difference for BLM optimization and theorycrafting, and it's kinda funny how the job that's most affected by caster tax is also the one that needs to deal with the constant looming threat of dropping astral fire or not getting all umbral ice ticks depending on spell speeds. Anyway, great video as always, I've been really enjoying how knowledgeable you are, I had never heard of backcasting and I'll certanly try to play with it going forward! Although I'm not really sure if it can work with a controller :(

your point about determination affecting all healing skills is true, but one thing to note is that the heal from holy spirit and holy circle is spell healing. Even though its an additional effect, the gcd is still a spell and the healing from it is spell healing. before they changed divine veil to activate on being pressed, it used to place a buff on the pld that would become an aoe shield on everyone else when the pld received healing from any spell. the self heal from holy spirit, circle, and all hits of the confeteor combo activated veil Also its worth noting, player ground effects tick immediately on application on top of on the regular server tick. so things like assylum and doton actually tick one more time than just duration/3

The one-at-a-time effects of AoEs can be especially weird when two of them are happening at the same time. For instance, a raid wipe might go half way through your party before your tank LB3 starts effecting people and 4/8 of you survive. This has happened to me three times in a Shadowbringers trial. I'll get that timing down eventually.

To note, the reason you can't 1-to-1 compare melee strength jobs to tank jobs for potency and such is because of how strength is calculated for both jobs. Tanks don't get the full effectiveness of their damage stat, while melees do.

Worth noting: Slidecasting is something you will see in WoW as well. One of the most popular WoW addons since at least as far back as Cata (or maybe Wrath? It's been a while) has been Quartz for this reason. It puts a red section at the end of your castbar to inform you when your cast is *actually* done according to the server as a result of latency, so that you know when you can move. (I feel like this is a feature that FFXIV should steal for it's UI) In FFXIV you instead have to put an emote on your bar to get a decent idea of when you can move. FFXIV is absolutely unique for it's animation locks, though. It's something WoW players don't have to deal with, and it's why we can only weave so many oGCDs into our rotation.

long combo breaks can come up for any melee when bosses go off and do stuff. for example, lvl 83 trial leaving to do astral eclipse, a monk might interrupt their combo with six sided star just as the boss leaves. the combo remains active until the boss returns.

Whats even funnier is that when the shield application change came, they changed all shields except they forgot Blue Mage. Try using Gobskin in a party and notice how slow it applies compared to the rest of the cast

For the last point this is actually super important for a WHM casting holy. I tell all new WHM I see to swiftcast the first Holy to get around this. That long cast time and the single target at a time stuns can be lethal.

You're correct about shield application speed being changed in endwalker. As a scholar main in Shadowbringers, I remember all too many times I was slow to get a shield out. Seeing my cast finish, raidwide goes out, hp getting hit, then the shield being applied.

The fact that shields apply instantly doesn't apply to every instance of applying shields. I dunno about other healer jobs but for WHM, divine benison needs to be applied around a 0.5-1 GCD early (in my experience) otherwise the shield appears but it is not registered in the damage calculations, basically shields having its own snapshot timings

I'm not sure if anyone's brought this up but the example at around 16:30 isn't entirely accurate. It's a common misconception among players who have noticed this that it means the damage is registered. The number shows up, yes, but it doesn't mean that the damage (or healing) has actually been applied. What's actually happening (for whatever reason) is the damage calculation was already done and snapshot, but forcing the number to show up by using another skill doesn't change the application time and the number being there is purely visual. It's easier to see on White Mage because many of their skills have relatively long application delays from their snapshots. If you try to use Glare, which has a ~1.3s delay from snapshot to damage application, on an enemy that's about to disappear (like in a raid or something) and immediately use another skill to force the text to appear, you will see in a log that while the numbers showed up, the damage didn't actually register. It's a little cloudy because many skills have varying damage application timings and it's not obvious right away what those are without looking at a log. Another way to see the effect it is to use a skill while jumping into a death wall. Many times the text may already have shown up but you don't aggro the boss because the damage never registered before you died.

4:30-4:35 - Its your left foot btw. Every character models pixel is under their left foot on idle animation 1 (Due to character models being mirrors of half of a body in most cases in most online video games to save on space / RAM for loading, mirror will load easier than a full model.)

I make use of the single pixel safety all the time. It's so much fun to do.. Find the absolute smallest safeshot to dodge things and watch people be confused

Idk why but i always find the term hurtbox funny. Also in reference to around 16:00 I noticed it is possible to use a spell like adlo that heals and shields in such a way that the healing is applied after the hit, but the shield before. When this happens the shield absorbs the damage, then the damage that went thru the shield is immediately healed.

I do remember noticing the buff application thing whenever I was playing WHM and spamming holy, as whenever I tried to use an OGCD like assize or whatever, the static noise and stun debuff seemed to apply right away, instead of taking like a full second to appear. On closer inspection though, it seemed as if the enemies were still attacking until the animation for holy actually went off, so it might just be a visual glitch. That or just my latency.

I've seen from the sequential AoE thing some players dying from a forced Tank LB3 raidwide because the tank started LB3 at the last second, and the dead players happened to be 20-30 yalms away.

W/re Asylum, the way I understand it is, it doesn't pulse healing on each person's server tick - it pulses healing on YOUR server tick. I.e. every time your server tick comes up (when DOTs and HOTs on you would tick), it heals everyone in the bubble. That's why it's treated separately from the DOTs and HOTs on each individual person.

I love how ridiculously technical your videos are, and I posite a question for you: Blue Mage has the spell "Toad Oil" that raises evasion by 20% but I can't find any information in exactly what the base or current evasion is. Think you'd be able to help figure this out?

So I had an idea from watching the caster gaze thing (#4). I remembered testing at e8 and it not working until I was far enough in the hitbox. I've tested some more with a few different hitbox sizes (e8, o11, o10) and I think it's based on being within an absolute distance to the centre of the hitbox, which I estimate to be 3-4y based on collective unconscious. At a dummy, you can be outside the hitbox, whereas I found the larger the hitbox, the farther in I had to be, seemingly the same absolute distance from the middle as the dummy at a glance. With actual bosses, you also need to watch that they haven't moved over to you in that time or get a friend to tank it and keep it in place. FWIW, I seem to remember one or more of Ily'a wiggle trick video and Xeno's legacy-with-strafe video describing a difference between legacy and standard. One interesting note at o10, I noticed this seemed to be about the same distance that the boss would stop adjusting and moving toward me. For another really weird feature idea, I'd toss out the cap of number of people that can be hit by one attack. One of the early Bozja fights showed it off pretty well with that attack that iirc drops everyone to low or 1 hp, with a few people on the edge not getting hit. Similar topic, I guess the buff/debuff limits could apply (buffs coming up with duel cheese), though those are more clear from a programming perspective of maintaining well-known upper bounds on computation.

Love your in-depth explanation of ffxiv advanced combat mechanics! Thank you for amusing videos!

On snapshotting, it seems like there are actually several different *kinds* of snapshotting when it comes to taking damage or avoiding it. 6.2's EX trial for example has attacks that rely on the animation, attacks that rely on the castbar like most of the other attacks in the game, and sometimes there were attacks that snapshot slightly after the castbar finishes but without being tied to a specific animation.

fun fact, AoE attack application order meant that before 6.3, Machinist could actually get 7 instead of 6 stacks of wildfire on a target by using Wildfire immediately *after* a scattershot, as the effect would be applied before the damage. This would only work if there were a bunch of other targets closer to the machinist, so not exactly a common situation.

A lot of the weird behavior here might come from a couple things. I remember hearing about a developer Q&A that addressed some of these things and, essentially, a lot of the weird server/timing issues are caused by the fact the game was originally developed for PS3 and PC. They also expected a lot of players to be using wifi. Their solutions to trying to sync the experience across multiple platform and connection types was to offload a bunch of the calculations and timings to server side and handshake things between client and server. This largely avoids discrepancies between server and client side timings, once you learn FF14's unique timing interactions. That's why, once you get used to the timings, you very rarely experience a "server disagreed" moment. Sort of like their version of rollback. Another stance - held entirely by Western gamers that are very angry, so take it how you will - is basically that Japanese devs refuse to implement good netcode because Reasons™ and ego, which I don't really buy. Lots of Japanese developers outsource to countries like Korea, Taiwan, Vietnam, the United States, European nations, and even China now, all the time. I somehow doubt that a Japanese company that outsources part of development to another country entirely would refuse to use game technology just because it was invented elsewhere. The Playstation and BD's were jointly developed between Japan and Korea, ffs. It just don't add up. Seems like gamerlore and not reality to me, but I suppose it's not completely impossible (even if totally unlikely) so I guess we can't write that off completely.

I've got one, sort of. This is pretty much common knowledge but Physick is functionally broken for SMN. The problem is that ACN (the class that SMN evolves into) scales off of the MND stat, but this spell does not change when the class evolves into the SMN job. This means that Physick scales horribly for SMN only, as you have no MND because you only use INT. For some reason, SqEnix refuses to either fix it or remove it. It's been this way for 10 years.

Though i knew most of this information its good to know i wasnt going crazy when it came to some of the weird interactions of this game

I guess they should change the description for determination to "healing actions"?

4:00 I can't tell you how many times i've exploited this for fun during EXs or Savages over the years. You literally can survive anything if you know the pixel xD

Number 1 weird mechanic presented right in your face as you create your character: Potato People

I’ve been making use of that barrier speed fearure a lot on Sage. I play on controller and sometimes I’m in the middle of A GCD when the boss is casting. That split moment after the cast finishes but before the animation pops is typically just enough for me to sneak in a eukrasian prognosis or diagnosis. Also I’m testing a macro that allows me to stay focused on the tank while casting dosis by having it target the tank’s target. Its a small difference but can confirm it does feel like a janky little delay even if I’m spamming the macro. I play on controller so I wanted to try something out that makes the targeting aspect a little easier for weaving purposes. Sad to say I don’t think the macro is it. Other downside to it is I have to watch the boss more closely because I can’t see their cast bar.

Attack snapshots are especially interesting with gaze mechanics. Most gaze mechanics slowly ripple outward - think of the first boss of Weeping City of Mhach, who does Frond Affeared. You have to wait until the "dodged" message pops up before you can turn back to her, or you get feared. But a couple gaze mechanics go out all at once. Later in the same raid, during Ozma, there's a gaze mechanic where you only have to look away for a split second right as the cast goes out, then you can turn back instantly.

For (7), while it's a good observation; the tank mastery trait is most likely a mistranslation, you deal 20% less damage on all actions while taking 20% less damage as well. So that nice looking 1.2k potency double down will innately deal around 960 without No Mercy (1152p w/ NM). The only ability that is not applied is DRK's Living Shadow, meaning it deals close to the stipulated potency with the only drawback of not being buffed by Darkside or the class' job Mod among other things. Job Modifiers is another attribute that makes it hard to compare potency within the same class archetype - it's essentiall bonus stats based on the job, but for damage calculations it uses the class's main stat. This only applies to Melees and tanks as they have varing job modifiers that affects their damage (PhyRange, Casters and Healers all have the type JobMod within their archetype). To really show case how Job Mod affects final damage. Take DRG's Geirskogul and SAM's Enhanced Enpi, on paper they're both 260p Under no gear, no personal or external buffs. The Geirskogul will be dealing slightly more damage on average by a little bit. This is because DRG's job mod is 115, where as SAM's is only 112. If you want to compare tanks and melees the disparity is much worse: GNB/PLD are 100, whereas WAR/DRK are 105. What JobMod is used for is to calculate f(WD) a multipler that is used to calculate the actual damage output to my knowledge - and f(WD) uses the base Weapon Damage on your weapon alongside a level modifier (don't worry about it). There's more to it than just jobmod and f(WD) when it comes to calculating actual damage output, but it does make it so that you can't really compare potencies between class archetypes or somethings within the same archetype in the case for tank/melee. If you want to compare damage or burst between classes you'll have to just calculate it from the ground up. Akhmorning has most of the formulas you need to calculate it so, but the values and modifiers might be outdated because of the stat squish and also not being updated to current patch. The other work around is using modified potencies where it's potency x total buffs. We can take NIN's for example, Hyosho is 1300p, but it can only be casted under Kassatsu so it's potency before trick will be 1690 modified potency, multiple that with trick and we'll get 1859p. If we want to know the modified potency of a NIN under 2 Mug + Trick, its just 1690 x 1.1 x 1.05 = 1951.95. I don't remember if the game just floors the values or rounds it up.

I would actually argue that snapshotting is not unique to this game, and is actually the norm. I say this because as a general rule graphics and animations are processed independently from game logic. There's a number of reasons for this, the biggest being the fact that in a server-based game, there are no graphics or animations being run on the server itself. So determining whether or not you get hit by an attack based on whether or not you were in the attack animation makes little sense because the server isn't even rendering the animation in the first place. Additionally, checking for collision between a character model and every particle or graphical element of an animation, in real time, would just be a very inefficient and slow way to do so. This would basically be like rendering physics for an animation scene, like in a movie or something, which are typically pre-rendered by simulations and not done in real-time. Checking a character's position relative to the attack's position at the time you need to know if they got hit or not is far easier and faster, and how basically every game does it. Instead, the difference between FFXIV and most other games in this regard, is that often times games will customize their animations to align with the game logic as best they could (or may also customize the game logic to delay when the 'hit check' is performed to give the animation more freedom). FFXIV instead has opted to focus on making things like the ground telegraphs align with the timing of the game logic while allowing the regular animations to just do their own thing. Additionally, while it typically appears that the application of damage is aligned with the attack animations (which is perhaps what makes the snapshotting behavior seem so apparent), I suspect this is just a client-side illusion, and that the server actually considers the damage dealt at the same moment that the snapshot happens. This is why, for example, as a tank if you hit a defensive cooldown or invulnerability between the snapshot and the damage application of a tank buster you still end up flattened, it's literally a "you're already dead and don't know it yet" moment. I imagine this also has to do with that last point you had where doing certain things can cause attacks or healing to be applied more quickly than normal, in reality (ie on the server) these things all happen simultaneously all the time, and the client just spreads them out for aesthetic reasons (maybe the devs think that it feels better to see/hear decimate hitting each target individually), but under certain circumstances they need to just get through the combat text for one attack right away in order to deal with the weaved ability.

Tried to do backwards casting but it didn't work, then i found out it only works in standard type movement. Is there any way to do it in legacy type movement? I already tried wiggling while holding right click but it didn't work.

The determination tooltip is wrong in english. In German it seems to be more accurate: Entschlossenheit: Je höher dieser Wert, desto höher der ausgeteilte physische und magische Schaden und die Höhe der durch Magie geheilten LP. (Translated in English) Determination: The higher this value, the higher the physical and magical damage dealt and the amount of HP healed by magic. healed by magic... this is the point. In my experience, Japanese is often difficult to translate into English. However, it seems to be a little easier into German when it comes to an accurate translation.

I remember using ninja and when lagging, I could dual ninjitsu when the lag caught up.

"Dont all strength based jobs do that why do you need a trait for that?" Well no because they didnt at some point. Short version tanks used to scale dmg only with str but them they changed it scale using only vit for awhile.

Dude, get some spellspeed. ;) Telegraph snapping is heavilly affected by latency. As EU player, when playing on US alt, im getting snapped by telegraphs i would be easilly out of in time on EU server. On JP alt is even worse, some fast AoEs are nearly impossible to dodge unless you predict them(and sometimes not even that). My ping to US is something around 100ms, to japan it can be over 300. That makes difference. Other thing that affect telegraphs is FPS. On my old laptop, i was getting hit by landslides and pudles on Titan all the times, just because those animated telegraphs rendered much slower(rendering latency). But i had very low fps running game on bare minimum settings, so it was extreme example.

With regards to the tooltip on determination which increases the healing of all spells, you need to look past how FF14 catagorises their skills. Spells with cast timers = Spell 0GCD or Instant casts are called Abilities. On caster at the end of the day whether it is instant or has a cast timer, they are still technically casting a spell, thus getting the benefit from the necessary stats.

Which is really frustrating because BLU specifically cares if you use a spell or ability, because if you use something that boost physical spell damage, it doesn't modify physical ability damage, such as Titan's move.

Dots and hots arent on a server tick, its on the mobs cycle set when they spawn. In a dungeon its all at the same time but in the field its based on when the mob or player appeared, desyncing it.

the - when aoe vanish and you stood in it, it will still hit you even if you dash out of it feels so weird to me after decade of WoW, where spell hit you, if it hit you:D also what really isnt explained for Red Mage - their swish swash combo is only increased by their buff (+5% magic dmg* if the use mana to cast it - and off Global Cd dont have increased dmg% for some reason) also at Leviathan?? when we are supposed to cast spells, we can do our swish swash combo without mana and off global cd, because they arent spells, but our swish swash are spells when using mana

the spell travel time hurst my soul. I main AST and for P10S' harrowing hell I always use macrocosmos (of course), I would prefer to make it go off on its own after the knockback but sometimes in PF things go weird and I have to manually use it to save our asses. So that week I was trying to get my reclears and I have to manually cast it. Everyone is saved... but the sage who dies to the late snapshot. We wipe that pull and go into another... where the EXACT SAME THING happens and the sage is the ONLY ONE where the macrocosmos went off late.

Snapshots are definitely the weirdest mechanic to learn, especially with how inconsistent they seem. I cant even count how many times my corpse ends up out of the mechanic when it goes off with the non-telegraphed snapshots.

4:41 had a healer pull me and get me hit once because I did exactly that

doesn't Slidecasting window scale with 2x latency as well? more lag makes it easier to do

Although the potencies are differnt based on the jobs, I always do find it so odd that aspected helios and medica 2 share the exact same potencies but medica 2 is a lot more expensive

A little sad to hear about the potency variance between roles. I had thought the release of Endwalker standardized it across all jobs once and for all, but it turns out that that didn't happen.

1. Just get some spell speed. 2/3 Yeah, game feedback with latency and server issues were such a big problem. They had to scale back to the pixel. Even now you can still get hit by something you were no were near when the spell goes off thanks to server latency, so have to take that into account.

Our static calls snapshots, snapsh!ts lol

The "Healing Spell" refers to stuff that comes out of your job actions. It's a fantasy game. You cast spells to heal. It should be understood as healing magic. This is the age old tooptip that excludes potions and incoming healings from other players.

point 10 was the core of shb pvp btw

Didn't know about the caster tax. Explains why my macro'd Holy button never seemed to be a DPS loss like everyone including myself figured it should be.

Nooooo he leaked my secret party trick in Mt. Gulg!!!

As an extra bit related to attack snapshots, your position only updates while you're on the ground. If you jump, your location is fixed at the pixel location from the moment you left the ground, until it updates the frame you make contact with solid ground again. This is how you can be hit by an AOE you appear to be out of if you bunny hop and your position hasn't updated yet. Extra aside, this is also why movement skills like Shukichi, Hell's Egress/Ingress, En Avant, etc. move you across the ground, and can never be used to jump gaps.

I mean, at least living shadiw makes sense that its that specific race given spoilers, though that begs the question of if TBN scales as if you're always an elezen

I was today years old finding out about the fact that the racial stats actually effect living shadow. LMFAO This whole time I was under the assumption it scaled off just the player

Can we talk about closely grouped mobs, like in the latest alliance raid, not getting hit by aoe? Why is it that some mob groups, usually the trash in alliance raids dont get hit by aoe, or are severely limited to getting hit by it? I used standard step on dancer in the middle of the mob group after nophica and it only hit one enemy. How the hell

Some of these are literally standard for MMOs.... noSpelling Queueing and 3 second ticks especially. It's very rare to differ on either of those. I can't name a single MMO that doesn't use combo timers either a combo will ALWAYS have a set time before you lose the combo that applies to other games with combo systems as well. Snapshotting is pretty common too but I wouldn't persay call that a standard unlike lack of Spell queue in macros, 3 second ticks and combo timers. These are not at all weird features, Potency Comparison is highly debateable as well :L it's been done the way XIV does it but that one is for sure not standard however it's not rare by any means. Job stat curves + different formula for something is actually pretty normal though you see it more in single player games vs MMOs but it is present in them. Never played WoW but I HAVE been playing MMOs for over 2 decades, so I can very safely disagree with these being weird or unique to XIV for that matter.

Class time yaaa

The caster tax should be BLM tax because RDM has 2s casts with 2.5s recast.

As much as i love the game, the attack snapshot mechanic is still one of the most annoying things in the game. Especially when, in harder content, some attacks are near instant, which means you need to predict when it'll happen and move a while before the boss even starts to prepare the move.

CUMBO TIMER

Quick note about spell speed on black mage: Thundercloud Thunder 3 is such a significant portion of Black Mage's damage that Spell Speed is actually very preferred, since Damage Over Time actually scales with spell speed, and since Thundercloud clumps 30 seconds of DoT into one massive hit, it means that said cast is going to be dealing that much more damage! Every 30 seconds you get much more damage for running around a large amount Spell Speed as of level 90 because of that, on top of the obvious advantages.

Cumbo.

The reason it isnt explained is because it isnt a mechanic. Its just the nature of latency

What's wrong about the burst meta?

the cast bar fades in with the cast already in progress (2.44 remaining) - plenty of time for the bar to fade away and back between casts.

for 4, you have to be using Standard type movement, which is objectively inferior, really

I love having a STEM degree for blm

level restriction on glamours is dumb and needs to be gone

It's called Hitbox, not Hurtbox.

you're slidecasting a bit too late and losing some mobility. don't know if that figures into your numbers, but you can gain a touch more movement every gcd.

As someone who does normal, extreme, unreal, savage and ultimate's. like all the cast timers, server tick manipulation, slide casting kind of matters but not really, but mostly none of it actually matters. Personally I feel videos like this one tries to make it seem more complicated as it actually is. Really maybe MAYBE 1% of the player base that parses where this stuff would be a factor, would actually use this information but again, not care. all spell cast times, by the time you are parsing in the higher tiers, you know what your class will do and don't need to sit there and server tick or over refresh your dots. like lol its all just bloated information to make it look more complicated than it actually is. This video is 100% misleading.