In programming term there are things call edge case. Edge case is a situation created outside of normal design e.g. racing condition where two conditions timing can create undesired outcome if one happen before the other

Those are normally hard to reproduce if they dont know the exact trigger condition (e.g. if it only happens during server lag, then they may never encounter it on your local machine)

Without knowing the code, it will be hard to know how hard to fix it.

As for disabling it, I think it should easy (e.f. simply remove it off the pool of rewards thst use oath rune combination). But I am not sure as I dont have access to their code

It’s wild. The patch the released that broke it literally had one note about MTX and that’s it. I don’t understand how it can still be broken nearly six days later. Expeditions are the only challenging content in the game atm. They’re the only thing I enjoy and they’re what pushes me to actually want to upgrade. I’ve barely played since Friday, and I’m about to go away for five days so I think I might just be done with the league.

They fixed it once. Hard to believe they can’t fix it again.

Can we just permanently remove the rune. Or at least the function? Having unkillable enemies is INCREDIBLY unfun. Make enemies with massive health bars if you have to, but please remove the “enemies are invincible” bullshit

It’s definitely getting old.

As a dev, the bug could be challenging to track down however I think disabling/replacing it would be a solid hot fix for the time being. Especially considering the severity

Easy to fix.

Remove the rune.
Increase the amount of health each kill removes from the parent monster so you don’t have to kill them all to kill the parent.
Make them slightly vulnerable so you can chip away at their health regardless rather than being completely impervious.

I’m sure there are other solutions dependant on how their systems work, but none of those would be hard to implement.

Impossible to say without knowing their code

I don’t think the supporter patch fucked it up. I think they never actually fixed the bug correctly. It was happening before the supporter patch. They released a patch that said they fixed it, but I think they didn’t actually fix it. They probably tested it, it didn’t happen for them, and they thought it was fixed but they didnt test all the possibilities and it was still happening for people the whole time.

Please make sure you check the Known Issues List or the Bug Report Forums for any pre-existing bug reports related to your issue. Duplicate reports on Reddit may be removed.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

Depends on how hard it is to figure how to reproduce the bug, and if fixing it will break anything else in the process.

From GGG’s perspective isn’t the bug that stops the game from working, and that have forced many players to give up playing, and still happens , a much bigger concern ?

They probably already shifted most/all of the resources to the content for the reset patch and it’s more of an issue of focus then how hard it is to somehow fix.

“its late Wednesday, the bug appeared like on Saturday if not earlier……why?”

the bug appeared two months ago.

One possible scenario is they fixed the rune and next build they released, the mtx one, was off a release branch that didn’t have the previous hotfix. Happens a lot in programming

It’s probably some floating point bullshit. They can cause a lot of bugs.

I work in construction and I can tell you this bug is easy to fix if you know what you’re doing

It seems to be already fixed now. There was an update 2 hours ago on my steam, and I have not had issues with oath rune since. I even deliberately propagated one for like 6-7 runes.

In the past leagues in poe1 ggg introduced “bugs” that prevented certain lucrative mechanics from working. Could this be happening here? Perhaps. If the trend stays the same, this will not be fixed until the next wipe and will be reworked so that it is not as lucrative.

Wouldn’t disabling the oath rune also disable all the combination/remnant rewards it is part of? Perfect Chaos/exalts, mirror, lvl20 skill gems to name a few (according to Google)

Not that I would mind, but wouldn’t it be significant enough to alter the economy?

They aren’t fixing it, because they’d rather you stop and go play POE 1 in a few days. That’s where their focus is right now, and they just removed RGB color requirements from sockets (making them optional and give buffs instead) to try to get more POE 2 players to play POE 1.

Disable its effect like what they did to the breach talent tree at the beginning of the league. Will take them maybe 15 minutes to implement and 30 minutes to deploy.

GUYS… the bug is unkillable, even GGG cannot delete its code .. we are fkkd

People speak about replacing or removing the runes altogether, I say let’s add a failsafe. If the map only has less than 5 creature alive for a period of time, say 4hours if you really want to be safe, kill all remaining creature and/or complete the expedition. This would be easy to implement and could be a temporary measure until they fix the bug.