Choonster

If an item has subtypes like Stone and Dirt do, you need to specify the metadata using the data property when using it in a JSON recipe's ingredient. Look at some of the recipes that use Planks or Stone (e.g. minecraft:acacia_boat) to see examples of this.

If you're following my example, the COLOR property is stored in the metadata and as such is already set when Block#getActualState is called. The FACING property is stored in the TileEntity and is the only property that needs to be set in your override of Block#getActualState.

No. Each version of Forge only supports a single version of Minecraft and won't work on any other version.

Unlisted properties aren't used to determine which model to render for a block, they're used by custom block models to determine how they should render. The correct solution here (while keeping a single block) would be to store the extra data in a TileEntity and use regular properties that have their values set in Block#getActualState. Though Mojang is moving away from having a single block for all colours with The Flattening in 1.13, so it may be best to split the colours into separate blocks now (as Cadiboo suggested). I have an example of a block with a colour and a facing here: Block, TileEntity, blockstates file

There are still some Vanilla methods like Entity#getName that perform translation but aren't client-only. These use the deprecated net.minecraft.util.text.translation.I18n and I don't think there's any real alternative.

I've never played Warframe, so that's not me.

On Unix-like systems, look in ~/.gradle rather than %USER_HOME%\.gradle for the Gradle caches.

Forge 1.12.2-14.23.5.2779 deprecated ReflectionHelper and changed the methods in ObfuscationReflectionHelper to only require an SRG name rather than both an SRG and MCP name. This is what @quadraxis was talking about.

Those are builds for 1.3.2 from 2014, they're not for 1.13.2.

What do you mean "the forge version"? The only place you should download Forge from is the official Files site (https://files.minecraftforge.net/). There are no 1.13.x versions available there.

Where did you download this from? There are no public releases of Forge for 1.13.x yet, and Forge is only being developed for 1.13(.0) at the moment.

This is incorrect. Method and field names are reobfuscated from MCP to SRG names when you compile, but MCP and SRG class names are the same. Forge deobfuscates Minecraft from Notch to SRG names at runtime.

Which part didn't you understand? Do you know how to create the replacement recipe? Do you know how to override a registry entry?

Did you read the post I linked?

I haven't dealt with 1.13's data packs yet and I'm not at my computer to test anything, but a possible issue is that your recipe file has .JSON as the extension rather than .json. If changing that doesn't work, post your log (I think it's logs/latest.log in the game directory) using Gist/Pastebin. There may be something useful in there.

@Config does work with Maps that have String keys, the Map becomes a category in the config file and the key-value pairs become properties. See here for an example of this.

If you use a static event handler method, you need to register the Class object with the event bus rather than an instance of the class. See the documentation for more information.

Instead of calling MinecraftForge.EVENT_BUS.register or using the @EventBusSubscriber annotation, you call MinecraftForge.ORE_GEN_BUS.register.

You need to register your event handler with MinecraftForge.ORE_GEN_BUS instead of MinecraftForge.EVENT_BUS.

As it says in the doc comment of OreGenEvent:

When using @Mod.EventBusSubscriber, your event handler methods need to be static. Your lootLoad method isn't.

Both of those are valid. The important thing is that you call that constructor, it doesn't matter where you get the values from.

This particular ArrayIndexOutOfBoundsException is caused by calling the ItemAxe(ToolMaterial) constructor with a non-Vanilla ToolMaterial as it tries to look up the attack speed and damage using the ToolMaterial's ordinal as an array index. These arrays only have as many entries as their are Vanilla ToolMaterials, so any modded ToolMaterial's ordinal causes an ArrayIndexOutOfBoundsException. The solution is to use the ItemAxe(ToolMaterial, float, float) constructor and specify the attack damage and speed yourself.

If your item uses the container item system to damage itself (like my ItemCuttingAxe), you don't need to create your own recipe class; just use one of the existing Vanilla or Forge classes. You only need to damage the item in the recipe if you're using an item from Vanilla or another mod.

Your lang file needs to be called en_us.lang (with an underscore), not en-us.lang (with a dash).