Dolphin's built-in Netplay plays any GameCube game with a local multiplayer mode online, without the old Nintendo Wi-Fi Connection or a Broadband Adapter. Netplay exists only in the desktop version of Dolphin, not on Android (Dolphin Netplay Guide).
Use your own legally obtained copy of the game. ROM does not condone illegally downloading ROMs.
What you need
- The same Dolphin version on every computer - the latest release from dolphin-emu.org. Dolphin refuses mismatched versions to prevent desyncs.
- Every player needs their own copy of the game, and the region and revision of all copies must match - identical dumps are strongly recommended, and the game must be in each player's Dolphin game list.
- A wired connection is recommended: bandwidth needs are light, but ping decides how much input latency the session needs.
Host a session
- In Dolphin, open Tools > Start Netplay Session and choose to host.
- Pick the game, set your player name, and choose how to host: Traversal Server works without port forwarding on most networks; Direct Connect shares your IP address and port instead.
- Share the traversal code (or your IP and port) with the other players.
- In the netplay window, assign controller ports, set the buffer (about 1 pad buffer per 15 ms of latency per player is the guide's rule of thumb), then start the game.
Join a session
- Open Tools > Start Netplay Session and choose to join.
- Enter the host's traversal code, or their IP address and port for Direct Connect, and set your player name.
- Wait in the lobby - the host starts the game for everyone.
Controllers and spectators
- With one player per computer, Dolphin maps each computer's first configured GameCube controller port automatically - nobody needs to configure the port matching their player number.
- The host can give one computer several controller ports for multiple local players, and anyone left out of the controller slots joins as a spectator without affecting latency.
Troubleshooting
- Cannot connect: a Strict NAT on the host or a joining player can block the traversal server - the host then has to port forward and everyone uses Direct Connect. Also check that the firewall allows Dolphin, and that everyone runs the same Dolphin version.
- Players see different things (a desync): use the netplay window's Checksum tab to confirm every player's game dump matches, and try Strict Settings Sync if a hidden setting difference is suspected.
- If nothing here applies: the Netplay Server Browser (Dolphin 5.0-8478 or newer) lists public sessions - if sessions appear there, Dolphin's infrastructure is reachable and the problem is likely local; an empty list on its own does not confirm an outage.