-
Notifications
You must be signed in to change notification settings - Fork 27
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
Potential issues with upgrading worlds to 1.18 #42
Comments
I also found that when running on a server it will lower the tps and mspt by a ton |
Dealing with exacte same issue as CarbonGhost. |
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. |
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 |
Relevant Fabric API issue here: FabricMC/fabric#1837 |
Has anyone found a real workaround for this? It's preventing me from upgrading my server 😢 |
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. |
After a long time spent troubleshooting, I believe that Carpet AutoCraftingTable may cause chunk corruption when upgrading a 1.17.1 world to 1.18. The issue seems to specifically be related to tile entities, in corrupted chunks, tile entities will become invisible and containers will lose their items.
Steps to recreate bug:
51 ~ 311
Seemed to fix the issue:
51 ~ 311
Sorry for not giving a more descriptive issue, but I don't understand the bug enough to give more info.
Potential related / caused by MC-244164.
The text was updated successfully, but these errors were encountered: