Registry Synchronization Error when joining a server [Solved]
RRubberGlove opened this issue · 4 comments
Minecraft Version
1.16.5
KubeJS Version
kubejs-forge-1605.3.19-build.299.jar
Rhino Version
rhino-forge-1605.1.5-build.75.jar
Architectury Version
architectury-1.32.68.jar
Forge/Fabric Version
36.2.39
Describe your issue
Me and some friends are trying to create a modded server using the "Rougelike Adventures and Dungeons 2" modpack with a few mods added. We all have the exact same pack, yet only the server owner is able to connect to the server, yet the rest of us get registry errors, as seen at the bottom of the .log. They are all related to KubeJS and we've tried almost every solution we could find on the internet. I would really like some help fixing this because it's getting really frustrating.
Crash report/logs
https://gist.github.com/RRubberGlove/1d3ff66d976c5cc4efc1567e9665a09a
Both the server and the client need identical script folders (unless you know what you are doing). This error in particular comes from the startup_scripts folder not being the same.
Make sure that you install the modpack properly, not just copy the mods folder. Use a launcher like the CurseForge app to do that.
We all used the curseforge app and made sure everything was the same, but I think that we might have missed that. Where would I find that folder? (Sorry I'm not very good at this kind of thing.)
Edit: Ok I'm stupid, my brain completely missed the "Inside the kubejs folder" part.
Both the server and the client need identical script folders (the folders inside the kubejs
folder), unless you know what you are doing.
This error in particular comes from the startup_scripts folder not being the same.
Make sure that you install the modpack properly, not just copy the mods folder. Use a launcher like the CurseForge app to do that.
Modpacks use KubeJS to add custom items, blocks and more.
That causes the registry syncronisation check to fail if the scripts used to add custom registry objects (like items and blocks) are not the same on both sides.
This error is caused by mismatched (or non-existant) scripts on the two sides, and it is up to you to synchronise those.
KubeJS will never sync scripts due to security concerns (RCE exploits).