Draco18s

Yes it did. You just don't know why. The GameRegistry is now private and you need to use the Registry.Register<T> events instead. (Replace <T> with <Block> for blocks, <Item> for items, etc).

If your state is stored by the TE, you need to update the TE's value. SetBlockState only changes the metadata.

By the way, don't extend BlockContainer. It does nothing you want.

You still need to extend it and deal with it.

Cough extends PlayerContainer Cough

You need to add the FACING property to the container, eg: https://github.com/Draco18s/ReasonableRealism/blob/master/src/main/java/com/draco18s/ores/block/BlockMillstone.java#L48-L51 https://github.com/Draco18s/ReasonableRealism/blob/master/src/main/java/com/draco18s/ores/block/BlockAxel.java#L60-L63

For reference, this: @CapabilityInject(IItemHandler.class) public static Capability<IItemHandler> CAPABILITY_SET1 = null; Is how you define a capability. It's equivalent to CapabilityItemHandler.ITEM_HANDLER_CAPABILITY It is not the implementation thereof. For that, you need a new ItemStackHandler().

Yes. Go find the code that runs when F3 is pressed.

I would assume that that question answers itself.

What do you mean "any other way?" That's a really broad question.

Uh Items.BED?

Bingo

Blocks.BED does not have an item form.

This line: https://github.com/HalestormXV/Runic-Sorcery/blob/master/src/main/java/halestormxv/objects/blocks/BlockStones.java#L130 Says to drop the item "Mystic Cobble" While this line: https://github.com/HalestormXV/Runic-Sorcery/blob/master/src/main/java/halestormxv/objects/blocks/BlockStones.java#L123 Says to drop the item "Lupresium Cobble" combine that with this line: https://github.com/HalestormXV/Runic-Sorcery/blob/master/src/main/java/halestormxv/objects/blocks/BlockStones.java#L58 Which sets the item stack of the above item (mystic or lupresium cobble) to have a metadata value. For mystic cobble, this value is 4. You never register a model for Mystic Cobble with metadata 4.

Containers are automatically synced by vanilla.

It's specific to my mod, yes. It's just a metadata value. But rather than using "1" in 14 different places, I use SomeEnum.VALUE.metadata (The enum exists in the library, in case anyone ever wants to make something compatible with my mods, they only need the library's source, not the whole mod). Let me consume my mystical crystal ball which knows all about your error. Ah, yes, you need to fiddle the widget and contortionize the jiggerwat. That'll make it go away.

It's just a variant enum. The .metadata property just maps from that enum value to an integer. https://github.com/Draco18s/ReasonableRealism/blob/master/src/main/java/com/draco18s/hardlib/api/blockproperties/ores/EnumOreType.java

https://github.com/Draco18s/ReasonableRealism/blob/master/src/main/java/com/draco18s/ores/OresBase.java#L342

This is client side only and will absolutely crash a dedicated server: public static EntityPlayer getPlayerClient() { return Minecraft.getMinecraft().player; } This is server side only: public static EntityPlayer getPlayerServer() { return FMLCommonHandler.instance().getMinecraftServerInstance().getPlayerList().getPlayerByUsername(...); } As evidenced by the "get server instance" method name. This code could only ever work single player, which is why it's called "reaching across logical sides."

You're reaching across logical sides here. You can't do this, as as soon as you connect to a dedicated server, it wil. crash (because on the client FMLCommonHandler.instance().getMinecraftServerInstance() will be null). You must use packets for this. The reason it works in creative, is because in creative the server explicitly allows the client to alter their own inventory. In survival, this is expressly forbidden.

This is because there are two coal items: coal (meta 0) and charcoal (meta 1). These must always be specified. If you use type forge:ore_shaped instead, you can use the ore dictionary. e.g.: https://github.com/Draco18s/ReasonableRealism/blob/1.12.1/src/main/resources/assets/expindustry/recipes/machine_wood_hopper.json I don't think leaves have been ore-dict registered already (its tricky to check, but you can look for all references to the oredictionary.registerore function and find out what Forge registers) and if not, you can register it yourself.

https://github.com/Draco18s/ReasonableRealism/blob/master/src/main/java/com/draco18s/hardlib/api/internal/CommonContainer.java#L37 I use this class as a "base" class that my other containers then extend, meaning I need this logic written once.

}//TODO add the other fabric variations You need to add your other fabric variations, assuming that those variants exist in your code. Second: "size": { "small": { "fabric": { "jungle": { That is not how variants are specified. You either need to use the vanilla format ("fabric=jungle,size=small":{ ... }) or the Forge variant ("fabric":"jungle" { ... }, "size":"small" { ... }).