2

Sometimes while playing Deathmatch, I'll see a prompt telling me that I've gotten credit for eliminating my own Steel Trap or Concussion Mine while playing as Junkrat.

Eliminating own Junkrat trap

I've had this happen to me 2 or 3 times, but only while playing as Junkrat in Deathmatch mode. I haven't been able to figure out how this happened, or how to prevent it.

This doesn't seem to be a bug with Junkrat's grenade launcher. When I tried firing directly at the trap, the grenades didn't do any damage.

How is it possible to eliminate my own Steel Trap as Junkrat?

2
  • 1
    Sounds like some sort of bug.
    – Powerlord
    Commented Sep 6, 2017 at 3:44
  • 1
    Is it possible that JeffTheTree was currently stuck in your trap when you killed him? I.e. when a trap closes, it "belongs" to whoever is caught by the trap, but the name of the trap is fixed once it's laid down (thus carrying your name, even though the ownership shifted). This makes sense from a game building perspective, because the trap and the trapped can be considered as a single game object for the duration of the trap.
    – Flater
    Commented Sep 6, 2017 at 7:53

1 Answer 1

7

It's a bug currently present with deployables in Free-For-All Deathmatch. Since there are no teams, a player's own deployables such as Junkrat's trap and Orisa's shield sometimes behave oddly, such as Junkrat's trap being destroyed by his own Concussion Mine and Orisa's shield blocking the pull effect from her alternate fire. There's nothing you can do except wait for a patch to fix it.

This link to Overwatch Patch notes for 1.15 confirms the following bug in FFA;

  • Junkrat can destroy his own Steel Trap with a Concussion Mine
5
  • 2
    Has Blizzard acknowledged this anywhere? At the moment, your answer seems like speculation. Commented Sep 6, 2017 at 12:47
  • I'm requesting some official source that states this is a bug. Otherwise, this is just your opinion. Commented Sep 6, 2017 at 12:51
  • 1
    ...no, having your own deployables work against you is not proper behaviour and definitely a bug. Official source will be patch notes once it's fixed. It's not an opinion. Commented Sep 6, 2017 at 12:52
  • 1
    No, it certainly isn't proper behavior, I'm not disagreeing there. But at best, your answer is just speculation about being a bug without some sort of official backing from the developers. Some sort of acknowledgment that it's a bug, anything. That doesn't seem like a mountainous request. Commented Sep 6, 2017 at 12:56
  • 3
    If this didn't exist my answer would be just as valid. Commented Sep 6, 2017 at 12:58

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .