You may remember that Apex Legends suffered a large-scale hack over the weekend. The battle royale was suddenly inundated with in-game messaging to promote a website petitioning Respawn to fix the original Titanfall. And now the developers who had to work to fix that hack have openly said that they have been trying to help Titanfall and its community - but these players' actions made a bad situation even worse.
Respawn Entertainment's director of communications, Ryan K. Rigney, decided to respond publicly on Twitter, expressing his own frustration with the way this situation has unfolded. Retweeting a TheGamer article, the developer agreed with the headline: "Congrats Titanfall Hackers, You Made A Bunch Of Devs Work On A Sunday".
Here are the best Apex Legends wins and fails...
Rigney explained on Twitter: "Nobody wants to hear devs complain when DDoS attacks are still a problem we haven't solved. But this article is right. I was holding my newborn nephew when I found out about the Apex hack. Had to hand him back, go work, and miss out on a day with family."
The communications director goes on to stress that the team at Respawn already knew about the DDoS attacks on the game and were trying their best to solve them. He says: "The team has never stopped working on DDoS solutions, and anti-cheat is just a never-ending war of whack-a-mole. On the DDoS front, we WILL solve this. When we do, I promise you it won't be because hackers 'made us aware' by ruining a holiday. They achieved nothing of value."
During this Twitter thread, however, he mentions that this attack was linked to the SaveTitanfall.com awareness campaign, which the site has now denied. Though the site's URL was plastered all over Apex Legends, if you go to the website now, it clearly states: "IMPORTANT MESSAGE: This website, nor the Discord servers listed below, are in no way associated with the recent Apex Legends hack."
It's not clear then, who the hackers were and we doubt we'll ever find out - they just seem interested in seeing Titanfall servers become more stable. Making a developer's life harder, however, isn't going to be the solution to that especially when they've already acknowledged the issue at hand.
Chosen for YouChosen for You
Most Read StoriesMost Read