Hello, wonderful modding community!
Today, I bring you a tale of such woe that I must insist you be firmly seated before I can begin - otherwise, your sympathetic despair may cause you to collapse.
Well, it's really not that bad (aside from spending nigh on 12 hours trying to get a working JDK for use with Forge because I'm a masochist that doesn't want to give Oracle my info).
What it boils down to is that for some unknown reason Forge isn't recognizing my recipe JSON.
Now would be a good time to note that I haven't touched Forge since 1.12.2, and I'm one of those poor fools who was taught to manually register everything (via GameRegistry.register) and to put everything into proxies. I'm now taking the time to re-learn how to write mods *properly*. Problem is, one of the things that changed out from under me was recipe registering. Supposedly, you just create a recipe file (in JSON format) with the type of recipe, recipe pattern (like the old registering pattern), key (also like the old registering key), and result.
I've already gone and created the associated item and block, and triple-checked the registry IDs.
assets/agab/recipes/example_ore.json (the recipe file):
((don't ask about the MODID, it's not important other than that it's consistent))
I can confirm that the item and the block are both appearing in the game, but for some unknown reason this JSON isn't loading, and I can't find any mention of it in the log.
For reference, I'm using Forge 1.15.2-31.1.0, along with Eclipse 2019-12.
Relating to that statement about being a masochist, I'm using AdoptOpenJDK ver. 1.8.0_242-b08 with the HotSpot JVM ver. 25.242-b08 on a 64-bit machine (that last bit was ~2 of the 12 hours lol).
I'd include a pastebin for debug.log, but uh... apparently it's like 3.3 meg??