Record where joining fails

Distinguish no invitation, failed entry, being returned after entry and in-game desynchronization. Start from a Steam-friend invitation to this game.

Try one change at a time

  1. Check that everyone launched the same game through Steam and is a Steam friend. Record build numbers and Mods. Matching builds and a clean shared configuration are suggestions for removing variables, not proof of a particular root cause.
  2. If using Invite Only, check the profile button or Settings > General > Lobby Mode. The developer’s all-participants setting and re-host instruction is intended to prevent uninvited entry; it does not prove every failed join is a privacy bug.
  3. The official connection advice is to avoid VPNs or software/modifications that change the connection, and let the friend with the better connection and PC host. Change one variable, retry an invitation, and record the result.
  4. Check updates. The 1.0.30 announcement describes network-code improvements and bug fixes, without saying they cover every fault. File verification or reinstalling is not a guaranteed repair; an original player report still failed after those attempts.

Preserve a fresh log if it still fails

On Windows, press Win + R, enter appdata, then open:

LocalLow\TENSTACK\Gamble With Your Friends

Find the Player file. The developer says it contains the latest session and older sessions are overwritten. Save the problem time, both builds, host, screenshot/error and Mods status alongside it; decide yourself whether to submit them to support.

A successful test means the invited player joins and both players see synchronized money or machine results during a day. Seeing the room name alone is not enough. This site has not accessed or sent your logs.