Abiotic Factor Crossplay Server Not Visible

Match this symptom

The server is running and one platform can find or join it, while another supported platform group sees no listing or cannot connect.

The answer first

Preserve the launch command, then check -PlatformLimited before changing the world or reinstalling. Omit that argument for the current all-platform crossplay path; PC means Steam only, Xbox includes Xbox and Windows Store, and Playstation is its own group. Then verify UDP 7777 and 27015.

Gone Wrong Servers connection setup used to isolate Abiotic Factor platform discovery and UDP reachability — Representative Gone Wrong Servers screen. Router and game screens vary by version; follow the written checks rather than matching button placement.

Record which platform actually works

1Save the current launch arguments and startup log before editing anything.
2Write down whether Steam, Xbox, Windows Store, and PlayStation tests see the listing, direct-connect, or fail.
3Confirm each client and the server are on current compatible builds.
4Back up Saved/SaveGames/Server before a maintenance restart even though the diagnosis should not require world changes.

Decode -PlatformLimited exactly

No -PlatformLimited argument: current all-platform crossplay mode.
-PlatformLimited=PC: Steam clients only.
-PlatformLimited=Xbox: Xbox and Windows Store clients.
-PlatformLimited=Playstation: PlayStation clients.

Verify game and query traffic

The developer quickstart uses UDP 7777 for gameplay and UDP 27015 for Steam query/listing. Match the configured -PORT and -QueryPort values in Windows Firewall and router forwarding. A fixed LAN address prevents a correct rule from drifting to another PC.

Use a true outside network for WAN testing.
Remove -LANOnly from an Internet server; its local discovery path includes port 14001.
Remove -UseLocalIPs if it causes the server to advertise or bind a private-only address.
Do not invent an RCON rule; no official RCON service is documented in the reviewed server wiki.

Restart with one intentional audience

1Stop normally and change only the platform limiter or only one network value at a time.
2Start, wait for listing readiness, and retest one client from every intended platform group.
3If all platforms fail, return to process/UDP reachability; if only one excluded group fails, return to the limiter/build matrix.

Keep administration cross-platform too

A SteamID administrator list cannot identify every console user. Configure a strong -AdminPassword and use the in-game Player Management flow for authorized cross-platform administrators; protect that password from public scripts and screenshots.

Use the pattern of visibility as evidence

If Steam can see the server while Xbox and Windows Store cannot, -PlatformLimited=PC is a better first hypothesis than a damaged save. If Xbox and Windows Store both work while PlayStation does not, inspect the Xbox limiter and platform build before changing UDP rules. When every platform fails from outside but a LAN test works, the shared public firewall, NAT, query, or CGNAT path deserves attention instead of any one storefront.

Record the active limiter, -PORT, -QueryPort, public test network, and one result per platform after each restart. Do not use a cached favorite entry as proof of current discovery; search or connect through the current supported flow. This small matrix lets the platform argument and network path be tested independently and prevents world/config files from being rewritten during a listing-only incident.