Sea of Thieves: How to Fix the KiwiBeard Error
Sea of Thieves is set for its official release on March 20th, but you may be one of the lucky few that gets to playtest the game or participate in the current Sea of Thieves scale test.
If you've been playing Sea of Thieves as part of their scale test to test stress against their online servers recently, chances are that you've encountered some strange errors behind some pretty funny names. These errors, called ThingBeard errors, are most common on the Xbox One console, but some can appear on the PC client.
We're beginning to see some of the issues we knew we'd experience in the Scale Test. This is part of the process! We appreciate patience and you can learn more about why we're running this test here: https://t.co/5pFd8cgj7C— Sea of Thieves (@SeaOfThieves) February 17, 2018
One of the most common errors that people are running into is one called KiwiBeard.
What Is the Sea of Thieves KiwiBeard Error?
The KiwiBeard error is caused by any of the following conditions:
- Sea of Thieves is not running a play session when you tried to log in, so you can't play right now.
- You have more than one Gamertag signed in to your console. Sign all other accounts out of the console, and only launch the game with the account that has been invited to play.
- You have not been invited to play the Sea of Thieves Technical Alpha. If you're registered as an Insider, you may be invited in the future.
Run down this list of possibilities and you should come across the one that's causing the game to throw this error. If you don't meet any of these error conditions, give the game a few hours to solve these online issues itself and give it another try. If you're still having trouble, send a message in to Sea of Thieves support. If you're signed into one Gamertag and you've been invited to their Technical Alpha, there's a very good chance that the servers are down.
What Are the Other ThingBeard Errors?
Although KiwiBeard has appeared as one of the most common error messages when launching Sea of Thieves, there are plenty more. Here's a quick rundown:
- AshBeard: You must be signed into Xbox Live to play Sea of Thieves.
- AvocadoBeard: When playing on an Xbox One console, you need an Xbox Live Gold membership to play online.
- AlabasterBeard, AlmondBeard, and CyanBeard: Your connection to Xbox Live and/or the Sea of Thieves services has been disrupted or lost.
- BeigeBeard: Your game client is out of date and you need to check for updates.
- DaffodilBeard: Something has happened on Sea of Thieves' side of things, and you'll need to wait for them to fix the issue.
- FluffyBeard: Either the servers are down for an update, or a playtest is not currently running at this time.
- LavenderBeard: This can be caused by antivirus/firewall settings or misconfigured proxy servers and other network management settings.
- LazyBeard: You have been removed from the active game session due to lack of activity.
There's also BronzeBeard and CinnamonBeard, two other very common errors you may experience. Although I haven't found any information on what it is that triggers these errors, they're easily fixed by pressing the Guide button, quitting Sea of Thieves, and then relaunching it.
If you come across any other ThingBeard errors, drop me a comment below and let me know, and I can try to help walk you through it. Be advised that Sea of Thieves isn't in a release state yet, so errors like this should be expected and very likely will occur at some point during your playtest of the game.
Looking for more Sea of Thieves content? Check out these: