Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

👉 "Failed to synchronize registry data from server" with NoFog - Tracking issue - Why does this happen #4854

Open
quat1024 opened this issue Jul 12, 2024 · 4 comments

Comments

@quat1024
Copy link
Collaborator

quat1024 commented Jul 12, 2024

Instances of this: #4839 #4674 #4662 #4641, probably #4846

Issue on nofog's end (just in case): Virtuoel/NoFog#36

Why does this happen.

Commonalities:

  • Always seems to be in a giant modpack.
  • Client always contains the mod No Fog.
  • Removing No Fog fixes it.
@quat1024 quat1024 pinned this issue Jul 12, 2024
@quat1024 quat1024 changed the title [Tracking issue] The goddamn sound event NoFog registry sync thing 👉 "Failed to synchronize registry data from server" with NoFog - Tracking issue - Why does this happen Jul 12, 2024
@Tommeh1
Copy link

Tommeh1 commented Jul 24, 2024

@quat1024 Is there any chance you can provide me with a modpack affected by this problem so i can try to narrow down the problem?
I assume that there is a 3rd mod that has to be present alongside NoFog and Quark for this to occur given what Virtuoel was able to tell me so far: "Been looking into it, but not yet been able to reproduce it with Quark and NoFog alone, so it's likely some weird multi-mod interaction thing going on."

@Vazkii
Copy link
Member

Vazkii commented Jul 28, 2024

A temporary fix for this should be to force crash the game (in a safe way so that FML catches it and shows an error window instead of force closing) with a message that indicates Quark is not compatible with NoFog. That should at least make it more intuitive for users until the actual problem can be solved.

@VazkiiMods VazkiiMods deleted a comment Aug 25, 2024
@Fl414r
Copy link

Fl414r commented Aug 29, 2024

On ATM 9 I keep getting this error if try to connect to any server with NoFog installed on my side.
But I didnt tested singleplayer and servers with NoFog on server side

@Tommeh1
Copy link

Tommeh1 commented Sep 5, 2024

It shouldn't do anything server side, but it is most certainly good to know that ATM9 is affected by this.
Now i have something i can potentially use to narrow things down

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants