#How to change Every Compat recipes?

31 messages · Page 1 of 1 (latest)

ivory gorge
#

Making a large modpack and trying to clean up recipes, and I can't seem to modify this one because I can't follow its file path. How do I remove it? I only want the last recipe to exist.

indigo jayBOT
#

hmm. everycomp:recipes/fd/cutting/ars-nouveau/archwood_log.json that's the file for the recipe

Jump

[Go to message!](#programming-🖥️ message)

ivory gorge
#

If found this message referring to the same issue, but I don't want to install crafttweaker.

#

How do I remove the recipe?

simple mirage
#

datapack

ivory gorge
#

Yes I'm doing datapack things.

#

But where is the .json?

simple mirage
#

enable debug resources to see the path

ivory gorge
simple mirage
#

ore use JEI

ivory gorge
#

But the path can't exist, because I can't make a folder named everycompat:fd

simple mirage
#

that is the path

ivory gorge
#

But I can't name a folder that.

#

: is not a valid folder name character.

simple mirage
#

all ids are like that

#

: means the namespace

#

root folder

#

mod id

#

whatever you want to call it

ivory gorge
#

So I should make the file path be

everycomp**/**fd/cutting/quark/ancient_log.json

#

?

simple mirage
#

no

#

vanilla recipes are in minecraft/recipes/smoing/salmon.json

#

for example

ivory gorge
#

Yes.

simple mirage
#

just make sure your datapack loads first

ivory gorge
#

So if my datapack loads before EC, it will prevent EC from generating recipes that are already covered?
Is that what you're saying?

simple mirage
#

no im saying the exact opposite, unless you alter the recipes EC copies in whichcase it would need to be before

ivory gorge
#

My apologies, I have figured out my error and the situation is corrected now. Thank you.

I had gotten this far after months of working on this modpack's datapack by mostly tracking down the original mods' .json files, and I was a bit lost with EC because its .jar doesn't have filepaths to follow, and I while I am able to follow the in-game file path, because it's not exactly the same I had been more using it for pointing in the right direction rather than reading it properly.

That's on me. Thanks.