-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Issue when updating from 1.0.16 - 1.0.17 #212
Comments
also note that the log says something about an auto sieve I currently don't have an auto, I do have 1 normal and 1 heavy sieve. |
do you have backup of the world from before it got messed up? |
that was the latest before updating I shall try some of the others. |
oldest backup did not work still had the corruption. I did find a way for now to get my stuff over when updating, I stored my whole base into vanilla chests(had to be vanilla otherwise it got corrupted/swapped) |
world without the wooden crucible turning into a ticking crash - https://drive.google.com/open?id=1S2Q7YhKuwr6Kp8tX85P942m2mSo_vYI_ |
Okay so this issue gets fixed by adding https://minecraft.curseforge.com/projects/notenoughids |
yes it did |
Okay thanks, im gonna add JustEnoughIDs in the next update, does the same thing just updated |
1.0.18 |
Bug Report
Steps to Reproduce (for bugs)
update from 1.0.16 to 1.0.17 with this world file
Logs
the roosts)
world dl - https://drive.google.com/open?id=18IZ8BMdJavHzewSSLxv-Y2xrj-wuWVS_
Client Information
The text was updated successfully, but these errors were encountered: