-
Notifications
You must be signed in to change notification settings - Fork 4
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
[Bug]: Failed to Create new World or Entering Existing World with the ceramicshears-fabric-1.21-3.2.0.0.jar installed #28
Comments
Thanks for your report! I will look into that, when I have time :) |
Hi @cech12, I've try to downgrade the Fabric version to 0.15.11 - 0.100.3+1.21, and the problem are still exists, I cannot create new world or open existing world with the CeramicShears enabled. Below are the log after I downgraded to Fabric version to 0.15.11 - 0.100.3+1.21, Regards, |
That's weird. That is the version I do all my tests. Thanks for your response. I will look into that :) |
…ontains shears tag as match tool condition cech12/CeramicShears#28
…ontains shears tag as match tool condition #28
Thanks again for your report! Unfortunately, I could not reproduce the error, but I have an idea what caused the issue in your mod pack. I hope I could fix it in the upcoming version 1.21-3.2.0.1. If not, feel free to re-open the issue. |
Hi @cech12, With the updated version 1.21-3.2.0.1, I can confirm that the CeramicShears and WoodenShears can now once again be loaded and used successfully on my game, I've tried it in SinglePlayer mode and Multiplayer Server/Client mode. Regards, |
Nice to hear that! Thanks for your feedback! 😁 |
Minecraft Version
1.21
Mod Loader
Fabric
Mod Loader Version
0.15.11 - 0.100.7+1.21
Mod Version
ceramicshears-fabric-1.21-3.2.0.0.jar
Modpack or other Mod
Describe the Issue
Failed to Create new World or Entering Existing World with the ceramicshears-fabric-1.21-3.2.0.0.jar installed.
Logs
https://pastebin.com/GEtZuU6F
Do you use any performance-enhancing mods (e.g. OptiFine)?
No
The text was updated successfully, but these errors were encountered: