Install Patch 1.2, reset the browser filters and let the list refresh before retrying. Hotfix 1 made the browser refresh more often, hid full servers by default and prioritized low-ping servers with 80 or fewer players. Patch 1.2 then fixed VIP reservations incorrectly affecting active server and queue slots. A VIP message on one community server can still reflect that server owner's rules, so compare an official server and another community server before assuming the whole browser is broken.
Match the message to the likely cause
| What you see | What to check first |
|---|---|
| The list shows space, but joining says full | Wait for the next refresh. The displayed count may have changed while you selected the server. |
| No full servers appear | Hotfix 1 hides them by default. Change the Full Servers filter if you want to see them. |
| Reserved for VIP or queue-slot error | Update to Patch 1.2, then test another server. Community server owners still control their own VIP access. |
| The server you want is missing | Clear region, ping, full-server and crossplay filters, then wait for a complete refresh. |
| Every server disconnects or crashes | This is broader than a browser filter. Record the error, platform, region and server name for official support. |
What Hotfix 1 changed
Hotfix 1 is live on all platforms. Its official notes say the server browser now refreshes more frequently, hides full servers by default and prioritizes low-ping servers with 80 or fewer players. Team17 also said it added servers and increased capacity while investigating launch congestion.
The browser can still change between the moment a row is displayed and the moment you join. A server that filled during that interval can reject the connection even though the old row showed space.
What Patch 1.2 fixed about VIP slots
Patch 1.2 is live on all platforms and its official changelog includes a specific server fix: VIP reservations should no longer incorrectly affect active server slots and queue slots. If the same message appeared before updating, install the patch and retest rather than relying on an old result.
This fix does not remove VIP systems from community servers. Those servers can reserve access for supporters or administrators under their own published rules. If only one community server rejects you while other servers work, the evidence points to that server or its current capacity rather than a site-wide outage. That is a diagnosis, not proof of the server owner's exact configuration.
Safe troubleshooting order
- Confirm the game is current. Patch 1.2 contains the VIP active-slot and queue-slot correction.
- Clear restrictive filters. Temporarily reset region, ping, population and crossplay filters so a saved setting cannot hide the result.
- Wait for a full refresh. Do not repeatedly click a population number that may be stale.
- Choose a server below capacity. Team17's launch-day advice favored servers with 50 or fewer players during the initial rush; Hotfix 1 now prioritizes low-ping servers at 80 players or below. The former was congestion guidance, not a permanent requirement.
- Compare server types. Try one official server and one different community server in the same region.
- Separate queue problems from crashes. A crash, timeout or anti-cheat error needs its own report and should not be described only as a VIP-slot problem.
If a server is missing
Start with the browser settings. Hotfix 1 changed the default visibility of full servers, while platform or crossplay restrictions can exclude servers that cannot accept the current player. Reset filters, allow the list to refresh and search for the exact server name again.
If a named community server remains absent, check that server's own announcement channel for maintenance or a name change. A community post can explain that server's local status, but it is not evidence that the entire game service is down.
If joining still fails everywhere
- Record the platform, current game version and region.
- Copy the exact error text rather than paraphrasing it.
- List two or three server names and whether they were official or community-run.
- Note whether the failure occurs before the queue, inside the queue or while loading the map.
- Send the report through Team17's official Help Centre if the problem affects multiple servers after updating and resetting filters.
Bottom line
Hotfix 1 improved freshness and default sorting, and Patch 1.2 corrected the documented VIP slot accounting bug. Those changes make the first response simple: update, reset filters, refresh and compare another server. A failure limited to one community server may be its current capacity or VIP policy; failure across several server types deserves a precise official support report.