-
Notifications
You must be signed in to change notification settings - Fork 5
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
Registering pools during worldgen seems to cause Minecraft to complain about "missing" pools #2
Comments
Looks like the tower do spawn their pieces but minecraft keeps complaining about missing pools. Like this: Though it seems the pool down exist as it is registered here but mcinecraft might be throwing a fit the first time it attempts to grab the pool before it actually sees it. Line 25 in b7873f4
Maybe switch the pools from being in code to using vanilla's worldgen json like this? Or maybe try initializing your pools at mod startup instead of during worldgen. In fact, doing it at startup is a better idea so that your coded pools won't registry replace people's datapack attempt to override the tower pools to add new pieces. |
I am seeing this issue, and it causes the game to hang. I have to kill the process if it happens. |
Using the latest version of the mod keeps throwing this... ****************** Blame Report 1.9.2 ****************** |
@ldrae Sorry for the ping, but this issue seems to be causing lag in Enigmatica 6, could you please have a look if you haven't already? :) |
jigsaw blocks pointing to a missing pool shouldn't ever really cause lag. I would check other mods instead or try removing mods see which could be the cause |
Alright, but it'd still be nice to get this cleaned up to allow for easier troubleshooting 😄 |
I seemed to fix this with without using datapacks. See #8 |
I need to mention that even if you remove the mod, the jigsaw issue still happens. I hope my fix will solve this. |
I was running my mod Blame with Towers of the Wild and it found several tower pieces weren't actually spawning. Here's all the pieces it found summarized. Hopefully this helps! :
log:
latest.log
The text was updated successfully, but these errors were encountered: