Destiny 2 Bug Allows Friendly Fire in PvE Gameplay

There’s an intriguing Destiny 2 bug currently circulating among Guardians that enables players to turn on each other in PvE activities. This glitch allows players to melee teammates and even kill them while they are part of the same fireteam.

Destiny 2 is a complex game with numerous components. This includes the intricate abilities, diverse weapon loadouts, various game modes, and a vast array of exotics that players can mix and match to create their builds.

Consequently, Bungie continually releases patches to maintain game balance, an increasingly challenging task with the continuous flow of new content. However, the introduction of new elements can sometimes lead to unexpected bugs.

A new glitch has recently been discovered by players, enabling them to attack their teammates even outside of PvP activities.

This bug permits Guardians to melee each other and inflict damage on allies, mimicking the mechanics of PvP. The twist is that this glitch was discovered within the Shattered Throne dungeon, which is a PvE activity that typically doesn’t include player-on-player combat.

In one instance shared by a Guardian, they were attacked by an invisible player. This usual occurs when a Guardian’s connection is slow, causing their character to take time to load.

In this state, they could deal melee damage and eliminate their teammate.

The affected teammate also provided their perspective; they appeared completely visible and were able to perform melee attacks that inflicted damage.

The two Guardians created a video explaining the mechanics of the bug. By using Siphons on their helmet and quickly swapping them, they generated a significant number of orbs, which caused server lag and resulted in a hilarious chain of events where one Guardian perished and upon respawning, gained the ability to damage their teammate.

This bug necessitates specific conditions for it to activate, but Destiny 2 players enjoy exploiting such glitches, so it’s likely we will see more instances of this bug unless Bungie intervenes to resolve it.

Source

Leave a Reply

Your email address will not be published. Required fields are marked *