Minecraft Forums

If you're experienced in Java, you'll get used in no time. The basic tutorials on how to setup your packages and the main class of your mod are found on youtube and google, it's pretty easy. Don't go through the entire Minecraft source, you'll have to get multiple puke buckets ready and it can't be good for your health. However, I'd recommend that you learn how to do the most basic stuff (blocks, items, armor, etc) to get used to this new environment. After that, you want to get used to the Forge API. By that, I mean how to handle your stuff over the event bus, tile entities, and much more. By then, get a clear idea of what mod you want to make and learn whatever you need to make it.

If you have more questions, I'd be happy to give you a hand

Check mr crayfish's Chanel he explains stuff really well

Call registration methods from the 3 main parts of the FML life cycle. Each must be annotated with @EventHandler, must be public static and in your @Mod annotated class. Many modders consider it good practice to have separate classes for registering each type of thing (entities, blocks, items, etc.)

Yes, the @Mod annotation tells the Forge Mod Loader which file is a valid mod. Inside it you will need methods that accept a single event argument.

Let me describe some for you:

FMLPreInitializationEvent

Anything you do from the method that accepts this event as an argument can be safely added to the game. This includes registering all blocks, items, itemblocks, and entities, among other things. Entity renders should be registered in this phase as of 1.8.

You will use GameRegistry methods added by Forge to register almost everything. For example, calling GameRegistry.registerBlock(Block myBlockInstance, String unlocalizedName) in 1.8.x or 1.7.10 will add a block to the game. Hopefully you set its other attributes before doing that. In 1.9 the GameRegistry class becomes even more flexible and is used to register dimensions and biomes as well.

FMLInitializationEvent

This method should register event handlers (that's another topic) and block and item rendering. Also register crafting recipes here as of 1.8.

FMLPostInitializationEvent

... I never use this. I suppose many mods do if they want to query all the blocks or liquids that have been added, but I've never had a need for that myself. Anyone care to elaborate?

Here's one example of an @Mod annotated file that calls a Config class, Item and Block registration class, Entity registration, rendering, event handlers, etc. See ExtraGolems.java

The proxies are another core part of modding setup. CommonProxy is shared code between the client and server. All blocks, items, entities, and pretty much everything content- or logic-oriented should be shared. For client only things, use the proxy. This mostly includes rendering and name localization.

1.7.10? Use 1.8.9 or 1.9 Unless you want to play it in FTB or something.