larsgerrits

False. You can write them in one order and read them in a totally different order, and it would still work.

These are the things that need to be in a GitHub project. If you have these you can simply clone it, run gradlew setupDecompWorkspace and than your IDE stuff and you have it. No more than that.

He is, he just hasn't put the @Override annotation above the method.

The stepHeight value is in the Entity class...

Set the stepHeight value to 1.0F for 1 block.

Judging by your last reply, you do not know how events work. You don't have to create new instances of an Event, but rather listen to the events posted by Forge/FML. Seriously, google it.

You do not know how events work. Google it, there are plenty of tutorials.

ItemPickupEvent.

ModelRenderer head = ... ModelRenderer horn = ... horn.setRotationPoint(head.rotationPointX,head.rotationPointY,head.rotationPointZ); Also, please stop sending me personal messages when you can ask here on the forums (others can use this information too).

First of all, rename the parameters to something human-readable. It will make it much easier to read and debug code. Second, look at the super classes you extend to make sure you're not missing something.

When using addChild you have to set the child rotation points to the head's rotation points.

Again, that's because your index value is wrong. You are initially setting the index value to the number of blocks in the structure (213), loop through the structure and increment the index 213 times, which results in a total of 628 blocks.

Check your index value.

I don't think that matters, as the rendering code would almost be the same.

[lmgtfy=minecraft forge sounds]Google is your friend.[/lmgtfy]

Latest is probaby your best guess for modders, recommended for users. Using the latest version assures you you got the latest additions, as you could've guessed .

Try updating your Forge, it fixed it for me.

I wonder if there's a mod with a GitHub project that does the same thing? (Hint: iChun's Hats mod, it has a GitHub project)

Never make a direct reference to a TileEntity over a long period! It can change and you will crash/bug out. Instead, just have a BlockPos variable you save to and read from NBT, and whenever you need to get the TileEntity, use IBlockAccess#getTileEntity() to get it. This makes sure you don't change a TileEntity that doesn't exist anymore.

Example: new ResourceLocation("modid:path/to/image/image.png"); That will result in assets/modid/path/to/image/image.png .

Entity movement is different from other Minecraft aspects. Entity movement has to be done on both client and server, instead only on the server. Making the entity moe on both sides resolves the lagging behind issue, and maybe the other ones too.

I'd say you follow the call hierarchy to see what it does, and look at the Minecraft classes for example implementations.

Try using the latest mappings, and see if that works. If that doesn't work, it may have to do with your internet connection.

* Where: Build file 'C:\WORK\mc_work\forge\build.gradle' line: 33 Show your complete build.gradle file, and line 33 of that file.