Draco18s

Burning: bx0010 (two values, shifted) Facing: bx0011 (four values, unshifted) Hmmm

Facing is 0-6 Active is 0-1 You can't just add those together. You need to offset one or the other to a free bit.

You can combine bools and integers in metadata. You just need to bitwise your data together.

EntityRegistry.registerModEntity(new ResourceLocation("hi","smile"), Entity303.class, "smile", 200, renderManager, 0, 0, false);

There is no way to know. For example, with squids, if you included the tentacles, would that be while they are close in against each other, or when they're spread out? Both? Animated along with the visuals?

That's putting textures in an assets directory. You can load them as a resource pack through code. I haven't done it, so I don't have a lot of information, I know I've seen things about it on the forum, though..

onArmorTick is common code, Minecraft.getMinecraft() is client-side-only, you can't do this. You have to set up a KeyInputEvent listener and send a packet to the server when the key is pressed. The server then checks to see if the action is valid, and if so, performs the resulting behavior.

Caused by: java.io.FileNotFoundException: ppextreme:models/item/itemsilverore.json

I have an item that uses NBT to determine what model / texture to use. The NBT values possible are defined by recipes, which are loaded after items. I tried calling ModelBakery.registerItemVariants and ModelLoader.setCustomMeshDefinition on the known result stack when the recipe was created, but it still left me with an untextured item.

GameRegistry.registerWorldGenerator(...)

It's "ravine" with an E. And yes, your problem is the InitMapGenEvent. That is not how you create new map generation features. You need to register them, not forcibly inject them into an event.

If you really want to do it in the single-call format (that is, your main class contains a new Block() line followed by a registerBlock() line) I'm in the process of updating my EasyRegistry class to 1.12, hasn't been pushed to git yet, but should be available in a day or so.

You can add resource packs via code.

I would love to have it.

Use Capabilities instead.

This is SideOnly(CLIENT)

Let me put it this way: Where are you calling EntityRegistry.registerModEntity?

Have you checked that the function runs on the server side. That's why you should use break points. Look at what the game is doing, make sure it is correct.

Put a breakpoint there. Does it ever get run?

The only button in your GUI that tells the server to do anything is the last one, TowncenterButtons.PLUS. None of the other buttons send a packet to the server and the server is the one in charge and the only one that can save data.

Probably never. And I don't think people are idiots, I just think that they can't be bothered to do even a cursory search.

Nope. Looks like I can use removedByPlayer instead and that correctly deals damage to the item.

1) STOP USING THE MODELMESHER (I am yelling because this is ALL OVER THIS FORUM for anything having anything to do with textures). This hasn't been correct since 1.8 2) http://mcforge.readthedocs.io/en/latest/concepts/registries/#registering-things

The stack itself takes the damage, at the end of the above function, the stack has the desired 1 damage. When it returns (back to the InteractionManager) it does not. The type of hoe didn't matter. I tried wooden, iron, and diamond.

I have this code in a block: @Override public void harvestBlock(World worldIn, EntityPlayer player, BlockPos pos, IBlockState state, @Nullable TileEntity te, @Nullable ItemStack stack) { if(stack != null) { Item i = stack.getItem(); if(i instanceof ItemTool) { stack.damageItem(2, player); } else if(i instanceof ItemHoe) { stack.damageItem(1, player); } } } While in survival mode, breaking the block with a hoe does not result in the item taking damage. When trying to debug, the item sustains the damage, this method returns, and as far as I can tell, no longer has the damage. Any other tool only takes 1 damage (???). I can't figure out what part of vanilla is overriding this effect. I know for a fact that this worked fine in 1.7.10, but I would need to go back and check 1.10 and 1.11