Empy +2 Possibly Bugged?

Do it again with a “explain like I’m 5” edxplanation and following the below format and I’ll translate it to JPN for you.

Operating System:
Specify which Operating System was in use to play the game. (Windows 7, Windows 8, and Windows 10)

ISP:
Name of ISP you use to connect to the Internet.

Type of Internet Connection:
Specify the type of connection. (dial-up, DSL, CATV, Optic Fiber, Other)

Internet Connection Speed:
Specify the speed of internet connection. (Example: 768Kbit/s, 5Mbit/s)

Date & Time:
Date and time of when the issue occurred. Please be sure to state the time zone of your region. (Example: Pacific Time = PST/PDT)

Frequency:
State how frequently the issue occurs. Please select from the following.
1.Always
2.Sometimes
3.Once (did not reproduce)
4.Unknown

Character Name:
Which character did the issue occur with?

Race:
Race of your character when the issue occurred.
(Hume M, Hume F, ElvaanM, ElvaanF, TarutaruM, TarutaruF, Galka, Mithra)

World:
World where the issue occurred.

Main Job:
Main job and level of your character when the issue occurred.

Support Job:
Support job of your character when the issue occurred.

Area and Coordinates:
Area and map coordinates where the issue occurred.

Party or Solo:
If you were solo when the issue occurred, please write “Solo”. If you were in a party, please write “Party”. With alliance, please write “Alliance.”
*If you wrote “Party” or “Alliance”, please also include the number of members.

NPC Name:
Name of NPC that your character was interacting with when the issue occurred.
*If you were not interacting with any NPC, then please write “None”.

Monster Name:
Name of monster that your character was battling against when the issue occurred.
*If you were not battling against any monster, then please write “None”.

Steps:
Detailed steps on how the issue occurred.
*Please try to include the following details.
What you were doing when the issue occurred. (Example: Battle, mission, quest, crafting, synthesis, etc.)
Please do your best to write using official terms for item names and skill/ability names. Please avoid any abbreviations or improper terms. If you were using macro commands when the issue occurred, please include the details of the command.
In case the error message appeared when the issue occurred, please include what the message said.

They already know, they're just literally incapable of figuring it out

It's been a year.

How is this -still- a thing?

Blocked! [Disjoined Galka] 6519 Spinning Axe -> Certainly
Certainly was defeated by the Disjoined Galka.

"Working as intended"

"There are currently no known issues."

Put into storage and forget about it...

I still love the 99999 mijin gakure. That is truly the best.

It's just that Eschite Breastplate is hot garbage due to its age :|

just never fight in it when fighting humanoids. I'd also be cautious if/when you have to fight grahs in neo-neo limbus and somehow vorpal blade counts too

This isn't an empyrean bug, that's just Mijin Gakure.

Source: I've died to 99k Mijin Gakures about once/week for the past 5 years. My empy body is in storage and it's never been in any of my equipsets.

Considering Mijin Gakure damage is modified by remaining HP, and can be resisted, I would also expect that this is working as intended. I've taken a few 99999s as well, yesterday I took 336.

Could be dependent on the mob's HP when it uses it. I think the biggest factor is whether the mijin is MB'd. I've noticed that it seems to hit 99k when I just suffered a skillchain.

My guess is that it's non elemental so it just takes advantage of your lowest resistance rank. If you have a SC on you, your resistance rank is lowered for that element and BOOM mijin destroys you.

I haven't scientifically proven it or anything, but I've been taking note of my mijin results for a little bit and it seems consistent

The previous bug report on this was moved to "insufficient information" by SE. So someone has to be the hero. Follow their format to submit exactly, and include as many weapon skills / abilities that trigger this as possible. It will be a pain, but it is the only way to fix this if you want it fixed.

[url]http://forum.square-enix.com/ffxi/forums/80[url]

It's been done. At least 4 times.

https://forum.square-enix.com/ffxi/threads/62525

Round 5.

Perhaps drop your confirmations before they move it to "Bugged as intended."

What you need to do is take 3 dozen different people and post the same bug over and over and over repeatedly. Until they pay attention to it.

One post a year with confirmation replies clearly ain't doin ***.

Spamming never achieved anything in the history of the internets.

Interesting, your bug report mentions Warder of Fortitude’s Vorpal Blade. I have not tested the body there personally, but I will now. I mean the next best thing we can do at this point will be video proof of the bug occurring otherwise the devs will just continue to move the reports to unable to verify section. I really had hoped my last report where I tested the old 89 +2 body and my theory on it only occurring once CE/VE capped being the one.

I joked fortitude's vorpal could do it, but itd make sense as it seems tied to just the use of player-acquired WS' for whatever reason. Looking forward to a new crop of pics when new limbus is out and the humanoid ghrahs return

So, if this is tied to weaponskills, has anyone ever managed to reproduce the issue in Ballista? (Does enmity even exist as a mechanic in that?)

Being able to say that a player in a fixed set of gear occasionally deals 8x normal damage or whatever while the target has the cursed paladin empyrean piece equipped might actually convince the bug report intern that this is actually a bug and not just NA players whining that the game is too hard.

It can, but it is not threatening due to the low level of the thingy.

Bug does not occur on Fortitude. 0 damage Vorpal Blades the entire time from 100% to 0% HP from just auto attacks with both 89 +2 and 119 +3 body.

The one Fomor NM I have tested before outside of W3 was Bres in the past. Has access to player WS the problem is the CE/VE decay on those Fomor NMs from the past is their gimmick so the bug never occurs.

I've also tested on the Reive fomor in Ra'kaznar Inner Court. They use Player ws as well. Could never get a massive dmg occurrence wearing Chev+3 body and spiking enmity high.

On the other hand, I have seen reports of massive damage spikes in wave 3 namis D from things that are not player style WS. There was a proc on a Eagle Eye Shot once. As well as a proc on the AoE dmg move from fetters.

So the conditions needed for the bug to occur are not simply mobs using player type WS. There's some other factor(s) required. Zone/instance/weird enmity mechanics, something of that sort.Atonement can deal damage to players in Ballista, so CE/VE have to exist in some manner there as well, even for players. That said... I dunno if the bug could occur there.

Explain, why do you do this with the full force of vorseals, buffs and armor? Give the damn thing a chance to hit you. Vorseals need to go, you dont have those anywhere else either.

Also, when I try to solo this on Paladin with just auto attacks, in default Dynamis Sets, it is SO damn slow, that I'd still be there after 24 hours and still slap it, so idk what you did there, but it must be in a completely different world than mine.

Since
- It's pretty hard to test
- Vorpal Blade is Multi-Hit and can easily miss
- The numbers are so low
- The content is completely different
- I have never been killed by Vorpal Blade in Dyna
I've removed it from my post. There's enough evidence from Dynamis Divergence around. Perhaps I could let myself get killed by Demisang Deleterious again, but for now, I'll pass.

These are just parts from my log, I dont want to stay here for hours and hours:
[Warder of Fortitude] 56 Vorpal Blade -> Certainly
[Warder of Fortitude] 62 Vorpal Blade -> Certainly
[Warder of Fortitude] 0 Vorpal Blade -> Certainly
[Warder of Fortitude] 44 Vorpal Blade -> Certainly
[Warder of Fortitude] 33 Vorpal Blade -> Certainly
[Warder of Fortitude] 34 Vorpal Blade -> Certainly
[Warder of Fortitude] 60 Vorpal Blade -> Certainly
[Warder of Fortitude] 54 Vorpal Blade -> Certainly
[Warder of Fortitude] 49 Vorpal Blade -> Certainly
[Warder of Fortitude] 53 Vorpal Blade -> Certainly
...
[Warder of Fortitude] 630 Vorpal Blade -> Certainly
Lucky hit? Idk, I'm still alive. It's so rare to see it on this dude.

Vorpal is 2 hits and can crit. That was probably a crit.

As per description, it should be 4 hits, not 2.

Sorry, must have gotten vorpal thrust on mobile or something. Either way, it is possible for a crit to have a big effect depending on ratio/whether you are using Phalanx/etc.

Trying on WSs that don't crit would be less ambiguous.

Just as an observation, all the log screenshots in this thread have been of huge damage after a skillchain, kind of similar to this:
https://www.ffxiah.com/forum/topic/58278/enemy-mijin-gakure-can-be-magic-bursted/1/#3735716

Could the AF+3 body be making some intended W3 dynamic go badly awry?

It's Empyrean Body - and nope, this happens without Empyrean Body as well. Mijin Gakure has a heavy modifier which is the mob's remaining HP. In W3, unresisted, it does absurd amounts of damage, but has nothing to do with this piece of gear. Mijin at really low HP does nearly no damage.

Not commenting if it can be magic bursted or not, but it is completely unrelated to the Chevalier's Cuirass bug.

Look at that!

It has been moved to Accepted Bugs!



That doesn't mean they'll fix it, does it?