larsgerrits

You can register IRecipes just fine, but you need to reference them from a JSON recipe file. To register a custom IRecipe you need to get a RecipeType usingRecipeType.get (look at VanillaRecipeTypes). You also need to register a custom IRecipeSerializer using RecipeSerializers.register. RecipeSerializers also contain the registering of all vanilla serializers. To use your custom IRecipe, set the type of your recipe to the ResourceLocation you specified from YourIRecipeSerializer#getName.

You don't. When the data changes on in the GUI, you send a packet from the client to the server containing the new information. The server will receive that packet and pass it to the packet handler together with the player, where you can verify if the data is correct (to prevent cheating) and set the capability data.

You don't have to with Java 8+. @DcZipPL don't provide copy/paste code like that. He doesn't learn anything from it and it's actually wrong in multiple places. @TheHex create your Items in a RegistryEvent.Register<Item> event handler instead of a static initializer.

Look at at net.minecraft.command.Commands. It registers all commands there and you can open each one of them to see how they work.

You shouldn't even have had that in the beginning, remove it. How are you building your mod?

https://github.com/MinecraftForge/MinecraftForge/issues/5545 As Lex said, the current fluid system is completely broken, and they won't add support until 1.14. So you can try to figure out how to use the vanilla system, otherwise you're out of luck.

Yes. Just pick another profile using a different version of Forge.

Why are you using LWJGL 2? Minecraft updated to LWJGL 3 in 1.13.

Fluids are going to be completely reworked. You'll have to wait until Forge adds compatability.

mcServer is probaby null here.

I thought it was a vanilla method patched by Forge... My mistake!

Mojang obfuscates the vanilla source code. Forge uses a tool called MCP which supplies names for each variable/method/parameter. However, those names are supplied by the community, which is why there are consistency issues throughout the code.

1.7.10 is no longer supported on this forum due to it's age. Update.

BTW, this is not how you ask for help...

The docs explain everything for WorldSavedData. What do you need help with?

That's a lot of variants... (85781777534284265411908227168123262515778152027948561985965565037726945255314758 variants)

Always post the crash log whenever you crash.

1.7.10 is no longer supported on this forum due to its age. Update.

Don't necro old threads. This is a 5 year old thread and completely unrelated to your problem.

1.7.10 is no longer supported on this forum due to it's age. Update.

Why did you comment out the "apply plugin: 'forge'"? It needs to be there. Also, stop modding for 1.7.10. It's not supported anymore because of its age.

Uhmmm... How does your build.gradle look like?

So it's actually the same as before (gradlew setup) however I think something got corrupted because a clean clone and fresh setup works again. EDIT: It was caused by the Gradle daemon getting locked up. This has now been fixed in the newest ForgeGradle version.

I have the MDK working fine, it's about contributing to Forge (submitting PRs).

Hi, I've been wanting to contribute to Forge for 1.13, but I can't seem to setup a proper workspace. I couldn't find anything online on how to setup a workspace with the new ForgeGradle and everyting I've tried leads to the Forge source missing a lot of imports. Can anyone list out the steps to setup a Forge workspace?