-
-
Notifications
You must be signed in to change notification settings - Fork 348
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
minecolonies:cook has thrown an exception #10592
Comments
Seems restaurants are now "missing its respective building" |
|
We went around our server creative pasting back any restaurant that had "lost its respective building." They were all functional again. But after a server restart my, and at least one other player's restaurant had again "lost its respective building." We are testing the hypothesis that the fixed restaurants that broke had added back menu items and fuel, because one colony had the restaurant replaced, did not add fuel or menu items, and after the restart it was still functional. Edited to add I am on the OPs server. |
Another update. After server's scheduled restart my restaurant had "lost its respective building" again. Another colony that was not affected at the earlier restart, was affected with this latest restart. The difference being that I had set menu items and fuel in it when I went to check on it. So, I think whatever the error is, it has to do with menu items being set. |
This was introduced by #10579. |
For now, the best thing to do is to downgrade to v1.20.1-1.1.790 until it's fixed. |
Is there an existing issue for this?
Are you using the latest MineColonies Version?
I am also running the latest versions of other mods that are part of my problem.
Did you check on the Wiki? or ask on Discord?
Minecraft Version
1.20
MineColonies Version
1.20.1-1.1.791
Structurize Version
1.20.1-1.0.763
Related Mods and their Versions
Mod list in latest.log
Reproduction Steps
Logs
https://gist.github.com/AnyankaT/01711aea361b3e4d5ad1fd7c3a2186bc
Anything else?
No response
Footer
Viewers
The text was updated successfully, but these errors were encountered: