1. They have a javadoc, no need for anything else.
2. Lots of tutorial for that out there, it didn't change since 1.3.
3. Didn't change since...I began Minecraft modding.
4. There is nothing in Minecraft nor Forge doing this. Do it however you want, it is complete freedom here.
5. That is a basic topic. Don't know how you can code anything in Minecraft without knowing this already. Search for NBTTagCompound in Minecraft source.
public BlockVillage(int par1) {
super(par1, Material.iron);
this.nameNumber = (int) Math.floor(this.townNames.length * Math.random());
}
A block is only created once in the entire game. You should decide the name when the block is placed.
You have only 8 town names, you could use metadata and change the meta values.
Vanilla enchantments are tested against the item's class.
ItemSword for sword enchantments, ItemTool for tools'...
If you don't use the right item class, you are on your own to fix it.
No, you don't, as confirmed by your screenshot.
Forge isn't in your "Forge" module (this is your naming, and it is inaccurate). It's in the external librairies. And those can be shared between projects without duplicate.
Did you check that your item set your paintings entity ?
Did you check that your paintings entity contains one of the paintings value ?
Did you check that your paintings entity is being rendered with your renderer ?
I shouldn't have to ask those questions only to get a useful error report.
Yes, changing the method works. Calling it, not.
What you want is changing the block to your own block, with
world.setBlockId(x, y, z, newId);
/----------------------------------------------------------/
public class ColoredBlock extends the-original-block-class{
@Override
public int getColorMultiplier(){
return your-own-value-here
}
}
Your crash log says that the element in your blocksList array is null.
But the real question is why do you make an array of 4096 elements, when you only want to change one block.
Calling yourself Block#colorMultiplier isn't doing anything, by the way.
Then what Draco18s said doesn't apply here.
You should have a .gradle/ folder in your setup, check the log inside, it should explain what happened.
If there is no error, post your build.gradle file.