Something is broken in the current (as of 15.10) continious release

[Michael-Shevtsov]

Unfortunately I have no experience with the development of this mod, so I can't narrow the issue. I have script that automatically updates mod version to the current continuous release before launching Rimworld and noticed that mod is broken right now - client can't connect at all.

I've build mod myself from ab90ccd and it's working again. So it should be somewhat easy to bisect.

[mibac138]

Please provide more details

• how are you connecting? (LAN/Direct/Steam)
• what do you mean by can't connect at all? Is there any message, any error?
• are there any errors in the debug log? (first icon at the top of the screen after enabling development mode in options)

Also, please send the Player.log file. It's available at C:\Users\<user>\AppData\LocalLow\Ludeon Studios\RimWorld by Ludeon Studios. Just keep in mind that this file is reset every time you launch the game, so if you played the game without encountering this issue, please first reproduce it, and then send the file

[Michael-Shevtsov]

None of the connection types work. The client only shows a “Disconnected” dialog. The host console does not log any connection attempts. When using Steam, I get the standard prompt to accept the connection, but after accepting, the peer still sees the same “Disconnected” message.

I will test the referenced PR later today and attach player.log if I encounter any issues.

Also, could you clarify “probably connected to a host with a different protocol version”? To stabilize 1.6 MP, I copied all RimWorld files and mods to the client before launching to ensure everything matched exactly. It still doesn’t make sense to me that the issue was introduced months earlier. It almost certainly relates to changes after ab90ccd, doesn’t it?

[mibac138]

I have received an issue report that sounded similar. The root cause there was that the host and client had different Multiplayer versions installed, and a recent commit (460bd71) had bumped the internal protocol version (in Source/Common/Version.cs). Due to that change, a different code path was executed. That code path is very rarely ran, and nobody reported an issue with it, but it was broken since a0a69a3, and that PR fixed it. Although now that you say you only have a "Disconnected" message, this might be a different issue (the other report had a Local packet read error). Regardless, please let me know if the new version fixes this for you, and if not, it's easiest for me to diagnose this if you provide the Player.log file

[Michael-Shevtsov]

Tested on the latest release (with #767) and it works fine!