Empy +2 Possibly Bugged?

Well well well...
https://forum.square-enix.com/ffxi/threads/62601-April-3-2025-%28JST%29-Version-Update?p=665592&viewfull=1#post665592

I'm more than a little surprised to find that these were the same, or at least, an interconnected, bug. While I'd made the connection between an SC on the player and the mijin thing, I hadn't thought to check that condition for the empy body bug. And then there's the whole, SC on the mob as well. Which just makes, no sense whatsoever, but... pasta-code, I guess.

This also explains why I saw this same thing happening in the Gigas Ambu, since it can SC the player, the Mercurial Strike your *** for 99k. And when are you Not going to be WS'ing/SC the mob while this is happening?

All in all, glad to see them fix the whole batch of BS. And now I can go rub it in a certain someone's face that this was in fact, a bug, and not intended. XD

it's very weird that there were two different conditions to both cause "excessive damage"

Have to see if the gigas doing 99k damage vod on youtube still exists. I said it was "damage during skillchain" but completely can't remember if it was a skillchain during a skillchain.

The very first ws was upheaval, no skillchain; 99k, twice. The third one was a sc during his sc to 99k

https://www.youtube.com/watch?v=0aJWh5GCJqI&t=806s

Still going to go with "dont ws during his skillchain, it's intended 99k" unrelated to the bug. But we'll have to prove it when gigas comes back.
(which by we I mean sure as *** not including me btw)

That happens to anyone on any job wearing anything, its unrelated.

Just like the 99k Mijin could happen to any job wearing anything anything. And yet it was somehow still related to the same bug. If you look at the dev notes on the issue, empy body was not the only case listed.
Keep in mind, the stated conditions don't actually require an SC to have occurred.

"The issue wherein significant damage could be unintentionally incurred when both the player and monster were simultaneously targeted and readied for a skillchain."

Basically, that's the mob and player were both WS'd or chainbound. Prepped for a SC, not necessarily actually SC'd. Though being SC'd should be equally valid as well, as long as the SC is one that could potentially be continued. The SC itself prepping the target for the next possible SC.

But yeah, next Gigas ambu will show if I'm correct to associate these cases cases. But I think there are sufficient parallels. Would be nice if this did address it and we ended up with another BS 99k instance removed. But perhaps I'm being too optimistic.

Indeed, it says
Wait until eyes are fully open before reading.

What an odd bug. And odder still that it didn't occur more often.

I'd also had this thought. Previously, I'd believed that the 99k Mijin issue required an actual SC to have gone off prior to the Mijin(Which did appear to be the case, looking at existing samples at the time.) Equating it to magic bursting, even though it shouldn't have been able to do so.

But now, knowing it could happen anytime both the mob and player were both "readied for a skillchain".. how did it ever not happen in a namis D environment? With multiple players spamming WS constantly, and the mobs, and possibly adds WS spamming the tank, you'd think you'd think both mob and tank would be in a near constant state of readied for SC... Perhaps the timing was tighter than actual SC windows or something."Simultaneously" as used in the patch notes might have been more literal than simply overlapping SC windows. Perhaps both SC windows had to be opened at the same time or very close to it?

Well, untestable speculation at this point, as this should be fixed now. <,<

Depending how it worked, there is a 3s window after a WS where you actually cannot skillchain, right? If it was just chain bound that mattered, maybe WSing every 3 seconds and keeping it so you could never SC would have saved you.

Similar to what thorny guessed here: https://www.ffxiah.com/forum/topic/58278/enemy-mijin-gakure-can-be-magic-bursted/#3736773

You know, I've forgotten about that gap multiple times while thinking about this and then had it brought up or recalled it later. I suppose that could be me still being somewhat stuck in the MB mindset(can MB instantly post SC) despite new info showing that the relevant point is the player(and mob) being SC readied, not potential MB windows.

It's a good point. Well, assuming the bug works from the opening of the actual SC window and not from the action that queues the "SC readiness" to occur 3 seconds later.

But considering that we didn't see the issue as often as might be expected under the newly known conditions... that might well be it. Enough spam on the mob actually potentially preventing the issue.

The gigas fight seems like its part of the gimmick though. It ALWAYS goes for merc strike after the skillchain.

Sure, but it doesn't always 99k you. And I do think it using mercurial in sequence with its SC is a part of the fight's design. But I don't think it hitting for 99k is. And, much like Namis D 99k mijin, the 99k wasn't something that happened for the original release of the content. Mercurial only started killing tanks with 99Ks after Gigas Ambu returned. I think.. it started from the 3rd time we had gigas ambu... Gonna search some logs.

I don't have any logs of Mercurial Strike for the Original 2016 instance of Gigas Ambu. But I do have 35 instances of mercurial for round 2 in April 2017. With no cases of 99k. Dmg was never higher than ~1,200ish. Although, I suppose it is possible that it existed at this point and I just got really lucky.

The first instance of a 99k Mercurial strike from the Bozzetto Enceladus in my logs was in June 2019(Gigas's third ambu appearance.) Also had a few hits while searching, of LS chat talking about how this is suddenly killing ppl.

This would also be about a year after namis D wave 3 was added. The first instance of a 99k Mijin I can find in my logs was in March 2020. And I played during the initial wave 3 release in July 2018. Though I dunno if I did namis all the way from wave 3 release till I ate that first 99k in 2020. Might have been breaks in there. So the actual issue could have started sooner.

Anyway, my thought here is that neither of these instances of content appeared to have the 99ks on original release. Then at some point, something changed, and they both started blowing ppl up.

Still, it is possible that SE just decided to adjust the Ambu fight when they brought it back. And the only way to really know if something is working as intended is for the devs to say it is. But.. I doubt this was intentional. And we now know for certain that the Mijin thing was not intended. With the many parallels between the Mijin case, and Mercurial, I suspect that the latter is the same.

It'll be interesting to see what happens next Gigas Ambu.

So, maybe I miss the part, but let’s say it’s "fixed", how is that piece better than adamantite ? Or other.

Defensively, it's not better than Adamantite. But it is a good Enmity/SIRD piece with decent meva compared to other enmity+ options. So, you're not likely to straight up tank in it(or at least I'm not.) But it's a good option for casting enmity spells in. And you spam such spells often enough that using it in Namis D before this patch had a pretty good chance of still killing you.

YouTube: https://www.youtube.com/live/4ITJ2ghCwiY

Twitter: https://x.com/leaguemili/status/1904654527980331386
JP take on the PLD Empy body bug. He uses PLD and RUN respectively, against the AA Galka HTBF fight (really clever situational test to be honest).

He uses the phrase "verification person", so if he access to SE QA, I am supremely jealous.

Some of you may not find this useful or interesting, so whatever? Enjoy.