search

FTBTeam / FTB-Modpack-Issues

Any and all FTB Modpack issues are here! Please create a new issue, add to an existing one or maybe even suggest a feature in the discussions
https://feed-the-beast.com/modpack
43 stars 13 forks source link

Server Connection Error: Unkown registry keys #6145

Open hyperliskdev opened 2 weeks ago

hyperliskdev commented 2 weeks ago

Modpack

FTB Presents Direwolf20 1.21

Modpack version

1.4.1

Launcher

Prism

Has the pack been modified

No

Log Files

[14:31:20] [Render thread/INFO] [minecraft/ConnectScreen]: Connecting to [ip_address], 25565
[14:31:22] [Render thread/WARN] [minecraft/ClientCommonPacketListenerImpl]: Client disconnected with reason: The server send registries with unknown keys: ResourceKey[minecraft:item / jaopca:dusts.xychorium]

Describe the bug

Connecting to a server that was started on an older version causes some registry errors after updating the server.

Steps to reproduce

  1. Update to latest direwolf20 Season 14 1.21 pack server and client.
  2. Attempt connection to server.
  3. Registry error

This server was also played on before the update.

Expected behaviour

I should be able to just connect to the newly updated server

Screenshots

image

Additional information

No response

BDTheNerdyMedic commented 2 weeks ago

I believe something in the kubejs folder is not updating or purging properly. Try removing that folder and then rerun the update. If that doesn't work, try purging the config and defaultconfig folders too.

Dnny44 commented 1 week ago

I also have this issue after updating to 1.4.1. I have attempted the fix that @BDTheNerdyMedic suggested in removing the kubejs and re-running the update did not resolve the issue. Also repeated the same process with the config and defaultconfig folders. Any direction would be spectacular!

Dnny44 commented 1 week ago

I also have this issue after updating to 1.4.1. I have attempted the fix that @BDTheNerdyMedic suggested in removing the kubejs and re-running the update did not resolve the issue. Also repeated the same process with the config and defaultconfig folders. Any direction would be spectacular!

Deleting the entire instance and letting the installer rebuild it, then restoring the world folder seems to have resolved this for me at the moment.