Hi
In the past week this bug/error has happened to me at least three or four times.
Basically I am killing a bosso o even a small minion and that minion becomes unkillable.
No matter how many times I try, it simply does not die. I normally would not say anything but I am trying a seasonal solo and basically it bugged one of the bounties…
I was at Torment IV - Elder Sanctum - clearing the chest in the bounty “The Cursed Bailey” - and the last demon marauder did not die (time 17.20 Italian time, 18/08/2024).
I am still missing a lot of gear and not be able to close a bounty it is a big deal.
This has happened once o twice during bounty quests, but before it did not bug the quest itself, simply I got nothing from the mob/boss.
Can you please check? Any Idea on how to solve it, apart from start from scratch?
Thanks
Amberdrake68
Longstanding Bug
Do not use black hole. This skill triggers the bug.
are you telling me that Blizzard doesn’t have tools similar to strace (I presume that they’re not developing on a GNU/Linux platform) to trace bugs…this should be an easy fix.
You’re assuming a couple of things.
First the code is purely in maintenance mode. That means unless the code is crashing or doing something like exposing user data to scammers they’re not fixing the problem. Every other bug in the code is now a feature.
The next problem is that the code is a mountain of spaghetti and none of the people left maintaining it have any idea how it works. You claim that tools for tracing would help track down the bug but what’s the bug? A monster with “negative” HP? Incorrect state flags? Is the bug caused by multi threading, a message synch error, a client/server data mismatch?
BTW, if/when you end up with an unkillable monster there is a clunky work around.
Have the monster(s) follow you to the next floor. When you walk down they’ll remain near the previous floor’s exit. Now, town portal back, re-enter the rift and walk/run back to Urshi. Assuming she’s not right next to the down they’ll be out of aggro range and won’t bother you.
If you do end up with Urshi close to the down you can try losing the monster(s) on the map. Assuming you have some dash/teleport/etc. skill slotted you might be able to lose them and be able to interact with her.
But if you can’t then you pretty much have to head back to town and tell Orek to close the rift. You’ll get the XP you earned to that point but not the completion XP or gem levels. Which sucks.
The bug has existed well before “maintenance mode”.
Irrelevant, see above. Blizzard was simply too lazy to fix the issue.
Are you saying that Blizzard has no competent devs?
That is indeed correct, yes.
Pretty much. Just look at the clown show that’s currently happening in D4 with trade duplication every season. That’s basic transactional processing which any 1st year CSci major can crib from a concurrent programming text book. Or that they couldn’t design their own stash system and took the one from D3 and made it worse with 8 players per instance instead of 4 thus effectively having to half D3’s already limited 13 stash tabs.
Wow. I stopped playing D4 after that crappy patch that destroyed my lightning wizard setup. Hard pass. Huge regrets trusting Blizzard and giving them my heard earned monies.
It seems that the game development companies are really struggling with devs and quality code. Blizzard, Bethesda both produce very bad code it seems.