{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/17/2025 5:00:58 PM
8
GM Conquest Whisper - Blights insta killing / Melting your health
Tried to do the GM conquest so I can rank up since I need to do both of them
I decided to try the Whisper one
First blight no problem
Finish jumping through the entire map so you get to where enemies spawn again
The second I step into a blight, it burns my health away in less than a second.
No enemies shooting, just entering the blight sphere melts all my health away.
Even with all enemies dead, just entering the sphere containing the blight kills me.
How am I supposed to beat it if I NEED to destroy them.
The timer is also unreasonably short, but that's the least of my worries.
-
1 ReplyJump on top of the blight and shoot down
-
So glad I wasn’t the only one this happened too. Wondering how long before a patch is issued though
-
Small update. It's not just the conquest ones. It's all Blights. The dreaming city ones do the same thing, there are very few spots where you can somewhat survive, but it will just burn your health if you misstep for even a frame.
-
can confirm this is still broken. as of 9/19/2025 9:30pm /sigh
-
3 RepliesI have just gotten to 390 power and can confirm this bug is still active. In no iteration of the game have blights ever killed that fast. GM, contest mode, etc. Even in a Well of Radiance with max/200 health, insta-death. I even scraped my elbow on the edge of a blight and was instantly dead. Fix it, Bungie.
-
Jump on the Blights, on the orb in the middle and shoot down to destroy it. Timing to jump off on time is hard though.
-
Edited by ABADDON_WOLFFE: 9/17/2025 10:40:02 PMYup the ones of hypernet are the same. Specially the blight projectiles. They just have to grace one of your guardians toe to insta kill. I could have sworn they said it was fixed. 🤔
-
I thought it was just a specific feature of the conquest when I ran it last week. Didn’t know it was a bug.
