[0.12.26] [kovarex] Mod Mismatch Error with Multiplayer

[Xterminator]

I'm trying to play some Multiplayer with someone and we played a few days ago on 0.12.24 and everything worked fine but now it won't with 0.12.26. We are using several mods, which worked fine before.

However, after updating to 0.12.26, when either of us tries to join each other, we get a mod mismatch error. What is confusing though is that we have double and triple checked all our mods and they are exactly the same.

The error is a bit confusing because it's like saying that the mods are both on the server and not on the server at the same time. I wish I could of gotten a screen-shot but he got off for the night.
The error said this for each mod though though:
The Mod YARM is not on the server.
The Mod Yarm is only the server.



It did that for every single mod we have even though they are all enabled and the same version. This is extremely puzzling and very annoying, any help would be greatly appreciated.

[Mikrotherion]

Can confirm this problem, although to a lesser extent.

For me and a friend it's only the FARL mod that gives us trouble. The others (peace, ressource spawner overhaul, blueprint string) did work.
We also checked that the versions of the mods are the same.

[kovarex]

I would like to see the error message and maybe even to have the mod folder of the two people.

Couldn't there be some case sensitivity related problem?

[Mikrotherion]

Case sensitivity is unlikely, unless it has been introduced in 12.26. Worked in 12.20 before, although sometimes it was necessary to fiddle around with some mod toggling/ untoggling. However, FARL worked before but after RSO and Peacemod were added, FARL was a problem. I'd understand if it were the newly added mods.

I can send my mod folder. I have no access to my friend's now. Will play with him again this week but dunno when.

EDIT: Might be a case sensitivity problem after all. Have to try some more.

[kovarex]

Oups, I did check that code again, and I actually find not one, but two different problems.

a) Problem 1 is that it was comparing mods versus mods that can affect the game state (scenario pack for example could make a problem).
b) It assumed, that the internal mod list is sorted by name, but it was actually sorted by load order, so I fixed that as well

Let's see how it works in in 0.12.27, but there is a big chance it will be working properly.

[Mikrotherion]

Ah, nice to hear.Thanks.
0.12.27 is due Friday?

[kovarex]

I'm not sure, there are lot of things to fix yet.

[Mikrotherion]

Ah, no worries.
As a temporary solution it's enough to make sure that on both (all) systems there are the same mods, so the load order of mods will be the same. At least that worked for my friend and me.