How to Fix Can't Join Friend in Burglin' Gnomes
Fix Burglin' Gnomes friend-join failures with host checks, version matching, Steam invites, firewall rules, and LAN limits.

By: Frontline Pathfinder | Lead Content Tester, GameguideHub
Tested on Version: Current public build | Status: FIELD TESTED / PATCH SENSITIVE. Multiplayer session handling, invite behavior, and firewall prompts can change after Steam or game updates.
Fast answer: if you cannot join a friend in Burglin' Gnomes, fix the host/session path first. The current build is a Steam Windows title with online co-op; do not assume a separate LAN-only mode unless your build exposes one. Check host reachability, version match, Steam overlay, invite state, firewall permissions, and then re-host from a clean lobby. For team roles after the connection is stable, use the co-op guide.
Fast checks before changing settings
Confirm the host is reachable
The host is the first failure point. If the host is still in a run, stuck after a failed day, tabbed out during loading, or sitting in a private session state, the invite can look valid while the join attempt fails. Re-host from the lobby, wait until the host can move normally, then send a fresh Steam invite.
| Check | Correct Action | What It Rules Out |
|---|---|---|
| Host state | Host leaves the failed run, returns to lobby, and starts a fresh session. | Old session handles and stale invites. |
| Friend list | Both players appear online in Steam, not invisible/offline. | Invite routing blocked by Steam presence state. |
| Lobby timing | Join only after the host is fully loaded and not in a transition screen. | Joining during scene load or day reset. |
| Party size | Keep the test to host plus one client before adding the full group. | One broken client being mistaken for a global lobby bug. |
Check version and platform mismatch
Version mismatch is the cleanest failure to miss. Burglin' Gnomes updates through Steam, and one client can stay on an old build if Steam is open, download scheduling is paused, or a player launched before the patch finished. Close the game, force Steam to finish downloads, then relaunch every client.
| Mismatch | Fix | Field Rule |
|---|---|---|
| One player updated, one did not | Restart Steam and verify the download queue. | Everyone relaunches before the next invite. |
| Wrong platform assumption | Use Windows Steam as the baseline unless your build clearly supports another route. | No console, mobile, or non-Steam join path should be assumed. |
| Steam Cloud sync prompt | Resolve the prompt before hosting. | Do not invite from a sync conflict screen. |
| Mods or launch options | Disable nonessential launch options for the connection test. | Test stock first, then re-add changes one by one. |
Connection and Steam fixes
Steam invite and overlay checks
A lot of "Steamworks fix Burglin Gnomes" searches are really Steam client state problems. Keep it boring: enable the Steam Overlay, accept the invite from Steam chat or the overlay, and avoid mixing old invite links with fresh lobbies. If the overlay does not open, fix Steam before blaming the game.
| Symptom | Likely Cause | Fix Order |
|---|---|---|
| Invite does nothing | Steam Overlay disabled or client not focused. | Enable overlay, restart Steam, then resend invite. |
| Join starts then drops | Host changed session or client joined during load. | Re-host, wait in lobby, send one invite. |
| Only one friend cannot join | Client-side firewall, VPN, or stale Steam state. | That player restarts Steam, disables VPN test, and allows firewall prompt. |
| Everyone cannot join host | Host network or session state. | Change host and repeat with the same clients. |
LAN and firewall checks
The current public build supports online Steam co-op, not a confirmed separate LAN-only mode. If your group is on the same local network, still test the local blockers: Windows Firewall prompt, router isolation, VPN adapters, and security software. Treat LAN as a network environment to clean up, not as a guaranteed alternate matchmaking mode.
| Network Check | Action | When To Stop Testing |
|---|---|---|
| Windows Firewall | Allow Burglin' Gnomes and Steam on private networks. | If the prompt never appeared, re-check Windows Security app rules. |
| VPN / proxy | Disable it for one host-client test. | If the join works, add split tunneling later instead of changing every setting. |
| Router isolation | Do not put one player on guest Wi-Fi and another on the main LAN. | Guest isolation can block peer visibility. |
| Security suite | Temporarily test with game mode or allow rules, not permanent blanket disables. | Restore protection after the test and keep only required allow rules. |
FAQ
Why can't I join my friend in Burglin Gnomes?
Most failures come from stale host state, mismatched builds, Steam Overlay/invite problems, firewall rules, VPN routing, or assuming LAN support that the current public build does not clearly expose.
Does Burglin Gnomes support LAN?
The current safe answer is: use Steam online co-op as the supported path unless your build shows a LAN option. Same-network players should still check firewall, router isolation, and VPN adapters because those can break Steam session joining.
Related Guides and Data Pages
- Co-op Guide - role setup once friends can join reliably.
- Death and Revive Guide - recovery rules after a multiplayer wipe.
- Save File and Progress Guide - Steam Cloud and backup checks before risky troubleshooting.