Draco18s

Packets. ((EntityPlayerSP)p) You can't just do this. This code will crash a dedicated server and even in single player it's reaching across logical sides. You must have the client tell the server "my user pressed this key" and the server needs to be the one to figure out what happens.

Then there's still a problem and you still need to debug it. "Not working" tells us nothing.

You haven't done this yet. I'll keep quoting this until you do it.

You haven't done this yet.

Ok, what about that line?

Edits to posts are almost completely unnoticed. They don't bump the thread, they don't mark the post as unread, and when someone sees a post with an error taking up 90% of it, they're likely to miss the "oh, nevermind" at the bottom. It also didn't help that I offered a suggestion, you said "yeah, I thought so too" and made no comment about it being solved then.

Oh. Try this: Replace "item": "minecraft:stone" with "item": "minecraft:stone","data":0 Stone is a metadata item and so just the item name isn't sufficient enough to fully specify the recipe.

Because I totally would have noticed that after there were new replies...

No

The only thing that can be null at that line is PacketHandler.INSTANCE, meaning your network stuff hasn't been set up properly.

Show your code

You can't register items to the OreDictionary if those items aren't registered with the game. You have to wait until after the RegistryEvent<Item> event (or do it inside that event when you register your item).

By "doesn't work" do you mean you can't craft it, or that it doesn't show up in the recipe book?

That means you have an infinite loop somewhere. Start using breakpoints.

Common OreDictionary Names All OreDictionary names for Minecraft items and blocks can be found in net.minecraftforge.oredict.OreDictionary. A full list will not be included here. Common prefixes already used in the OreDictionary include ore, ingot, nugget, dust, gem, dye, block, stone, crop, slab, stair, and pane. Common prefixes for modded items include gear, rod, stick, plate, dustTiny, and cover. Common suffixes in the OreDictionary include Wood, Glass, Iron, Gold, Leaves, and Brick. Common suffixes for modded items include the names of metals (Copper, Aluminum, Lead, Steel, etc.) and other modded materials. http://mcforge.readthedocs.io/en/latest/utilities/oredictionary/

As mentioned previously...

1.7.10 is no longer supported here. Update.

Usually every Minecraft update.

Yes, just register the items with the ore dictionary.

Yeah. Exactly. That's what we keep telling you: the server tracks everything and you have to synchronize what you do with the client. You can't just cancel the event on one side. If it only happens on one side you need to synchronize the effects.

No, that's the beginning of cargo cult programming. True understanding comes from looking at what is already available. You say you want to look at what we did, but how about you look at what Mojang did first?

https://en.wikipedia.org/w/index.php?title=Fallow

Notice that ITileEntityProivder methods use metadata while the methods in the Block class (added by Forge) use IBlockState

Make the non-moving part a standard block model. Make the moving part (and only the moving part) a TESR. I believe that FastTESR is sufficient, I am not current on that knowledge on account of having not needed a TESR at all in some time.