JavaScript is required to use Bungie.net

Service Alert
We are actively investigating issues impacting players' ability to sign in to Destiny 2. Until resolved, players may experience disconnects or be unable to sign in. Please stay tuned to @BungieHelp for updates.

Help

Help us help you.
3/25/2019 6:49:40 PM
1

Gambit Primeval Bug? Still had health but game declared it dead

Please check out the attached video. In regular Gambit last night, I invaded and killed two enemies to heal up the Primeval. While working on taking down the third, they unleashed their Hunter's super. From my perspective, it looks like I killed him before the super did damage and thus with that amount of health regained the Primeval shouldn't have been dead yet. So... 1.) Based on numbers, can a Hunter one-hit kill a Primeval from that amount of health with their super? 2.) Which should have happened first? Primeval being healed or killed, based on the video? 3.) Is this a bug in which the Primeval only appeared to be healed but was actually dead first? If so, can we please get a fix to prevent the health bar from going back up after it's dead? Thanks! -Sol Knightt

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
  • what it looks like happened was you killed the hunter after he launched super, but close enough to where there could be a difference due to lag/internet connection speeds. That is why you see the health bar go to zero then back up then down again. Basically, on your screen you killed him before/as he launched, on his screen it was after so the game decided the match.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon