Many players have recently dealt with a new Among Us error, which brings up a message that says "The game options received were from an old version of Among Us".
What does this error mean, and how can you solve it?
Among Us Error
Despite only being developed by two people with a massive audience, there have been very few Among Us errors over its lifetime.
Most players only ran into problems before servers were expanded to cover the massive playerbase.
But after the most recent Among Us update, a new error has cropped up.
This error prevents lobbies from starting in Among Us, which can certainly ruin a session. Worse, it effects players on PC, Android, and iOS.
Let's go over what the error means, and how to solve it.
Old Version of Among Us
This new Among Us error brings up the message - "The game options received were from an old version of Among Us".
So what does this error mean for your Among Us game?
This error has only shown up after the most recent Among Us update improved the game's antihack software.
Because of this, many players speculate this error could come up in lobbies where players are being flagged by the antihack software.
If this isn't the case, it's simply a new bug after the update, and hopefully one that gets fixed soon.
Among Us Beta
Another theory is that this bug is in part because of the Among Us beta.
The Among Us beta has become quite popular for testing new changes coming to the game. It was also used extensively for recent Among Us tournaments.
With the increased popularity of the Among Us beta, this could be part of the problem for the new Among Us error. Especially with players switching between the two, and even playing games with players using and not using the beta.
There's no permanent solution for the old version Among Us error, but we know it can be brute forced.
Simply closing and reopening your game several times seems to eventually work, even if the error has come up multiple times in a row for you.
This also checks for updates in-between which will help if one is available.
For now, this is all players can do until Innersloth addresses the new issue, and doesn't stop the error from happening again in the future.