no sadly this morning same deal again @funcom Please fix this!
Still occurring to me, verified files, deleted modlist, removed and reinstalled mods. I really hope they extend the battle pass to make up for lost time.
We are facing this issue on server 1977 since the 3.0 update, when the server restarts we are able to join, then past few hours the problem returns, my guess is that the server is getting some disk partition full, that partiton is cleared on restart and then with the use during the day fills all the partition again.
I think that at some point all servers will suffer of this condition, unless fc deals with it, im counting 4 or 5 server showing up the forums with the same problem.
Is this being looked into still? Any update on it?
I can tell you right now itās a problem with the game not writing to the servermodlist file. If you delete the file, and create a new one: It writes to the file ONCE if no mods are subscribed to and you re-download the mods. You can play once with no infinite modmismatch loop. But once that file has been created, if it changes it any way, it doesnāt actually change the servermodlist file like itās supposed to:
Thus leaving you in an endless mod-mismatch loop.
Itās not that your mod hasnāt been updated: The servermodlist.txt isnāt being written to properly. So your mod updates, but the servermodlist.txt doesnāt reflect that.
So you have to unsub from the mod that was updated, delete the servermodlist file, verify integrity of game files, start the game, try to connect to your server, redownload the newly updated mod, and then you can connect.
Not sure why this is so hard to fix when the problem has been pointed out a few times now. 
There is no game-level bugā¦
That is EXACTLY how that file is supposed to work 
I think you misunderstand what that file is used forā¦ Itās specifically a part of the auto-subscribe to mods and reconnect featureā¦ so it is ONLY relevant when your game restarts for a loop.
Other times itās not being used at all.
Yes, because that actually forces Steam to properly update your mods.
See the issue is not on the games level, itās something up with the steam workshop. Whenever mods get updated, your game will not notice and simply think that itās up to date and launchā¦ So there is āsomeā bug, but itās related to the steam workshop.
(My speculation is that theyāre working on a new feature involving the workshop which has this as a temporary side-effect.)
But bottom line, once you set up everything properly and both the server and the game clients are updated (even if itās a bit of a struggle getting there) - it works and lets you in and the mismatch loop goes away. Itās probably best to manually keep track of mods during this timeā¦
I personally check my subscribed mod list every day on steam, if I see any of the mods I use having a new āupdatedā date, then I stop my server, do the updates, hit unsub and resub in my client for that specific mod only and it works on the first try every time, never getting the mismatch error like this
1 Like
Hi. me again
Do you know why this loop would be happening specifically for some servers but not others even if they have the same mods?
The same reason, one of the mods are not updated correctly on either the client of the server.
Now if two servers use EXACTLY the same mod list without any of them having any additional ones and one server lets you in while the other one gives you a mismatch error then it would mean that server in question has been running with an outdated mod and needs to be taken offline and updated.
If however any of the mods differ, then those individual ones could be causing it all the same, it only takes a single mod that didnāt update correctly to break things sadly.
The typical steps listed to get rid of the issue on the client side work, so unsubbing from all mods, doing either a verify files or physically deleting the mods and then either connecting to the server and having it resub for you or manually resubbing them and putting them in the correct order and then joining (this latter one is more prone to error hence why people suggest the auto-connect)
If it doesnāt let you in after all of these steps then thereās a good chance the issue is with the server and it wouldnāt let others in either until updated
Keep in mind though, if you did this and the server let you in, but it doesnāt let you in the next day, it does not mean the fix didnāt work and the same issue is backā¦ it usually means that one of the mods got updated in the meantime so you have to unsub / resub to that mod (which is way easier than unsubbing from all, but requires you to keep track manually of any updates of any mods on their respective workshop pages) or do this whole āfixā procedure again.
1 Like
Same problem. Itās inconsistent and none of the workarounds work all the time. I realize 3.0 is still kinda new but this is getting really old, really fast.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.