[Bug] Desync due to HASH / Different mod order

[Evilhelder]

Area

Mod loading

Severity

Minor

What happened?

My friends and I are unable to play using mods that modify events—such as "Aram:Mayhem," which adds runes with specific effects; when using it, a desync occurs immediately and automatically after card selection. I initially suspected the mod itself, but we encounter the same issue even with simpler mods (like character mods that only add their own cards without introducing new mechanics or events):

For some reason—unlike in my game, where the mod order and hash remain consistent—my friends' games generate a random mod order and a different hash. Even after correcting the order (both in-game via Ritsu and on Steam) and restarting, the game refuses to save the mod order and reverts to the previous random hash. To complete a match, we have to disable the "Enable ModelDB Sorting" option in Ritsulib every time we play, yet the supposedly incorrect order continues to cause constant, random desyncs.

Here are my game logs.
PC 1 godot.log
PC 1 ritsulib_state_divergence_20260907_013524_3929756_checksum_1_4d0c02b2_8d3a83f0fc6f4ac780128e1f22ec8595.zip

And here are the game logs, my friend.
PC 2 godot.log
PC 2 ritsulib_state_divergence_20260907_013524_8132270_checksum_1_bf6ef57c_aaa33421ab204b7181aeb1d34c2c2a7c.zip

Steps to reproduce

1- Download the mods from steam
2 - Open the game
3 - Create a room
4 - Play the game

Expected behavior

The game synchronizes the hash and mod order.

Logs / stack trace

RitsuLib version

v0.5.19 (compat 0.107.1)

Environment

Windows 10 Pro

[Evilhelder]

Sorry for any writing errors; I am still learning English.

[Evilhelder]

Also, I don't know if it's relevant, but unlike me, my friends use Windows 11, while I'm on Windows 10.

[BAKAOLC]

Version 107 (official release) of the game itself does not implement stability sorting measures, so for mods that add in-game models, it requires the loading order to be exactly identical.
This can generally be quickly resolved using various order-adjustment mods from the Steam Workshop, or the mod order sorting feature included with ritsulib in version 107.
This is an issue inherent to the original game itself. To ensure compatibility with the original game and other mods, this part is not within the active handling scope of the lib.

[BAKAOLC]

I'll check the log to find why the sorting cannot be saved.

[Evilhelder]

Version 107 (official release) of the game itself does not implement stability sorting measures, so for mods that add in-game models, it requires the loading order to be exactly identical. This can generally be quickly resolved using various order-adjustment mods from the Steam Workshop, or the mod order sorting feature included with ritsulib in version 107. This is an issue inherent to the original game itself. To ensure compatibility with the original game and other mods, this part is not within the active handling scope of the lib.

We tried using some mods that handle load order, but the result was the same; the game always flags a desync issue—related to the hash or something similar—when starting a match. Sometimes, an error even pops up stating the game version is incorrect when my friends try to join the lobby without first clicking "Sort Now" in the Ritsu "Core Settings".

[BAKAOLC]

I found a log output with StableHashPatch on PC 2, indicating that on his side there is an additional layer of hash processing behavior, which is the reason for the extra differences in the hash. I am currently locating its source.

[Evilhelder]

I found a log output with StableHashPatch on PC 2, indicating that on his side there is an additional layer of hash processing behavior, which is the reason for the extra differences in the hash. I am currently locating its source.

So, it turns out the problem wasn't actually me—since I’m the one who usually hosts the matches, I asked my friends to host games for each other. Even though their games behaved the same way and generated the same hash, they couldn't join each other's lobbies; they kept getting an error stating that their game versions were different.

[Evilhelder]

I remembered another strange behavior with my friends' game: for some reason, when downloading a Steam mod that had two versions (Beta and Public), the game would only recognize the Beta version. However, after switching the game version to Beta and then back to Public, the problem went away.

[BAKAOLC]

I remembered another strange behavior with my friends' game: for some reason, when downloading a Steam mod that had two versions (Beta and Public), the game would only recognize the Beta version. However, after switching the game version to Beta and then back to Public, the problem went away.

This issue is caused by a problem with the Steam Workshop's working mechanism, so there is indeed nothing that can be done about it.

[BAKAOLC]

Additionally, I found the source of that hash modification. It appears to be TheRhythmGirl's patch, which performs an additional processing step without any recognition checks, leading to the mismatch.