Fabric API

Fabric API

Mods
106M Downloads

[1.16.1] Registry Sync Module

FlashyReese opened this issue · 3 comments

commented

As stated in #507 (comment)

image

This occurs on a 1.16.1 mp server, even if freshly generated. Use the workaround method does not work(deleting fabricRegistry.dat)
NOTE: This does not occur in SP worlds.

  • Fabric API 0.17.+build.386
  • Fabric Loader 0.9.1+build.205

image

Edit: Also all client sided mods such as LambDynamicLights and Sodium are not present in the server.

commented

I haven't seen this bug in years.

commented

You use Vanilla to connect a fabric server which have a mod that add new Block?

commented

I write a gravestone mod, when player dead, mod will place a gravestone block to store player’s item.

https://github.com/uestclug/gravestone

But I want this mod support Vanilla, so I Mixin PalettedContainer to cheat client that the gravestone block is a player skull.

It work fine in 1.16 with fabric-api-0.14.0+build.371-1.16, but when I update to 1.16.2 with fabric 0.17.2+build.396-1.16, Blockstate is out of order.

I found that fabric-registry-sync will remap registry, and send sync packet to fabric client. But if client don’t install mod which register block, the block registry will not update. In addition, the Vanilla client will not update block registry, too. I don't know how to solve this problem elegantly.