Draco18s

You can still get the current value in the way that D7 said when drawing the hud.

No. Because you're bypassing the block-break system in PlayerInteraction.java

Yes. Do whatever it is you're doing on the server thread. If you can't, then no, you need packets.

try {EntityPlayer p = Minecraft.getMinecraft().player; You're doing everything on the client. The server then synchronizes everything and overwrites your changes.

Show more of your code. There are several reasons why this might fail, but in order to determine which one of those it is, we need to know where this code is.

I'm not up on the status of various tutorials. I generally do things on my own and ask for help here. Occasionally I hit up Choonster's github for things I know he's already done. https://github.com/Choonster-Minecraft-Mods/TestMod3/

so what would you recommend? would you be able to point me in the right direction? MrCrayfish. Bravo.

You can use item model display tags (in the JSON file) for this.

Seriously? Can't you people even look at the Enum? Or other blocks that use it? EnumFacing.getFront(meta) /** * Get a Facing by it's index (0-5). The order is D-U-N-S-W-E. Named getFront for legacy reasons. */ public static EnumFacing getFront(int index) { return VALUES[MathHelper.abs(index % VALUES.length)]; }

Did you register your event handler?

Too easy for two different mods to try and use the same mod ID

There are no second level recipes, everything's "first level." If you have an item that is made up of non-resource items (say bookshelves: made out of books) you have to use a lookup table to figure out how much paper is involved: you know how many books the bookshelf is made out of, then multiply by the amount of paper in each book.

Actually you use use .isAir() instead. Mods may add blocks that they wish to be treated as air (for example, Greg's Lighting's spotlight, which creates a column of blocks that are light sources, but should otherwise be treated as air).

Yeah, well, 1.12 changed a lot o' shit compared to 1.9. Like, everything. 1.9 and 1.10 were fairly close, but 1.11 changed how items and blocks are registered, and 1.12 changed recipes and achievements.

You already have the position, it's the position that isn't working. Now you need to get the facing (which side of the block that was hit by the raycast) and offset that position by 1 in that direction.

Like any other property: "name" : "value" { ... }

Not working...how?

http://mcforge.readthedocs.io/en/latest/concepts/sides/

This is what texture offsets are for. Rather than binding a different texture, you offset the location of each box to use a different part of the same texture.

For reference, the mcmod.info files has no bearing on whether or not it works. It's just a easy-to-read text format of the details of your mod so that services like Curse can display that information without having to decompile the entire jar. Good practice to change it, but doesn't actually do anything.

private Item getItem() { return this.getItem(); } Yeugh. You realize this is an infinite loop, right? Also, public ItemStack getItem(World worldIn, BlockPos pos, IBlockState state) is deprecated with the note // Forge: Use more sensitive version below: getPickBlock You should probably follow that advice. It also appears you've overridden a bunch of functions that you don't need to. It's hard to tell. Start your own thread, dude. Don't hijack someone else's thread to ask them how they did something. Also: Read the Docs

Seeing what? ModelLoader being client side only? import net.minecraft.client.renderer.block.model.ModelResourceLocation; import net.minecraftforge.client.model.ModelLoader;

The hashtag there means that the method is not static. BlockPos.offset(...) implies that you can just call it like that: foo = BlockPos.offset(bar); When that is in fact not the case, you need an instance of BlockPos instead: BlockPos foo = ... foo.offset(bar);

I linked you to an example. It is an event, it needs to be in a client-side event handler.

A mod ID that is only 2 characters long is not really a good idea. It's best if you make it at least 3, might be related to your other problem. Also, if you have a completely blank row or column in a recipe (cough, you do) just omit it, or it forces the recipe into the top two rows.