Video:
https://youtu.be/2J4Dh-njsLg?si=PQ3cA1j5A_57q7ZD
Not sure what exactly went on here. I know there’s certain physics interactions that can just cause Tree to blow up but this doesn’t seem like one of them?
The only thing I can think is that it was a little too far off the payload? Any insight would be great, was a… interesting moment for sure.
Yeah that’s the ol’ Payload being a douche lol. Anything it contacts it destroys. I’ve seen many of my Junkrat traps about to snare the best enemy player-only for the payload to destroy it by going over it FeelsBadMan
2 Likes
I think it definitely has something to do with the payload, but I have put tree on, and in front of, payload constantly since Lifeweaver’s release and have never ran in to this issue, even on other Blizzard World games (and literally later in that game lol).
Not sure if it was just the positioning or if there was some other element or what
Could quite be possibly be the positioning yeah if that was the first time it’s happened. On the plus side, made you more aware for future positioning.
What you could do is try to replicate it on a custom game vs AI and see if it’s indeed a positioning issue. If it doesn’t happen again it could be something else.
Just wish it would leave my traps alone lol
1 Like
It may be that you must have the center axis of this deployable squarely on a surface. This looks like it was just off the payload’s edge, creating the tree in the air, as far as the game was concerned, and it set off an error trap.