Apex Legends

Ranked Progress Glitch Officially Under Review, Apex Legends Developer Says

Chad Grenier, Design Director for Apex Legends, has advised players that the development team is aware of a recent Ranked progress glitch.
Chad Grenier, Design Director for Apex Legends, has advised players that the development team is aware of a recent Ranked progress glitch. / Respawn Entertainment

Chad Grenier, Design Director for Apex Legends, has advised players that the development team is aware of a recent Ranked progress glitch.

This might be one of the most devastating bugs on the player-side in Apex Legends. Recently, some players have been stricken with a glitch that refuses to save any progress they make while they play Ranked mode. It doesn't matter how far they get, how many matches they play, or what legends they pick—the game simply does not recognize the fact they've moved up.

Ranked Progress Glitch Officially Under Review

Grenier responded to a tweet posted by an affected player on Saturday, Aug. 14—though some report encouraging the bug as earlier that week. The user, @Guild_Gamer, posted a short clip showing the glitch in full form. They were able to show the difference between their Ranked progress upon leaving a match to their unchanged position from before the session.

"Love it when my progress doesn’t save." They wrote, tagging both the verified Apex Legends and Respawn Entertainment accounts.

Eight hours later, @Guild_Gamer posted again that the glitch was still active, quote tweeting their original post with further explanation: "If I switch off or change server everything gets reset back to what it was yesterday." They then tagged Grenier and Apex Legends new outlet, @alphaINTEL.

This seemed to do the trick. Grenier replied to the tweet within minutes to assure @Guild_Gamer and their audience that the development team was on the case.

"Yikes. I’ll pass along to the appropriate people on the team to take a look," he wrote.

However, at the time of writing, there still appears to be no active fix for the glitch.