The button labelled "Resume As A Host" to continue the campaign is greyed out after the most recent Steam update was downloaded. The saves are still present on both of our computers.
- Be on the current latest version, 1.7.1 17625.2613664, released on Steam around Jun 21, 2022
- Go to the multiplayer page
- Notice that it's not possible to host a game that was saved with the 1.7.1 17233.2290568 build released around May 27, 2021
As both me and the host are using Windows machines, I can't say whether this is also an issue on any other OS (though I doubt there would be any difference, this seems to be a version/build mismatch issue). I've attached a player save (no idea if the host's is different), but I had to change the file extension (it should be ".save_multiplayer", not ".save") since the HTML file input artificially restricts the file extensions it accepts.
Details of any solutions that have already been attempted:
At first we thought it might be because of the game being considered "modded" (note, neither me nor the host have ever run any mods on Three Kingdoms), so we used Steam to verify the integrity of our game caches. No files were out of order. Next we tried backdating to the 1.7.0 version (build 16713.2221481) included in the Betas section. We were able to start hosting and got to the join-up screen, but almost immediately after loading started we were kicked back to the title screen (we tried this multiple times without success).
After that, I dug around in the log "modified.log" (under the Three Kingdoms' app data folder). After finding that the "manifest.txt" file under "/Total War THREE KINGDOMS/data/" was missing (and remained missing no matter how many times I deleted files/folders and had Steam check Three Kingdoms' file integrity), I recreated it based off of the version of the file that existed in the aforementioned 1.7.0 version. After massaging it and getting all the files that "modified.log" told us we needed, and at the right sizes, the game was no longer considered "modded" (do note that version 1.7.0 was still considered modded, and as far as I could tell it was just because the contents of the "manifest.txt" file were incorrect, even after checking file integrity multiple times). This, however, did not result in the "Resume As A Host" button being clickable for the original host (or as the other player, predictably, since non-hosts aren't allowed to rehost an existing save).
My best stab at solutions that are out of my control:
The first option (and the laziest, and the most likely to succeed) is to have the previous 1.7.1 17233.2290568 build listed as a Beta on Steam that can be rolled back to. This would almost assuredly allow saves from that build to be hosted again.
The second option would be to relax the version/build exclusion logic so that saves made on old versions/builds would be hostable on the new version/build (at the host's own peril). This is likely a time-prohibitive option with limited future utility.
If you need any other information or one of the host's saves, feel free to ask and I'll supply whatever I can.