1.9-3.0.4 complains about crusher recipe
kreezxil opened this issue · 3 comments
I've deleted it on the client side like it suggested and still says it. The game doesn't appear to be affected tho. I have yet to build the crusher recipe to see what happens.
18:42:02] [Client thread/INFO]: Registered plugin: com.setycz.chickens.jei.ChickensJeiPlugin [18:42:02] [Client thread/INFO]: Registered plugin: com.zerofall.ezstorage.jei.EZStoragePlugin [18:42:02] [Client thread/FATAL]: [NeoTech] CrusherRecipe json is corrupt! Please delete and recreate! [18:42:02] [Client thread/FATAL]: [NeoTech] CrusherRecipe json is corrupt! Please delete and recreate! [18:42:02] [Client thread/FATAL]: [NeoTech] CrusherRecipe json is corrupt! Please delete and recreate! [18:42:02] [Client thread/FATAL]: [NeoTech] CrusherRecipe json is corrupt! Please delete and recreate! [18:42:02] [Client thread/FATAL]: [NeoTech] CrusherRecipe json is corrupt! Please delete and recreate! [18:42:02] [Client thread/FATAL]: [NeoTech] CrusherRecipe json is corrupt! Please delete and recreate! [18:42:02] [Client thread/FATAL]: [NeoTech] CrusherRecipe json is corrupt! Please delete and recreate! [18:42:02] [Client thread/FATAL]: [NeoTech] CrusherRecipe json is corrupt! Please delete and recreate! [18:42:02] [Client thread/INFO]: Registered plugin: com.dyonovan.neotech.api.jei.NeoTechPlugin [18:42:02] [Client thread/INFO]: Registered plugin: com.setycz.AnotherDustsMod.JEI.AnotherDustsJEIPlugin [18:42:02] [Client thread/INFO]: Registered plugin: cyano.basemetals.jei.BaseMetalsJEIPlugin
Interesting. Did you delete the entire config directory for Neotech? Seems to be an issue loading
Yes I did do that just in case
-----Original Message-----
From: "Paul Davis" [email protected]
Sent: 3/31/2016 8:45 PM
To: "TeamBR-Modding/NeoTech" [email protected]
Cc: "kreezxil" [email protected]
Subject: Re: [TeamBR-Modding/NeoTech] 1.9-3.0.4 complains about crusher recipe(#271)
Interesting. Did you delete the entire config directory for Neotech? Seems to be an issue loading
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
