larsgerrits

He literally says it: "You cannot place code outside of methods". Place your code inside a method...

Your entity registry code is f*cked up... Issues with it are: - You register every Entity atleast 10 times. - What is up with those Entity IDs? - You messed up the trackingRange and updateFrequency parameters in some of the calls to registerModEntity() . - Making a method for registering entities is redundant. Why make a method with 1 line of code, instead of a single line of code? No methods needed. - And if you still decide to make a method (just don't), actually use the parameters...

Don't add it as a parameter in the getItemFromBlock() method, but as an parameter of the ItemStack constructor.

Override getRenderBoundingBox() and make it return a bigger AxisAlignedBB than the default (1x1x1).

Why do you have your own getTotalWorldTime() method? It is a method in the World class you have to use, and not make your own.

Are you sure youo want the rotationPointX ? I think you mean the rotationAngleX .

With registerModEntity() you have mod-specific IDs, so no random number generator or findGlobalUniqueEntityId() , just use ID 0 for your first entity, 1 for the second etc.

Those are the String used as keys in the OreDictionary. You can get an ArrayList<ItemStack> using OreDictionary.getOres() and as a parameter the Strings you get, to get the ItemStacks that can be used for the recipe. BTW, what are you trying to do? Are you sure there isn't another way of doing what you are trying to do?

Doors aren't BlockContainers, and they don't have an associated ItemBlock. So you'd have to rethink your logic (Hint: getPickBlock . Please use that, it is your only way to do it properly..

Yes, because you have to pass it as a parameter. The first one is the Item/Block, the second the amount to be dropped (defaults to 1), and the third the damage/metadata.

And what do you want to tell us with that?

You get the Block using world.getBlock() . You can remove the Blocks.blocksList because it doesn't exist anymore and isn't needed. And please, rename your variables properly, it will be much easier to understand the code and what it does.

It is still called ForgeMultiPart. ChickenBones didn't name it 'wrong', he just chose to have 'Forge' in the name, but it doesn't have anything to do with Forge.

When another block that gives of light gets placed, Minecraft updates the light around it, and resetting the light values set from worldObj.setLightFor() .

Then you don't need TileEntity.createAndLoadEntity() and that world.getBlock().createTileEntity();

Use World#setBlock() to place the block, and also the TileEntity if that block has one. You can then call TileEntity#readFromNBT() on the TileEntity gotten from World#getTileEntity() .

I don't you have to use a custom renderer for this. Try overriding requiresMultipleRenderPasses() to return true;

You probably had to refresh your project in Eclipse to make Eclipse aware of the changes and actually make MC aware not to load the assets.

If the gui has a container, you can use the container to sync the data. If you don't, you probably have to use packets to sync the data.

Yes, metadata is saved automatically. But what Eloraam has done there is not metadata, but rather just a simple field in TileMachine that has to be saved to NBT. The vanilla furnace does use metadata to store it's rotation.

You have to set the damage (metadata) of the colored glass in the ItemStack.

You only open the gui on the client side. You have to use packets to tell the server to open the gui.

You have to link it to the .gradle folder in your user directory.

Caused by: java.lang.IllegalArgumentException: Cannot get property PropertyInteger{name=level, clazz=class java.lang.Integer, values=[0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15]} as it does not exist in BlockState{block=mw:underwater_plant, properties=[variant]} at net.minecraft.block.state.BlockState$StateImplementation.getValue(BlockState.java:167) ~[blockState$StateImplementation.class:?] at net.minecraft.block.BlockLiquid.getLevel(BlockLiquid.java:64) ~[blockLiquid.class:?] It looks like it has something to with a method in the BlockLiquid class. Look at that method on that line and look what is causing the crash.

System.out.println.