In the shooter Apex Legends (PC, PS4, Xbox One) a new bug has emerged: Some players who have reached the maximum level of 500 cannot log into their account anymore. They receive the error message: “Server shutting down – Internal Server Error”.
This is the situation: In the first months, players could only level up to 100 in Apex Legends. A major update changed that and made it possible to reach level 500.
Players had the opportunity to continue grinding and grab more rewards. Level badges are offered as recognition, so that those who spend so much time in Apex Legends have something to show for it – along with hopefully many kills that can be seen in the Apex Tracker.
Cosmetic rewards are tied to leveling up in Apex Legends; players do not gain gameplay advantages by achieving a higher level in the shooter.
With level 500, some can no longer play Apex Legends
This is the problem now: In the EA forum, a player said on Monday: When reaching level 500, you get the error message “Server Shutting down – Internal Server error” and cannot log into your account, no matter what you do.
In the discussion, other users also report that they are level 500 and have the same problems. They cannot log into the account at the maximum level. They can only play Apex Legends if they use a different account.
A player says he can bypass the bug by constantly logging in, at least then he can play a match, but afterward he faces the problem again.
How is the discussion going? The discussion in the forum started on Monday. EA community managers have also responded and tried to narrow down and understand the problem through inquiries.
Apparently, the bug is under investigation, but there have been no updates in recent days.
The situation is escalating. Affected players say: Hey, we are your most valuable players, we have spent the most time in Apex Legends, take care of us and not just new players.
Right now, as a new event is starting on January 14, the excitement for Apex Legends is high among veterans.
Players are now hoping for the update for the event
This is the status: The last update from the community manager, EA_David, on Friday was: “Hopefully the bug can be fixed on January 14 or sooner, but there is no information on when exactly this fix will come.”
