After first adds Lilith just keeps spawning waves. It is always like that for my bone spear necromancer. Lilith just doesn’t let me reach phase 2. Here is the video link: Diablo IV - Lilith infinite waves bug - YouTube.
Happens to me too… its when you do enough dmg right as first adds spawn that would otherwise make the 2nd add type spawn… broken.
and I hate you for being able to avoid the waves like that. my smooth brain cant even do 1 wave half as smooth as that.
Either do MORE dmg before adds spawn… or do less and do another round to get the other adds.
this game sucks lol, I didn’t understand why it kept doing this either, of course the answer is to do less or more damage, nothing can just work like it’s supposed to in this game…
This is so annoying as it preventing me from completing the fight.
thx for reporting this. i am experiencing this on console (PS5), too. i thought i am just way too stupid to do the fight, now i learned why i cant reach stage 2 with my BS necro… thx
i cant find any workaround until now. neither doing more or less dmg during the 2adds phase does any difference. its annoying and frustrating ![]()
actually, the fight would be quite doable with the BS necro. i play season and have barber heart equipped. i can shred her down easily to <50% in the first 20s of the fight. from then, she starts bugging around… no progress possible.
Am running into this, as well. Kind of ridiculous. It needs to be fixed. To be fair, I ran into it on purpose a few times, to practice waves. Really helped, honestly. I was able to get past 11 waves in a row, on my best try. Not too shabby. I’m still bad.
i captured a video of this bug where i dodged 10 waves in a row before the next one got me.
i captured a video of this bug on ps5 where i encountered 11 waves in a row:
Diablo 4 Uber Lilith S1 infinite waves bug PS5 (BS Necro barber heart)
1 month later and still bugged … ![]()
![]()
![]()
I’m gonna bump this one, plz fix it blizzard.
Still bugged don’t worry
Still getting same bug today 9/8/2024. Thanks for the comments at least explaining its bad AI phase shifting issue.