Diablo patch just killed my invincible thorns build

Been on this character for weeks, dont have much time to play because of life so it was my relief to get on and murder on hardcore. Butcher would run up to me and sui by swinging on me, I have clips.

Today i login and start doing the usual nmd grind. I get to the end of one dungeon and i have 1 single elite left to kill but he was a spectre that doesnt attack so my thorns build wasnt killing him. 30 seconds into attacking him. Everything just stops… the game froze but my character can move freely… I literally cant do anything other than leave game but i know if you leave in the middle of ANY fight, regardless of hp itll tag you as cheating and kills you for leaving with low hp.

Right when the game boots me out, i see on the side of my screen “diablo 4 update ready”
Thank you blizzard im tired of this bull:)
Ive made maybe 6 hardcore characters. Not a single time have i died by my own means and errors. Im done.

IT WAS A THORNS BUILD, I LITERALLY CANT DIE, IF BUTCHER SUICIDES ON ME THEN WHY DOES A WRAITH KILL ON DISCONNECT?

Here’s the clip I saved. Wtf seriously I can’t get over this
https://youtu.be/QJADx48w_H8

Your own clip shows you being at half hp from things hitting you. Saying you cannot die is idiotic.

2 Likes

I had over 60% damage reduction when injured, the build plays around being in an injured state. Once that damage reduction bucket kicks in, mostly nothing can kill me. ill stand in a wave of exploding demons and nothing. I’ve literally watched everything do no damage to me what so ever. Even tested if i’d die by disconnect by standing still in the middle of a dungeon with enemies hitting and nothing. Your comment just shows that you don’t understand the thorns build.

Literally also just died after same patch - super rubberband on horse while running thru helltide. Exploders appeared in thin air, and exploded without warning (on horse, stuck rubberbanding - couldn’t do anything).

4th horse related lag death since game release.

This instance was immediately after 1.1.2 implementation.

RIP @Lvl 66 OtZo bear druid.

1 Like

Your build looked neither invincible or strong.

However, I sympathize with the death. I wish Blizzard would announce taking servers offline so things like this wouldn’t happen.

I have seen too many topics of people being killed by impromptu patches and updates. I don’t know where/if these updates get announced ahead of time but they have to be because otherwise it’s just unacceptable for servers to suddenly poof (on top of our usual suite of connection issues).

https://youtu.be/_dBZgv7rHas

I clipped that yesterday, in case someone thinks the build didnt work.
Its more the fact that I chose to continue that dungeon with wraiths and such with a super low attack speed so thorns doesn’t work as well compared to lets say a demon dungeon we’re i run past and everything melts.

Completely unacceptable. No matter how sh!tty your build is. The fact that no notification is given about an update and it ends up killing players is beyond stupid.

1 Like

People need to turn off auto update in battlenet app. Same thing happens within Steam too, if you allow it to happen.

I agree with this, playing hardcore and always 2-3 shots dead is not a way to do it. A combination that could kill your is a volcanic explosion together with wrath nukes and you would be done. However, network dropping out this way resulting in your death is really not acceptable. I play HC, I can relate

You did VS Butcher at within 3 level of you. You are not suffering the diminishing return. Monsters that is higher than 3 levels than you, and you will suffer more damages while dealing less damage. In the clip you died, they were 11+ level on you

Wow… Can’t believe I never thought to do that / knew I could. Well then… derp. Good advice.

Idk how to explain it further but noone of that would have killed me, i could tank waves of exploding demons and my health wouldnt budge.

Yes, it would, otherwise you can be level 50 and do NM100 without budging