No errors in the log, recipe not available in-game.

gooblob.json, located at resources\assets\oreflowers\recipe:

{
    "type": "minecraft:crafting_shaped",
    "pattern": [
        "xx",
        "xx"
    ],
    "key": {
        "x": {
            "item": "oreflowers:oreflowers1",
            "data": 4
        }
    },
    "result": {
        "item": "oreflowers:sticky_goo",
        "data": 0
    }
}

(I also tried resources\assets\oreflowers\recipes but another thread indicated that that was wrong).

 

Also, I love how we went to enums for everything, only to then change to JSON files for recipes where raw metadata is used.

new ItemStack(oreFlowersDesert1,1,EnumOreFlowerDesert1._4AVELOZ.getOrdinal()

Was so good in 1.10 and 1.11.

Edited August 27, 20178 yr by Draco18s

First, I believe "recipes" is correct, as that is what I am using currently. Either that or both "recipe" and "recipes" works?

I just tested what you have here, and can confirm that my test recipe (basically identical) also did not load, and did not error either. You're not crazy!

I have a similar recipe that uses a shaped ore recipe that works though, so try changing the recipe type to "forge:ore_shaped".

If it works, I'm guessing you might have another problem: the recipe book will try to place the items in like "xxx", "x--", "---". If it does, there are a couple problems with forge that need to be fixed.

 

Nope, still not working.

I even tried setting the recipe to "xx ","xx ", "   ", using # instead of x, removing the data:0 on the result (the output item doesn't have subtypes).

 

No dice.

16 minutes ago, Eastonium said:

the recipe book will try to place the items in like "xxx", "x--", "---". If it does, there are a couple problems with forge that need to be fixed.

Also didn't appear to be true.

Finally figured it out.

Turns out my data value was off by 1...making it want a flower variant that didn't exist (pure coincidence).