[1.16] "Failed to sync registry data with server"

[Khytwel]

Hi!

Many people who play on our Valhelsia 3 modpack encounter this problem when connecting to their server (Failed to sync registry data with server).

On our side, we looked a little bit at the logs and the same problem seems to happen every time.
For some reason, the client-side configuration file seem to be enabling matrix enchanting sometimes even when it is disabled in the config (it is also disabled on the server side by default). This breaks everything.
The problem is sometimes solved by restarting the modpack or making a new installation which is very annoying.

Here is the client-side logs file: https://gist.github.com/Khytwel/d56d2aa8bf2bdae0863effbb7d7a4747
Quark version: r2.2-262 (version used on the logs provided)

The bug is still present on the latest version.

[HowellTheOwner]

My friends and I have consistently day by day had to go through and copy a fresh server file to our personal client side which i actually have to download from the server itself, it's been quite trouble. I can upload client logs as well but it's the same as the original post and server side seems to somehow be changing day to day.

[Londran]

Same issue. Log attached from client.

Was able to resolve it, do not know if temporaly:

1. Copy quark-common.toml from config of server to config folder of client.
2. Restart Client.
3. Connect to server
4. Success.

Attaching log of failed attempt
client.log

UPDATE: false fix... only randomly working :/

[100xdonaldx001]

Well we hopefully fixed that issue

with deleting Quark Oddities from our server and Clients.
We also deleted all the config parts in the Quarks Config from Oddities

Edit: Again just a temporarely Fix like the Person above me.
But we cant figure out where the problem is since when we start over GD Launcher we get that error bot over Twitch we can just join.

[martindanielsson]

Well we hopefully fixed that issue

with deleting Quark Oddities from our server and Clients.
We also deleted all the config parts in the Quarks Config from Oddities

Edit: Again just a temporarely Fix like the Person above me.
But we cant figure out where the problem is since when we start over GD Launcher we get that error bot over Twitch we can just join.

What is your log file saying is wrong, after you've removed Oddities? We've run into similar issues on our server. Just trying to debug.

[100xdonaldx001]

Well we hopefully fixed that issue
with deleting Quark Oddities from our server and Clients.
We also deleted all the config parts in the Quarks Config from Oddities
Edit: Again just a temporarely Fix like the Person above me.
But we cant figure out where the problem is since when we start over GD Launcher we get that error bot over Twitch we can just join.

What is your log file saying is wrong, after you've removed Oddities? We've run into similar issues on our server. Just trying to debug.

Well its the same error as the first post.
even tho the mod isnt on the server or in any client configs.

Some players can still join the server with the mod still installed, some cant join it anymore
some players fixed it with installing a fresh version of the Forge versios we are using (1.16.1-32.0.108) and joining afterwards

so its still random.

[jblosser]

This is also present on 1.15.2, with Quark-r2.1-245.jar. It all works fine locally but once I start up a remote server and try to connect, I get the same failure and very similar debug.log with registry errors around matrix enchanting, despite having it disabled in the config. The client and the server have 100% the same config file, but that doesn't matter.

[jblosser]

I did some digging and it appears this only shows up with Apotheoisis also loaded. I have that in my list, and I see the original report mentions Valhelsia 3, which also includes it. The latest Apotheosis for 1.15.2 is Apotheosis-1.15.2-3.3.7.jar. If I downgrade to Apotheosis-1.15.2-3.3.5.jar, I don't see this error. I'm not running 1.16.x so I didn't try the same checking around there, but based on release dates you might try Apotheosis-1.16.2-4.2.1.jar.

I reported Shadows-of-Fire/Apotheosis#239

[leahlouisa]

Same issue... so far only our player who has played a singleplayer Valhelsia 3 game is having the issue.

Edit to add: not sure if it is purely a coincidence or not, but of the 5 players on our Valhelsia 3 server, 2 players tried the modpack out singleplayer before joining, and three players did not. Only the two players who tried out a single player game first are having the issue. They have tried deleting and replacing their quark-common.toml file multiple times; sometimes it seems to fix things and sometimes it does not. Completely uninstalling and reinstalling the modpack doesn't seem to help.

[martindanielsson]

This was fixed in Apotheosis Shadows-of-Fire/Apotheosis@e93680d

[Vaelzan]

@martindanielsson Quark is (for the moment) on 1.16.1, the Apotheosis patch was for 1.16.3. A 1.16.1 version with the patch was not released and is not planned to be (according to the Apotheosis developer), so the uploaded fix won't do anything at all to help with this issue since they're different Minecraft versions.

[martindanielsson]

@martindanielsson Quark is (for the moment) on 1.16.1, the Apotheosis patch was for 1.16.3. A 1.16.1 version with the patch was not released and is not planned to be (according to the Apotheosis developer), so the uploaded fix won't do anything at all to help with this issue since they're different Minecraft versions.

Shoot! I didn't see he had already upgrade to 1.16.3 in the 1.16 branch :(

[100xdonaldx001]

Well we hopefully fixed that issue
with deleting Quark Oddities from our server and Clients.
We also deleted all the config parts in the Quarks Config from Oddities
Edit: Again just a temporarely Fix like the Person above me.
But we cant figure out where the problem is since when we start over GD Launcher we get that error bot over Twitch we can just join.

What is your log file saying is wrong, after you've removed Oddities? We've run into similar issues on our server. Just trying to debug.

Well its the same error as the first post.
even tho the mod isnt on the server or in any client configs.

Some players can still join the server with the mod still installed, some cant join it anymore
some players fixed it with installing a fresh version of the Forge versios we are using (1.16.1-32.0.108) and joining afterwards

so its still random.

Need to update my message here. After a couple days everyone got their errors under control with the things I already said. We all looked at each other's logs and could eliminate all the errors that were made by cleaning up their files from quark oddities. Everyone can connect to our server fine now. And over the last days noone got the error anymore.

So I can say it was a successful fix it just took some time for everyone to set it up right.

So it was my mistake here that I said it didn't worked.

Edit 1: Hope that others can test this fix too and say if it worked or not.

Edit 2: we just installed a gravestone mod instead of the one oddities had

[MericGit]

What I did was did the temporary fix they put in the thread. (There's another bug report for Apo for the same problem) I.E. adding a dependency for Apo for when quark is present to load Apo after Quark.

Doing that seemed to work fine. It does require unzipping the jar, editing the mods.toml file then repacking the jar though so it's not really the most efficient solution for someone who isn't tech-savvy.

[Th3Madjackal]

Got the exact same issue as OP except it bounce around, sometimes i'll get it for hours and sometimes i'll be able to re-join the server a few minute laters.
I tried the dependency trick but doesn't seems to work, unless i've messed up writting it https://pastebin.com/RK9X5RJa .
But from what i've read (and the very very few post that get more than barebone techsupport reply to some distant related issue with the same message) there's 0 way to fix that aside getting rid of QuarkOddities.

[Vazkii]

Is this still relevant?

[Khytwel]

Apparently it's fixed, it was a problem with Apotheosis: Shadows-of-Fire/Apotheosis#239.