Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
This issue was brought up a few days ago here (reddit). The answer from Multiguns sums up whats happening pretty well.
"Mismatch errors are NOT a mod problem. Ever.
It literally means that the version you have does not match the version on the server. That's it.
It's not a mod bug. It's not a problem with the creator. It's not something for them to fix. Mod creators CAN NOT control ANYTHING after we upload the mod to steam.
Update the server mods, and then update your version. If you are still struggling, verify files on Conan and it will force steam to download the latest version of the mod. If your server still isn't updating, then you need to contact the server."
If this isn't working for you, there's something on your end causing it. Our servers our working fine after updating properly.
Hmm, I'll have to play with my server. It's not a version mismatch, the mod is just no longer functional/recognized by my server despite being installed. I attempt to connect to the server and get a 'mod mismatch' error, and the list doesn't have BetterDescription in it. I remove it from my loaded mods and join without an issue. But so long as I know it's working for others I can dig into files on my end.
EDIT: G-Portal server. Server had somehow deleted the .pak file, and would not reacquire it. Renamed the known updated file from my PC, uploaded it, and it's now working properly again.
Glad you were able to get it sorted!
That being said, I'm going to lock this thread as the original issue this discussion was for is now fixed. If anybody has more concerns, please open a new thread.