September 2025 Version Update

Unless I'm misunderstanding what you're saying, thats what happens when you (outside of these NM's in limbus) Ooze anything between 89-99% HP: its HP jumps back to 100.

i did it on a NM that had 49%* hp

Yeah, and it shot back to 100% cause hp down put it at its 100% value, then dot hits and its deax

1 HP is probably not far off and they have some variable hp boost of +millioms, ooze is overwriting that, then dot kills it

Note the (outside of these NM’s in Limbus) part.

If this has 1,000,000 hp, then ~490,000 hp would be 49%. If the bugged purulent ooze is reducing its hp to a number between 1 and 15 (15 being the listed bio DoT inflicted per wiki), then its hp will be reduced to a max of 1 to 15, or anything in between. Whatever the number is, the damage purulent ooze does itself is irrelevant as the HP down debuff comes after the damage is calculated, and current HP cant be greater than max HP.

This whole “the NMs have an HP+ buff” theory is weird because that implies their base HP would have to be a low double digit number, no?

Im wondering if its just 22 1 stat mannequins that are caked in undispellable stat buffs based on their job

On Cerberus I found the Geomancy NM at 60% in Apollyon. One Purulent Ooze and its HP shot up to 100%, before dying immediately after. I did not directly engage it. Pet only. And I used my pet magic accuracy set to be sure it landed.



I'm going to find some more and see what happens.

If it is just a flat 1 hp, then the only jobs that could maybe survive a tic are jobs that get innate hp bonus like mnk/nin/run/pld, and thats only if SE gave them those traits at all

So are we going to have to set up a fund to pay bsts to clear the NMs a few times a week for the rest of us?

You mean you can't just go out there on a fresh 99bst with 5/5 nyame and pet macc food and just land it 1/1, or unleash spam it til it lands?

Not sure. I just wanted to be certain. My BST is not great, but it has a macc set. I don't have Nyame and didn't use food.

Edit: Found a Pillager THF NM, but mixed feelings on killing it because it robs people of having a go at it.

some random nonsense time:
BST NM in apollyon appears to use charm once every minute roughly, Cruel joke has no effect, charm inflicts bind (so does not work)
magic finale did nothing, so if it has some crazy buff it's not dispellable, yaegasumi doesn't block auto damage so they can't be WS type (idk im just ruling out possibilities)

and i litterally dont know if this means anything, but with a well timed t1 spell you can kill it without dot right after purulent

Also, does anyone have an Ultio Grip? It gives a chance to inflict curse. Might as well see if that does anything too

More likely it's due to the fact that Limbus monsters have/had that stat-allotment mechanic where their ilvl resets on agro/deagro, which refills their HP as well. (as a zone wide mechanic)

It was altered for the iLvl monsters, but the NMs are supposed to be static level.

This means that the NMs had to be programmed in to follow the rest of the way the monsters in zone are coded, so they had to have a deagro'd state and agro'd state HP values.

Obviously, they are set to always be in their agro state stat values, but the base value state still exists. The regular monster's intiailly used to CON as Incredibly Easy before agro or pull, but had their values adjusted after the "fix" for pulling with Silence and the like.

Basically they set the NMs to always be in the, "1" position, agro'd, but for some reason, Arthur's Purulent Ooze adjusts their HP into the "0" position, which I suspect means all of their stats are simply 1 in said position.

It doesn't work this way on any other monsters in Limbus because their "0" position has higher stats than their "1" position.

It's like uhh, intern mistake. He just set the state he thought the NM would never be in to all 1s, cause that's the easiest/quickest integer to enter, and called it good. Set the mob stats to always be in "1" but the HP can't go back up as part of this gimmick, and there's a case in there where passive regen is also ticked off.

So the Ooze is tricking NMs into believing they aren't spawned, so they get their minimum stats and die.

Right like, cause it can't really be Overflow. HP down just works in set%HP = NewmaxHP. It's not healing and breaking a data point. It's setting 1HP to be 90% of 1 HP, because adjusting the NMs' HP total is causing a false flag interaction with Limbus HP coding.

That's my guess, anyway. Byrth's #3.

The most likely explanation is that these have very low native HP, with an atma-like buffs that give them a Max HP Up buff. Purulent Ooze applies a Max HP Down that overwrites it, and then the DoT does the rest.

Mannequins aren't normally an enemy NPC but thinking that they are is indeed hilarious.

The max HP buff explanation is the most likely to me. Using something like that would allow them to more easily scale the HP to the amount of players on server, amount of people in the zone, amount of limbuses killed, or some other population adjusted measure.

I highly doubt anyone's made a controlled attempt to see how much HP they actually have (would be difficult since you likely lose a ton of info to packet drop with that many people), but curious if it's actually the same on Asura as small servers.

Sep. 11, 2025 2:00 (PDT)

[Affected Service]
- FINAL FANTASY XI

[Update Details]
- In Limbus, the Notorious Monster deployed in the version update on September 9 was configured to be stronger than intended and so we have lowered their status in consideration of future updates.

The following issue has been addressed:
- In Limbus, if a Slug summoned by a beastmaster performed the Purulent Ooze special attack against certain monsters, it would cause the target’s HP to become 1.

So bad news they probably ended our BST fun, good news they supposedly weakened the NMs

Somehow they gave bst throat stab

The idea that they gave the mobs 1 hp base stat and made % based scaling overwritten by ooze is... insanity.

The base hp should not be a 1 lul

more alarming is that they considered them too strong and nerfed in less than 24 hours after release. that's definitely a first.

Well, the mnk was clearly broken.

probably based on martel's post, but broken and too strong aren't the same thing.