Blue mob spawning logic is broken, large repetition of mob types

So monster mob spawning logic is busted. I have twice now encountered entire area's with abnormally high quantities of a specific mob type. When delving I encountered 5 corrupting fever mobs along a single track line and was lucky I didn't bleed out as a result of NOT having immunity.

Today I encountered SEVEN burning ground mobs while playing MELEE in a single area. S.E.V.E.N. I didn't even continue, I just straight left and restarted the instance after that.

Thankfully I have yet to have encountered a build breaking occurrence in maps or delve that just completely and totally gimps a run. But if it is ever at any point in time possible for an entire map to spawn as a mob that the player is bad against and it not be the result of mods present or special circumstances, then this is not ok.

Please fix, because unless a map or area is intentionally moded with something that directly adds these mod types in, this is absurd.

isn't that exactly what the initial patchnotes 3.19 described there:

"

We have toned down the modifiers that can spawn on magic monsters so that more of them are stat-based bonuses that aren't too spammy. All monsters in an instance that are the same or very similar will have the same magic monster modifier, rather than rolling a different Archnemesis modifier for each monster.

"

BunkerkindAnni wrote:

isn't that exactly what the initial patchnotes 3.19 described there:

"

We have toned down the modifiers that can spawn on magic monsters so that more of them are stat-based bonuses that aren't too spammy. All monsters in an instance that are the same or very similar will have the same magic monster modifier, rather than rolling a different Archnemesis modifier for each monster.

burning ground and corrupting blood aren't stat based. while it might have sounded good on paper it was a nightmare in implementation when these instances occurred.

Encountering large quantities of the same mob type in an area when the mob type is deadly to your build or setup feels insanely bad, because rather than a single dangerous mob ITS AN ENTIRE ZONE.

Being melee and encountering seven mobs of burning ground is horrifying. Not seven enemies, seven mobs of 5-10.

Running an entire delve without corrupting blood immunity and having it regulated to flasks is disgusting with this implementation.

I really don't feel like this is what they intended, as this just made it worse......

"

Raghin wrote:

"

BunkerkindAnni wrote:

isn't that exactly what the initial patchnotes 3.19 described there:

"

We have toned down the modifiers that can spawn on magic monsters so that more of them are stat-based bonuses that aren't too spammy. All monsters in an instance that are the same or very similar will have the same magic monster modifier, rather than rolling a different Archnemesis modifier for each monster.

burning ground and corrupting blood aren't stat based. while it might have sounded good on paper it was a nightmare in implementation when these instances occurred.

Encountering large quantities of the same mob type in an area when the mob type is deadly to your build or setup feels insanely bad, because rather than a single dangerous mob ITS AN ENTIRE ZONE.

Being melee and encountering seven mobs of burning ground is horrifying. Not seven enemies, seven mobs of 5-10.

Running an entire delve without corrupting blood immunity and having it regulated to flasks is disgusting with this implementation.

I really don't feel like this is what they intended, as this just made it worse......

both of those are from AN mobs, both have easy solution
Corrupted blood - use a jewel with CB immunity, even if its worse for your build overall(tbh if hit yourself you should have this as a default)
Burning ground - go back to hideout, change pantheon to get burning ground immunity and be done.

"

dorkdude2 wrote:

both of those are from AN mobs, both have easy solution
Corrupted blood - use a jewel with CB immunity, even if its worse for your build overall(tbh if hit yourself you should have this as a default)
Burning ground - go back to hideout, change pantheon to get burning ground immunity and be done.

That doesn't fix the buggy design and issues, it just ignores them.

Both of those are what are called fun taxes. Fun taxes are things you have to do to ignore mechanics completely in order to have fun. PoE is absolutely overflowing with fun taxes. I want mechanics I can interact with, not that I need to ignore in order to have fun.

I want to "interact!" and have fun. Not "ignore set and forget" because it feels bad.

Cap resists, immune to ailments, immune to bleed and corrupting blood, immune to stun, large amounts of accuracy if ur an attack build because reasons.

I can either pay the tax and be silent, or protest the bad buggy design that causes everything to instantly kill you if you don't pay up to begin with.

Thankyou for reminding me about the pantheon, but it doesn't fix the initial problem of it being a broken mechanic to begin with.

"

Raghin wrote:

"

dorkdude2 wrote:

both of those are from AN mobs, both have easy solution
Corrupted blood - use a jewel with CB immunity, even if its worse for your build overall(tbh if hit yourself you should have this as a default)
Burning ground - go back to hideout, change pantheon to get burning ground immunity and be done.

That doesn't fix the buggy design and issues, it just ignores them.

Both of those are what are called fun taxes. Fun taxes are things you have to do to ignore mechanics completely in order to have fun. PoE is absolutely overflowing with fun taxes. I want mechanics I can interact with, not that I need to ignore in order to have fun.

I want to "interact!" and have fun. Not "ignore set and forget" because it feels bad.

Cap resists, immune to ailments, immune to bleed and corrupting blood, immune to stun, large amounts of accuracy if ur an attack build because reasons.

I can either pay the tax and be silent, or protest the bad buggy design that causes everything to instantly kill you if you don't pay up to begin with.

Thankyou for reminding me about the pantheon, but it doesn't fix the initial problem of it being a broken mechanic to begin with.

except it isn't buggy, its working as intended.

I don't disagree with the layers of defenses/immunities/other offensive stats required these days making it harder to enjoy the game.

"

dorkdude2 wrote:

except it isn't buggy, its working as intended.

I don't disagree with the layers of defenses/immunities/other offensive stats required these days making it harder to enjoy the game.

Is it tho? We don't have hard values for the data that it is indeed working as intended, only that it feels bad. And if it was all working as intended we wouldn't be having repeated nerfs to Archnemesis in general, which is in fact very busted and unbalanced.

Galvanic Field wasn't working as intended on release where it's 15% more dmg per 5% shock was busted. How do we know someone didn't typo a 9 as a 6 somewhere in the damage modifier multiplication?