[1.15.2] Exceptions being thrown in log preventing recipes in stonecutter registering
jarquafelmu opened this issue ยท 3 comments
The stonecutter in my modpack is having some issues with recipes not registering and being available. For example this is how stone looks in vanilla with the stonecutter
but because of the exceptions being thrown in the log (I believe this is the cause) recipes aren't being registered so now it can only do this
latest.log: https://gist.github.com/jarquafelmu/fbc0f0dc6537a1846b8bbf2eba9f3d09 (I would have used pastebin but the log was too big for it)
MC v1.15.2
Quark vr21-245
Example of an exception being thrown
[08Aug2020 20:15:13.816] [Server thread/ERROR] [net.minecraft.item.crafting.RecipeManager/]: Parsing error loading recipe quark:building/stonecutting/vertslabs/elder_prismarine_vertical_slab_stonecutter
com.google.gson.JsonSyntaxException: Unknown condition type: quark:flag
at net.minecraftforge.common.crafting.CraftingHelper.getCondition(CraftingHelper.java:225) ~[?:?]
at net.minecraftforge.common.crafting.CraftingHelper.processConditions(CraftingHelper.java:214) ~[?:?]
at net.minecraftforge.common.crafting.CraftingHelper.processConditions(CraftingHelper.java:203) ~[?:?]
at net.minecraft.item.crafting.RecipeManager.func_212853_a_(RecipeManager.java:56) ~[?:?]
at net.minecraft.item.crafting.RecipeManager.func_212853_a_(RecipeManager.java:37) ~[?:?]
at net.minecraft.client.resources.ReloadListener.func_215269_a(SourceFile:13) ~[?:?]
at java.util.concurrent.CompletableFuture.uniAccept(CompletableFuture.java:670) ~[?:1.8.0_232]
at java.util.concurrent.CompletableFuture$UniAccept.tryFire(CompletableFuture.java:646) ~[?:1.8.0_232]
at java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:456) ~[?:1.8.0_232]
at net.minecraft.resources.AsyncReloader.func_219557_a(SourceFile:71) ~[?:?]
at net.minecraft.util.concurrent.TickDelayedTask.run(SourceFile:18) [?:?]
at net.minecraft.util.concurrent.ThreadTaskExecutor.func_213166_h(SourceFile:144) [?:?]
at net.minecraft.util.concurrent.RecursiveEventLoop.func_213166_h(SourceFile:23) [?:?]
at net.minecraft.server.MinecraftServer.func_213166_h(MinecraftServer.java:731) [?:?]
at net.minecraft.server.MinecraftServer.func_213166_h(MinecraftServer.java:141) [?:?]
at net.minecraft.util.concurrent.ThreadTaskExecutor.func_213168_p(SourceFile:118) [?:?]
at net.minecraft.server.MinecraftServer.func_213205_aW(MinecraftServer.java:714) [?:?]
at net.minecraft.server.MinecraftServer.func_213168_p(MinecraftServer.java:708) [?:?]
at net.minecraft.util.concurrent.ThreadTaskExecutor.func_213161_c(SourceFile:127) [?:?]
at net.minecraft.server.MinecraftServer.func_195568_a(MinecraftServer.java:1464) [?:?]
at net.minecraft.server.MinecraftServer.func_195560_a(MinecraftServer.java:450) [?:?]
at net.minecraft.server.MinecraftServer.func_71247_a(MinecraftServer.java:363) [?:?]
at net.minecraft.server.dedicated.DedicatedServer.func_71197_b(DedicatedServer.java:212) [?:?]
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:613) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]
Can you try this with only quark? If this is happening it's because some mod is breaking the recipe conditions.
I'm not the orginial commentor, but people on the minecolonies discord are guesssing the incompatible mod is performant, and disabling performant's recipe caching is said to fix it