You press join, the screen goes black, and nothing else happens. This is the hardest join failure to diagnose because there is no error to search for. The good news is that the game labels every stage of a join, so the first question is not "why is it broken" but whether there is any text on that screen at all.
Look closely before you do anything else. A join that is working but slow shows a stage label, sometimes small and dim against a dark background. A join that has actually failed shows nothing, or drops you back to the menu. Those are two different problems with two different fix lists.
These are the loading stages the game prints, taken from the strings shipped with V3.2.0. Find the one you are stuck on.
| What the screen says | What is happening | What to check |
|---|---|---|
Waiting for server... | The client has connected and is waiting for the server to answer the handshake. | The server is up but busy, still generating or still loading a world. A server that has not finished loading cannot accept a join. |
Receiving and loading configs... | The server is sending its configuration and mod data to the client. | This is the stage that hangs when the server has mods the client cannot accept. Full guide. |
Waiting for server to send the world... | The client has asked for the world and the server has not started sending it. | Server upload bandwidth, or a server still writing files. Give it a minute before deciding it is stuck. |
Downloading World: N% | The world is transferring to the client. On a first join this is the longest stage by a wide margin. | Nothing is wrong. A 10K or 16K world on a slow uplink takes minutes. The percentage moves, sometimes slowly. If it truly stalls. |
Downloading Localization or Downloading Sign Data... | Smaller transfers that follow the world. | Same causes as the world download, but these finish quickly. |
Initializing world... | The client is building the world locally: terrain, biomes, blocks, prefabs, splatmaps, environment. | This is local CPU and storage work. On a console with little free space it can crawl or fail. See the storage section below. |
Creating player... then Starting game... | The last steps before you are in. | If it hangs here the world arrived but something in your player save is wrong. Try joining with the same account from a different platform to confirm. |
The practical rule: a first join to a large world is slow, and it is slow exactly once. If the same player joins the same world again later and the world has not changed, the transfer stage is skipped. So "the first person waited eight minutes and everyone since joins instantly" is normal behaviour, not a bug.
If you get any text at all, the game has told you the cause. These are the messages it can show, quoted from the same shipped strings, with what each one actually means.
| Message | Cause |
|---|---|
| Too many players are permitted on the server for Crossplay. Allowed maximum: N | The server's slot count is above the crossplay limit. This is the single most common reason a console player cannot join a server that PC players are already playing on. |
| Server does not have EAC enabled. | Anti-cheat is off on the server. Crossplay requires it. Overhaul mods require it off, so an overhaul server cannot take console players at all. |
| Remote data validation failed. Modified files detected. | The client has files the server does not expect, or the reverse. Any client-visible mod will do this. |
| Game Version Mismatch: you have 'X' and server has 'Y' | Different builds. The build number after the b matters, not just the version. How to line them up. |
| Crossplay is not allowed. | Crossplay is switched off on the server. |
| Crossplay is not allowed between X and Y. | That specific platform pair is not permitted. |
| Crossplay is temporarily disabled on this platform. | Platform side, not yours. Nothing on the server will fix it. |
| Crossplay multiplayer sessions are not permitted at this time. | Same category: the platform is refusing, not the server. |
| Checking your {platform} status timed out. | The platform ban check did not answer. Usually transient. Retry. |
| This server only allows users from the friends list to join. | Server visibility is set to friends only. |
| You are not permitted to join this session. This session may be set as Invite Only | Session visibility, not a network fault. |
| Connection rejected by the server | The server refused at the network layer. Check the password, the slot count and whether the server is full. |
| Could not connect directly, no IP found | The client resolved the session but got no address for it. Common on a server reachable only through the relay. |
| Network Timeout, Connection Lost, Can not connect to server | Ordinary network faults. Start here, then check NAT type. |
A console player who gets a blank screen or is bounced straight back to the menu, while PC players join the same server fine, is nearly always hitting a server configuration that excludes console clients. Four things must all be true at once, and three of them are silent when they are wrong.
ServerAllowCrossplay must be true. It is false by default, so a stock server is not a crossplay server. There is no property called CrossplayEnabled; if a guide told you to set that, it was wrong.IgnoreEOSSanctions must stay false. Setting it true removes the server from console search entirely, with no error anywhere.ServerMaxPlayerCount must be at the default of 8 or lower. Above that the server stops being a crossplay server, and a joiner is told the player limit was exceeded.EACEnabled must be on. Console clients will not join a server without anti-cheat.All four are in serverconfig.xml and all four survived the V3.0 migration, unlike the gameplay properties. The full crossplay setup guide covers the rest, and the serverconfig.xml reference lists every property a V3.2 server still reads.
Downloading World or Initializing world, and it does not always say so. Clear space before blaming the server.V3.1.0 shipped with a bug in game invites: players on both consoles were stuck on "waiting to receive invitation" or told the content could not be loaded. The developers acknowledged it and shipped a hotfix. If you are still on an early V3.1 build, update before troubleshooting anything else, because you may be chasing a fault that was already fixed. Current branches and how to match them.