How do I set up CrossPlay?

1 — Update first

Cross-play only works if all platforms are on the same build number. Make sure you (or your host) have pulled the latest ASA dedicated-server build (AppID 2430930) before you start the instance, and tell your console players to install any pending patches. Mismatched versions are the #1 cause of “connection timed-out” errors.

2 — Forget the old -crossplay flag

Studio Wildcard removed that switch in the November 2023 SDK update. ASA now brings cross-play on by default; you only need a flag if you want to restrict a server to certain devices. Use the new syntax instead:

• PC  = Steam

• WINGDK = Windows-Store/Game Pass build

• XSX = Xbox Series consoles

• PS5 = PlayStation 5

Chain the tokens together with “+”.
Examples

PC + Xbox only -ServerPlatform=PC+XSX
Console-only PvP -ServerPlatform=XSX+PS5
Disable cross-play -ServerPlatform=PC -pconlymods

3 — Launch line template

• -NoBattlEye is currently recommended for full cross-play. BattleEye does run on PC, but consoles will refuse the connection if BE is active. (This is still “early access” behaviour; keep an eye on patch notes.)

4 — Keep your mods console-friendly

• Every mod must come from CurseForge and be flagged by its author as “cross-platform”.

• If you leave any Steam-only mod in your Game.ini list, console clients will fail to load the map.

• If you really need a PC-only mod set, launch the server with -pconlymods.

5 — Show console players how to join

1. Start the server and watch the console; ASA prints a line like
   Server: "ARK #234567" has successfully started!

2. Tell Xbox / PS5 players to open Join Ark → Unofficial → Search by Session ID and enter that 6-digit ID.

3. Remind them to tick the “Cross-Play” filter so the list isn’t restricted to console-only servers.

6 — Typical connection hiccups & quick fixes