Bug description
When hosting through Steam with "Automatically accept Steam connections"
enabled, a joining player frequently remains indefinitely at:
Waiting for host to accept
There is no request or action available on the host. Rehosting the same
save and attempting to join again eventually works. In the attached log,
the first two hosting attempts failed and the third succeeded.
Versions
- RimWorld: 1.6.4871 rev591
- Multiplayer: 0.11.5+4a3be27-dirty
- Host and client: Windows / Steam
- Both machines use the same RimWorld and Multiplayer versions
- "Automatically accept Steam connections" is enabled
Steps to reproduce
- Host an existing multiplayer save using Steam.
- Have another Steam player join.
- The client sometimes remains at "Waiting for host to accept".
- The host receives the SteamP2P connection, but the player never joins.
- Stop hosting and host the same save again.
- The same player can then join successfully, sometimes after more than
one rehost.
Failed attempt in host log
MpServerLog: New connection: SteamP2P (<Steam ID redacted>:)
MpServerLog Error: Received a join packet: True for player:
Multiplayer.Common.ServerPlayer (player should only be null when joinPacket is true)
The join-packet message repeats several times. There is no "has joined",
"Adding player", or "World response sent" message.
Successful attempt
MpServerLog: New connection: SteamP2P (<Steam ID redacted>:)
MpServerLog: Notification: <player> has joined
MpServerLog: PlayerList: Adding player 1:<player>
MpServerLog: World response sent
Client log
The client remains in the connecting window until it is closed:
Stopping multiplayer session from virtual System.Void
Multiplayer.Client.BaseConnectingWindow::PostClose()
No version mismatch or connection timeout is logged.
Additional notes
This appears different from #843 because automatic Steam acceptance is
enabled, and the host successfully creates the SteamP2P connection.
#948 has similar visible symptoms, but the logs and networking setup appear
different. In this case, the characteristic behavior is repeated join
packets arriving after the server has already created a ServerPlayer.
Bug description
When hosting through Steam with "Automatically accept Steam connections"
enabled, a joining player frequently remains indefinitely at:
There is no request or action available on the host. Rehosting the same
save and attempting to join again eventually works. In the attached log,
the first two hosting attempts failed and the third succeeded.
Versions
Steps to reproduce
one rehost.
Failed attempt in host log
The join-packet message repeats several times. There is no "has joined",
"Adding player", or "World response sent" message.
Successful attempt
Client log
The client remains in the connecting window until it is closed:
No version mismatch or connection timeout is logged.
Additional notes
This appears different from #843 because automatic Steam acceptance is
enabled, and the host successfully creates the SteamP2P connection.
#948 has similar visible symptoms, but the logs and networking setup appear
different. In this case, the characteristic behavior is repeated join
packets arriving after the server has already created a ServerPlayer.