Draco18s

Your prior code should work. I don't see anything wrong with it.

Your prior code should work. I don't see anything wrong with it.

Note that Survival Single Player is still a Client/Server relationship. It's a local server thread with a single player connected.

Note that Survival Single Player is still a Client/Server relationship. It's a local server thread with a single player connected.

Technically a 1x1x1 block can have bounds that exceed 1x1x1, but only in the +Y (skyward) direction. See: BlockFence

Technically a 1x1x1 block can have bounds that exceed 1x1x1, but only in the +Y (skyward) direction. See: BlockFence

Item item = Item.getItemFromBlock(block); is returning null because you didn't register an ItemBlock for your block. That no longer happens automatically.

Item item = Item.getItemFromBlock(block); is returning null because you didn't register an ItemBlock for your block. That no longer happens automatically.

Well, the line ClientRegistry.bindTileEntitySpecialRenderer(TileEntityTest.class, render1); is outside a method, which is Not Correct.

Well, the line ClientRegistry.bindTileEntitySpecialRenderer(TileEntityTest.class, render1); is outside a method, which is Not Correct.

Largely speaking, everything is still correct. There's been a reduction in buses for 1.9 (there's only one now, the split wasn't very meaningful) and some event names/properties have changed, but it should still be sufficient to get started.

Largely speaking, everything is still correct. There's been a reduction in buses for 1.9 (there's only one now, the split wasn't very meaningful) and some event names/properties have changed, but it should still be sufficient to get started.

You need an event.

You need an event.

Its not recognized as a written book because it's not an ItemWritableBook.

Its not recognized as a written book because it's not an ItemWritableBook.

In that case, it probably was. Non-running TEs (furnaces would still have an update tick) would run pretty fast, but there is memory overhead. Note that we're not saying "Don't use a TE for this" but "TEs do require extra resources: be careful."

In that case, it probably was. Non-running TEs (furnaces would still have an update tick) would run pretty fast, but there is memory overhead. Note that we're not saying "Don't use a TE for this" but "TEs do require extra resources: be careful."

So remove that? Seriously!?

So remove that? Seriously!?

If you're using a custom crafting bench, absolutely. I've got a "Sifter" machine that takes inputs of size 8 and produces an output of size 1 (turns Tiny Dust into Dust). Ditto for a "compactor" (turns Snowballs into Snow, etc)

If you're using a custom crafting bench, absolutely. I've got a "Sifter" machine that takes inputs of size 8 and produces an output of size 1 (turns Tiny Dust into Dust). Ditto for a "compactor" (turns Snowballs into Snow, etc)

I've accidentally turned the entire world into chests once. It was awful.

I've accidentally turned the entire world into chests once. It was awful.

You still need to register your sound event, like blocks and items and rendering, sounds still need to be registered.