The Prestige version of the Leviathan Raid in Destiny 2 was recently beaten shortly after it went live, but that accomplishment has definitely been dampened by learning that the victorious Clan Redeem used an exploit to finish the Raid.
Videos by ComicBook.com
Clan Redeem was the first team to beat the Leviathan Prestige Raid, and it didn’t take long for Bungie to hop in and acknowledge the group of players. Bungie tweeted a congratulatory message directed at Clan Redeem for accomplishing the Raid so quickly, a moment that was quickly spoiled by a response that pointed out the use of the exploit.
“im coil glitching” pic.twitter.com/CnA0XT7PfL
โ Drew Anderson (@imshoobie) October 18, 2017
In the clip shown above, it appears that the players are using an exploit known as a “Coil glitch,” a move that allows for instant replenishment of a power weapon’s ammo. If seeing it on-screen wasn’t enough, you can even hear the players explicitly saying that they’re using the Coil exploit. Another clip shows them mentioning the exploit again as the “dubious glitch” and performing the same actions.
Destiny 2 Players Aren’t Happy
When watchful viewers started picking up on the use of the exploit by Clan Redeem, Destiny 2 players had an understandably angry reaction to what’s essentially cheating the Raid, something that was made worse by Bungie acknowledging the team without catching the exploit.
Thought, exploits weren’t allowed for worlds 1st? pic.twitter.com/UTSgDqxQoe
โ ThaddeusPrime (@thaddeusPrime) October 18, 2017
While plenty of players seem to simply be disappointed that the race to beat the Leviathan Prestige Raid first was tarnished by an exploit, others are calling for more drastic actions. One Redditorย said that the Clan should be disqualified from their first-place status and hoped that Bungieย has a way of detecting whether other teams are using the exploit or not.
Bungie hasn’t followed up on their initial tweet where they congratulated Clan Redeem, but they might not considering it involves a known exploit that hasn’t been fixed yet.








