Enemy Mijin Gakure Can Be Magic Bursted

I've had a theory for a while, so every time we've been in Dynamis [D] I've been keeping an eye on the damage from Volte Shinobis.

Without fail, every single time there is an open MB window, I take 99,999 damage from Mijin Gakure. If there's no open MB window, it does minimal, frankly pitiful damage.

There's something about SC/MB that allows enemies' Mijin Gakure to do BONKERS damage.

This is on PLD and no, I don't have empy body on, it's in my Mog Locker.

Use this information however you choose. Feel free to post here if you see this in your runs as well, or if you see something contradictory. I am extremely confident this is true after months of observations, it's been 100% accurate with not even a single false result.

I've always thought this is the case, all the 99k mijin I've seen were always followed after SC. For that reason I've always save intervene for shinobis so they miss their WS

what would dynamis be without nin and bst mobs? they account for 99% of the fun.

had this happen to me before, can confirm.

Yeah, this is how the whole issue works so far as I'm aware. I've gone through a lot of logs, and never seen a 99k Namis D wave 3 Mijin without a open MB window. The one time I thought I'd found a non MB window instance, I checked logs on a different character and it turned out that the original character had lost the packet for the WS that closed the SC. <,<

Of course it doesn't say it MB'd in the log.. but.. I don't believe it was supposed to be able to burst to begin with. It's a bug. And I can also recall a time when bursted lunge also didn't say it MB'd when it did(But that might have been a battlemod issue? Not 100% sure there.)

The stupidest bit about the whole thing is that Mijin is non-elemental. There should never be a valid SC for it to burst on since there's never an element match.. but instead.. it'll burst on anything. -_-;

A side note and question. What's the earliest date anyone has ever seen a 99k Mijin occur? Because I would swear that this ***did not happen back at original wave 3 release. I burned out on the event after release, and took a break from the game. When I came back and did Namis D again.. this ***was happening. So I think something in the spaghetti code changed in that gap.

EDIT: Final note. I've never seen this happen to Mijin outside of the special wave 3 mijin. The single target one that ignores DT. Never seen it on wave 1 or 2. And in wave 3, it's not just the NM that can do this. Add/minor NIN's can as well.

Does Fealty help at all on the Fomor Mijin MB issue?

I typically save Fealty for Volte Trainers, so I don't think I've tried Fealty. I doubt it would work though. I think I might've tried it once a while ago and still died.

Using Intervene sounds like a great idea! Bastok is a bit rough because I typically use Intervene on the W2 boss to make the last 50% go smoother, but the NIN NM is in the adjacent circle (fire).

No. It'll still kill you. And while Fealty affects normal mijin dmg, I don't think it works on the single target wave 3 version at all. But.. I haven't verified that for certain.

Rampart does work on wave 3 Mijin, but.. it's not enough to change anything when a Mijin MB's. Still dead. And probably still 99k.

The most effective methods to prevent death by 99k Mijin involve preventing SC. RUN using battuta a parrying all the WS. Stunning/terror'ing, or otherwise impeding the mob(although, if you're tanking multiple mobs while a NIN is being killed... the non NIN mobs can SC you, and then the NIN can slap you with the Mijin...)

The most complicated counter measure I ever used was what we called, "Cover Dance". Where we had two tanks, one tanking all the mobs, and the other popping cover on the first tank and moving in front of the first tank then back out every other WS to break up SC by making them hit different targets. <,<

Intervene is also a good idea. Just limited by recast. And... as mentioned above, other mobs can SC you even if the NIN is missing every ws, so unless you're saving the nin for last and it's the only mob, Intervene won't guarantee survival.

Petition to SE to change Nagi to "Allows Mijin Gakure to Magic Burst".

Job fixed!

Why does Mijin Gakure kill the player but NMs just keep living? That seems like a bigger inconsistency than anything. I've always been miffed at how players always get nerfed versions of monster abilities. Actually, if Mijin Gakure is going to kill the player, they should at least keep all of their buffs, since they're not really dead, just kind of dead.

You have to be a ninja master with a Nagi to not die, I'm sure all the enemy NINs have them...especially the low level yagudo

So umm...whoops. Maybe the theory is wrong?

I always thought its just a matter of resisting and remaining mob HP.

No time stamps, hard to tell if the mijin was within the SC window or not.

You shield bashed after the skillchain, need timestamps to see if the mijin was actually in the window

Not that it really matters but this is an accepted bug based on Martel's bug report from 5 years ago. But given they have 709 of those, I wouldn't expect anything to ever happen with it.
https://forum.square-enix.com/ffxi/threads/56659-Taking-99-999-dmg-from-Mijin-Gakure-in-Dynamis-Divergence.

It would be pretty weird for shield bash to last 8+ seconds on that level of monster

I recognize that the screenshot isn't definitive, legal proof that the mijin wasn't before the SC. I can assure you that in real life while experiencing it, the WS&SC happened before the mijin went off.

There could be some log *** to make it appear out of order, but that definitely didn't happen here.

It could've also been the case that the mijin happened 8 seconds after the SC happened. I can tell you with 3000% certainty that didn't happen, it was immediately after. I ***bricks because I saw the SC and mijin happening.

There are no timestamps on combat logs in game so I can't really do much else. I don't stream dynamis so it wasn't recorded

Windower timestamps do. If you use it, I also highly recommend logger, it's great to be able to go back and look at logs weeks later to verify things.

If players aren't blinking, real log isn't guaranteed to be in correct order anyway. Most messages show up after the animation finishes.

The stun wears off would hit log instantly because it has no attached animation, the mijin would be delayed by animation time unless MT was blinked out. I don't think it's possible for the mijin to have occured after the stun wore off; even if there was no delay for animation the stun wearing off should be sent before the mijin packet and that message isn't delayable.

Maybe it's interacting with the chainbound/skillchain window rather than the magic burst window, though? If the mijin was too soon after the SC, it wouldn't be in the skillchain window yet.

I know there are better options, I just prefer not to use any third-party programs (other than Windower to launch the game twice on my PC).


This could be it actually, I wonder if that's how the interaction works.

This one was definitely VERY soon after the SC, like the second the SC happened. The animations were kind of stacked on top of each other.

Only if battlemod is not used.

Vanilla with timestamps enabled (it's in config) will show timestamps but only after animation ends, yes.

Not for combat. Timestamps only appear on chat messages (examination, linkshell, party, yells, unity chat, etc). You cannot get timestamps on the combat log; the screenshot above has timestamps enabled.

I'll say it's possible.

[Volte Ninja] 923 Blade: Hi -> Certainly
Darkness: 115 -> Certainly
[2] [Disjoined Tarutaru] 39 hit -> Certainly
[Shiroineko] Ice Threnody II -> Volte Thief
[Stun] Carnage Elegy -> Disjoined Tarutaru
[Orefille] 217 hit -> Disjoined Tarutaru
[Disjoined Tarutaru] 195 counter -> Orefille
Shiroineko Ice Threnody II -> Volte Thief (Threnody)
[2] [Volte Thief] 8 hit -> Certainly
[Noreverse] 612 hit -> Volte Ninja
[Noreverse] missed -> Volte Ninja
[Noreverse] 391 RA struck true -> Volte Ninja
[Limn] Cure IV -> Certainly
[4] [Leckergano] 1808 hit -> Volte Thief
Stun Carnage Elegy -> Disjoined Tarutaru (No effect)
[Piyori] Cure IV -> Certainly
[Limn] 1236 HP Cure IV -> Certainly
[Fourthrock] Savage Blade -> Volte Ninja
[Fourthrock] 12439 Savage Blade -> Volte Ninja
[Piyori] 859 HP Cure IV -> Certainly
132 HP -> Piyori
0 HP -> {3}: Vivinn, Gunvolt, and Llamatron
[Onionlord] 543 hit -> Volte Ninja
[Onionlord] 826 critical hit -> Volte Ninja
[2] [Volte Ninja] 38 hit -> Certainly
[Orefille] 330 critical hit -> Disjoined Tarutaru
[Orefille] missed -> Disjoined Tarutaru
[Orefille] 163 hit -> Disjoined Tarutaru
[3] [Noreverse] 1173 hit -> Volte Ninja
[Noreverse] 204 RA struck true -> Volte Ninja
[Volte White Mage] 51 hit -> Certainly
[Vivinn] Cure IV -> Certainly
[Onionlord] 834 High Jump -> Volte Ninja
[Leckergano] 808 critical hit -> Volte Thief
[2] [Leckergano] 758 hit -> Volte Thief
[Volte Ninja] 99999 Mijin Gakure -> Certainly
Certainly was defeated by the Volte Ninja.

Maybe we're approaching this from the wrong direction. Relying on a mob to do it. Why not grab some folks, go into balista, and experiment. Whatever works on mobs probably also works for players.