Last night was…a moment in Destiny 2. One of those “you had to be there” things that Bungie is talking about usually in regard to sunset content, but really, it’s the goofiest things that are the most fun.
For a few hours last night, there was a “Khepri’s Horn” meta in Iron Banner. Not because it’s particularly good, even after it’s recent buff to give it scorch stacks, but because it…totally broke Iron Banner and gave out instant wins or losses to teams.
What you would do is have a Titan with Khepri’s, the run up and cast the barricade over an uncaptured zone. For reasons no one can fully explain, once everyone was inside the previously Khepri’ed zone, it would rack up about 70 capture points instantly, triggering the game’s mercy rule and ending an entire match within about ten seconds or so. Instant wins, instant losses. Then soon enough, races to see which team could properly execute this first.
But wait, it gets funnier! Bungie soon announced that Khepri’s Horn was disabled in all activities except…Khepri’s Horn did not agree. If you were already wearing the exotic, it did not disable it, and given that loads of Iron Banner players were obviously wearing it this did not change much about the bug.
So, ultimately, Bungie had to change the entire Iron Banner mode from Control to Eruption. That’s right, Khepri’s killed an entire Iron Banner mode, which I genuinely don’t think I’ve ever seen before. I’ve seen a lot of bugs in my time that Bungie had to react to quickly, but this is easily one of the most memorable and hilarious.
During those few hours, people were able to farm full Iron Banner resets on wins or losses with games being reduced from 8-10 minutes down to ten seconds. You’d spend longer in the queue than you would in the game. Those rewards will not be taken away, but if you missed out last night (like I did, playing Diablo) you are out of luck now.
I am still unclear on A) how this was discovered in the first place and B) what exactly is going on here. I suppose someone was trying to play Khepri’s normally and just happened to use it to defend an uncaptured zone, and maybe things spiraled from there? As for what’s happening, given that this has never happened before, I might assume that it has something to do with its recent buff to apply Scorch? Maybe to uh, the Iron Banner fire in the middle? I’m just making stuff up now.
Anyway, this was hilarious. Good times.
Get the best of Forbes to your inbox with the latest insights from experts across the globe.
I’ve been writing about video games, television and movies for Forbes for over 10 years, and you may have seen my reviews on Rotten Tomatoes and Metacritic. I cover all manner of console and PC games, but if it’s about looting or shooting, I’m definitely there. If I’m watching something, it’s usually science fiction, horror or superheroic. I’m also a regular on IGN’s Fireteam Chat podcast and have published five sci-fi novels.
Read MoreRead Less