Resplendent Spark - Uber lilith

Was this just something temporary or was she suppose to drop a spark on the first kill every season going forward? Cause i killed her on T2 a few min ago and no spark. She isn’t in the season journey so would make some sense i guess, but still expected her to reward one.

Same issue for me. Killed her on T1 just some minutes ago and no spark. Others in Trade Chat reporting same issue…

I killed her three times on T1. This is a bug and will be fixed with the new patch

Do you have any confirmation from Blizzard that it is a known bug?

same issue here… didnt get a spark for killing the first tormented boss either.

same here no spark blizzard really failed us here i hop they fix this asap

Just killed Lilith in T1 (i.e., for the first time while still having the purple quest to kill her) and did not get a resplendent spark. Pretty egregious.

-This is even after the 2.0.3 patch

1 Like

It did not get it either when I killed her on T3. The purple quest completed when I entered the map but I did not get anything.

No spark either in T4. Hope Blizz fix this

No Resplendent Spark here either, for the second/third time.
I only checked my inventory after I killed her first on my own in Season 6 and I was confused, when I’ve only found 3, because I could have sworn that I already had 3 the day before. Then I helped a friend, killing her, he got the Resplendent Spark, I didn’t, but I didn’t expect to get one. Now I killed her on my second character in Season 6 and I checked before AND after the fight: nope, no change, I’m definitely stuck on 3 Sparks.
I hope Blizzard monitors their forums, because I haven’t found any other way to report this error.
BTW: According to an article in WOWHEAD (Uber Lilith Resplendent Spark Bug Fix Incoming - Diablo 4 Vessel of Hatred - Wowhead News).-,Blizzard%20has%20confirmed%20that%20players%20not%20receiving%20a%20Resplendent%20Spark,s%20are%20even%20more%20scarce.), the bug should have been dealt with in Version 2.0.3 but we are currently on 2.0.4.59390 and the bug obviously still persists.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.