Draco18s

The L is part of the internal signature stuff. I'm not sure what it means, only that when I was doing ASM coremodding (way, way back), it showed up there too.

What the bloody fuck is all that garbage sitting OUTSIDE ALL METHODS!?

Read: you can just go look at the class and its available constructors...

Registry names come in two parts. You supplied half. Forge automatically supplied the other half, which was wrong for what you're trying to do.

Problematic Code #14

The class that is causing the problem is your BlastingRecipeSerializer.

You don't need to implement or extend anything. https://github.com/Draco18s/ReasonableRealism/tree/1.14.4/src/main/java/com/draco18s/harderores/network

Or you didn't set up your environment properly.

If you want a "it feels like 1.7.10" method of registering stuff, grab these: https://github.com/Draco18s/ReasonableRealism/blob/1.12.1/src/main/java/com/draco18s/hardlib/EasyRegistry.java https://github.com/Draco18s/ReasonableRealism/blob/1.12.1/src/main/java/com/draco18s/hardlib/client/ClientEasyRegistry.java Then you'll want to do 3 things: 1) change the package name 2) make these classes your client and server proxies 3) remap all Hardlib.proxy calls to WhateverYourModIs.proxy Alternatively, look at how I did it in 1.14 so that (2) and (3) aren't necessary. But you will have to deal with things being renamed. https://github.com/Draco18s/ReasonableRealism/blob/1.14.4/src/main/java/com/draco18s/hardlib/EasyRegistry.java

https://gist.github.com/williewillus/353c872bcf1a6ace9921189f6100d09a#nitty-gritty-random-things-ctrlf-section

Best I got. https://gist.github.com/Barteks2x/41122efc766afdd47aeb457a3c19b275#gistcomment-2989342

Look at existing usages? ICraftingRecipe is as far back as you should really go, which returns IRecipeType.CRAFTING from getType, distinguishing it from SMELTING, BLASTING, SMOKING, CAMPFIRE_COOKING, and STONECUTTING.

If an issue ever arises where someone suspects a bug in very popular software vs. their code, I will always assume its "their code" and not the popular software. Are there bugs in Intellij? Probably. But something like this would get noticed and fixed before it ever got released. This was literally the only helpful thing you said in this thread.

...that's the version that he says works...

What version of Minecraft? Have you looked at how Vanilla does it?

Everything else it used to take is now in the toml file. Registration of things is also massively changed.This goes for nearly everything that was not already previously a IForgeRegistryEntry object (there used to be about 5 or so registries: blocks, items, enchantments, biomes, and one or two others, there's now 35 or so). Config stuff also changed, but as I haven't poked at them in 1.12 nor 1.14, I don't know what's different.

Find any event in your IDE Right click on it Open Type Hierarchy Select the Event class Right click, Open Type Hierarchy or Right click, Focus on Event

Question: Did you write your own mod or Do you just run a modded server?

Here's an example: https://github.com/Draco18s/ReasonableRealism/blob/1.14.4/src/main/java/com/draco18s/hardlib/api/recipe/RecipeTagOutput.java#L180 https://github.com/Draco18s/ReasonableRealism/blob/1.14.4/src/main/java/com/draco18s/hardlib/EasyRegistry.java#L182

No, it said create a thread in Support & Bug Reports. I'm not sure why Lex decided that that should happen, but there you go.

The screenshot you shared is useless because you did not expand the blocks and items directories to show the files inside them. I know you said that they're named "black_stained_clay.json", but we can't actually see that.

By the way, you can really simplify your item model: https://github.com/Draco18s/ReasonableRealism/blob/1.14.4/src/main/resources/assets/harderores/models/item/sifter.json There is literally no reason ever (almost) to actually override the display tag.

Could be. Open an issue on their git. https://github.com/MinecraftForge/MinecraftForge/issues/

You can also just apply it to a class. But it requires that the field names match the object's registry name exactly (except for cAse).

I haven't messed with it in 1.14, but you should be able to write a new recipe (with the same name) that lives at data.minecraft.recipes and it'll override the vanilla one. Not the same ingredients, the same name. SO to overwrite the chestplate you'd have to have a chestplate.json recipe with different ingredients/result.