Potential issues with upgrading worlds to 1.18 about carpet-autocraftingtable

[magneticflux-]

@rhettl This works: https://github.com/apple502j/UpdateBlockEntity

[RealCrayfish]

I also found that when running on a server it will lower the tps and mspt by a ton
20tps goes to 1-5tps when added

[MickZi]

Dealing with exacte same issue as CarbonGhost.
Workaround is not a solution since loading in all builds would require immense effort.

[Airblader]

I'm the author of MC-244164 and I can at least confirm that I had installed carpet-autocraftingtable on the server shortly before the world download was taken that gets corrupted by updating to 1.18.

[magneticflux-]

My current theory, copied from MC-244164:

I believe the issue manifests when a TileEntity/BlockEntity with a non-vanilla ID is included in the list. Because in Schema2842 the DataFixer only reads types of DSL.list(TypeReferences.BLOCK_ENTITY.in(schema)) and the non-vanilla ID isn't considered a BLOCK_ENTITY so the type doesn't match. This deletes the data instead of throwing an error because the field is marked as optional.

[magneticflux-]

Relevant Fabric API issue here: FabricMC/fabric#1837

[rhettl]

Has anyone found a real workaround for this? It's preventing me from upgrading my server 😢

[gnembon]

Well, it is a vanilla bug, not a carpet bug nor fabric bug.

Having said that, that's the main reason act is NOT part of any other carpet 'package', like carpet extra, since it by design violates the integrity of the vanilla worlds.

I suggest not using auto crafting table and switch to dropper crafters from carpet extra.