#Character saves alternate between sessions and join error EXPEDITION_NOT_FOUND_BY_INVITE_CODE

1 messages · Page 1 of 1 (latest)

willow iglooBOT
#

Thanks for flagging this. “Character saves alternating between sessions” and the join error “EXPEDITION_NOT_FOUND_BY_INVITE_CODE” are not currently listed in the Known Issues. For join/connect problems, please try:

  • Run the game as Administrator.
  • Check your Firewall/Antivirus and allow the game.
  • Press F11 to view ping/network stats.
  • If you hit disconnection loops, try switching servers.
  • For stalled matchmaking/joining: wait up to 15 minutes; if nothing happens, restart the client and ensure your expedition is planned and a Trampler is selected before queueing.
  • Prefer a stable, wired internet connection. If possible, test with another connection (e.g., mobile hotspot) or confirm you can reach the PlayFab site in a browser.
    We’ll keep monitoring; please continue sharing details if this persists so we can investigate patterns.

Sources:

willow iglooBOT
#

Thanks for the details. While that specific error isn’t listed, these steps can help with expedition/join issues:

  • Verify the game files via Steam.
  • Restart the client; ensure your expedition is planned and a Trampler is selected before matchmaking.
  • Try switching servers/regions and retry.
  • Check Windows Defender Firewall and allow the game.
  • Prefer a stable wired connection; if possible, test another connection (e.g., hotspot) and try opening the PlayFab website to confirm access.
  • Update Windows and your GPU drivers.
  • If you’re on Linux/Steam Deck, install the Proton BattlEye Runtime from your Steam library.

If it continues, please share diagnostics so we can investigate:

  • player.log and player-prev.log from: %USERPROFILE%\AppData\LocalLow\Hologryph\SAND
  • Your 17-digit SteamID
  • Approximate time the issue occurred
  • Did it happen on the Trampler or outside?
  • Were you using a custom or default Trampler?

You can also press F11 to view ping and other network debug info while testing the above.

Sources: