EdgarAllen

I setup a basic animated block using vanilla models(not obj or b3d). It's a lever that looks like a repeater and slides to the other side when you click it. The code to setup the animation for the block seems fairly straight forward. I commented notes into the code; which could have wrong info, so don't take it as gospel. The json files are still a bit of a mystery to me. I get parts of them, but I still have a bit to figure out. I'll try to write up some proper documentation on them once I learn their ins and outs a bit more. Here's the github if you want to check it out and toy around.

The one from pWn3d.

Was talking to the OP. Should have quoted him I guess.

Have you used animation state machines before? Is this the grammer definition you mentioned? grammar.js -> engine.json

Try isFullCube

markDirty has the exact same call usages as in 1.6.4. The only thing that has changed besides the name, is the comment; which isn't anything to go by.

markDirty()

player.addChatComponentMessage(new ChatComponentTranslation("blah.random.comment"));

At the end of update entity, you are ninja editing an itemstack. You probably need a call onInventoryChanged/markDirty to have those edits sync.

try adding a call to world.markBlockForUpdate when your state changes and you want to sync. If your state changes in a gui/container, onContainerClosed is a good spot.

There is no TileEntity for the Workbench. All the magic happens in ContainerWorkbench.

I think what you are looking for is IExtendedEntityProperties. This post over at minecraft forums has a quick run down of how to use it. http://www.minecraftforum.net/topic/1952901-eventhandler-and-iextendedentityproperties/#entry24051513

Would that actually work in LivingUpdateEvent? There is a lot of stuff that is updated between when your code runs and when the xpOrbs do their thing in onCollideWithPlayer. Depending on what is updated there might be a difference in what orbs you collide with and what orbs are actually picked up. If you are targeting 1.7.2, I'd add a hook to onCollideWithPlayer that fires an XpOrbPickedUpEvent. If you get it pulled now, it'll be in when the recommended build is set. That way you'll be all set going forward, not to mention any other mods that may want to mess with xpOrb pickups.

I came across that last night. It does fix the gui problems I was having.

Personally, I'm just waiting till forge pulls in the commit. I don't expect it to be more than a couple days. I know my gui code is correct. In the mean time I just did a mock that has it's inventory filled with random items so I can test things without having to open the gui.