New Dragon-Mireu

Awakening.


what if?

Seems unlikely, I doubt it's that rare for someone to get awakening and then disconnect or leave prior to mireu dying. It can be a considerable timesink on small servers and I imagine people go to DI without being able to commit an extra hour to Mireu. Would be very poor design if so.

I'd bet it's a specific element, damage type, or something like that. I've seen it take 5 minutes or more on leviathan a few times, but never had it cost a win. If it was awakening, that would mean the person went afk and came back just in time to save the kill.

The brew effect was already disproven. That was my first thought years ago.

Since I've seen the bonus reset a few times on Bahamut, my theory is that occasionally if Mireu gets beaten too many times in a row, it'll just eventually have a run where it can't be beaten.

The whole refusing to die mechanic and randomized "proc" are convenient smokescreen.

Though I suppose... Is there a server where Mireu's always been beaten? Like that one bad *** server that never lost the *** Candy for like 12 years?

It's something really stupid like it gets a +1 counter for every trust it final KO's and it kills thousands of trusts

Can rule out the 8 basic elements, I've dealt all 8 types of damage on my RDM.
Unless you have to deal a specific element AND do beyond a certain threshold of damage, I can't disprove that of course.

Some server did indeed have a really, really long Mireu streak, but I do not remember which one it was.

So SE moved the report about Mireu not dying into Accepted Bugs, so at least it didn't get immediately thrown into This is a feature.
https://forum.square-enix.com/ffxi/threads/62293-Mireu-at-1-for-20-minutes-despawned-instead-of-dying.

Better very very late than never I guess.

They’ll post a video of how to take out that last 1% with zooms in on the chat log.

Need to dual wield kraken club for the last 1%

It's because no one would cast Xzone because they wanted their personal points instead of worrying about the server streak. You guys failed Mireu's selflessness check.

Probably thinking of Asura, our previous loss was in August 2022. Our consecutive monsters count was over 80,000

And Eiryl simply shows up and screws a 2 years winning streak.

Figures.

I just imagined the scene:

Eiryl pops with a tarutaru avatar onion-head type, properly dressed in the eminent gear, swinging a eminent dagger and yelling:

“Hey you slobs, hit harder!”

“Hit faster!”

“You good for nothing, hes not moving and there are only 5 minutes left”.

“You ***, are you guys even trying?”

“WooHoo we lost a Mireu good job everyone”

That only took what, 5? *** years to admit, find and fix.

Nice work reporting this and getting it fixed. That was a frustrating day and Asura lost the DI bonus and kill streak. They should restore the kill-count to whatever it was prior to this bug as an act of good faith.

Roll back isnt possible because this was not a single occurrence nor only on Assura.

As long as i can recall, thats basically the main reason why so many servers lose the streak. Maybe hundreds time this occurred over the years DI was available, really a good job pointing the bug to SE and them to acknowledging it and fixing.

But its really astonishing how it took so long for reports on that happening. I wonder for long time the playerbase simply assumed this was intended.

It did feel like some sort of gimmick.

I wonder how many other obscure NM also have faulty programming while people simply assuming its something extremelly complex. For example, Kumhau proccing. Given how unreliable is to proc it, i suppose it was in the category of faulty programming instead of obscure weakness

Curious under what circumstances needed to trigger for the bug, cause I've done most Mireru encounters on Bahamut for a long time and never seen it happen.

I've done 10 at most Mireu's on Bismarck and saw this issue 3 times. Very infuriating, glad it's now resolved.

Truthfully I hate fighting this stupid thing. It gets really buggy/laggy.

I just tag it with P. ooze for 10% max HP down as soon as it starts and warp out half the time. (Familiar/Unleash Needed).

I noticed corrosive ooze does not last long at all. So I swap to rabbit for healing points.

Nobody can really hate on you for warping out early after doing this. I can literally take it down from 100% -> 90% with my slug and move on with my life.

Otherwise I'm stuck spamming wild carrot to keep everyone in the battle alive between weapon skills.

Pets/Trusts will technically die, but remain on screen or in party. You will be locked out of resummoning until the game unfucks itself .

On occasion you will be unable to target the NM. Pretty frustrating. If you disengage to do something; you run the risk of not being able to re-engage. This got me killed a few times after reraising..

The 1% HP glitch on top of all of this makes me want to avoid this fight entirely.

So glad they got it fixed! Makes me wonder how many other things would get fixed if reported in the official manner, although I bet more than a handful of things have been and it's just 22 year old spaghetti code that prevents fixing things... XD

Then fixing this will mean the price of ash will be reduced and become more stable, they should have considered lowering the kill time to 30 mins. Just to make killing it a thing still, it will be near impossible to not kill it now with how much gear has progressed.

There are 15 other servers (maybe 13, Bahamut and Odin are pretty well populated) that dont have 3000 people online at any given time you know.