Draco18s

Here's a working inventory container/gui. It's actually kinda funky. Particularly line 37. https://github.com/Draco18s/ReasonableRealism/blob/master/src/main/java/com/draco18s/ores/GuiHandler.java

And you never could before, either.

Most likely, you are using the single-parameter tool material constructor, you need to use the three parameter ToolMaterial, float, float one.

That method is called anytime world.setBlockState() is passed a 0x1 as the third parameter.

That's onBlockHarvested, I believe. Which is called from onBlockRemoved (by player).

Create a new enumerated and have an explicit "unknown" or "none" value.

te.hasCapability(ItemHandlerCapability, side)

In C# you can, but really all that means is that the interface is declaring an explicit getter/setter. I know this because I did it not to long ago. e.g. public interface ISomeThing { public someField { get; set; } } But yes, you can't do that in Java. You'd have to declare it as a getField() and setField(v) methods and supply the field itself in the implementation.

Items.getItemFromBlock(block)

You don't have the Java knowledge necessary to even have someone help you with this.

Because the object is never set to anything. I can't tell you because you haven't posted your current code.

Also self explanatory.

That's not how you compare ItemStacks.

And the crash

If any are wrong, this would be the one. But not having used I18n yet, I am not 100%

Considering that the crash occurs on line 67 of your custome elytra class, yes, I do think its related to your code.

Should be self explanatory.

Define "doesn't work"

In which case: Stop suggesting custom entities for simple problems. It is the wrong solution.

There is no reason to call new WorldGenCustomNameHere() every time the chunk generates. You can create one in the constructor of CustomGeneration and save it in a private field and reuse the same generator. Also, "WorldGenCustomNameHere" is a terrible name.

Forge still saves a .log file. But I suspect that this isn't a Java issue but a computer issue.

I don't see a crash log.

If an item has the wrong texture (e.g. missing) there is a problem with the item's JSON model or with its registration, there is nothing wrong with Vanilla's EntityItem class. There is no reason to create a custom EntityItem class unless you need to override certain EntityItem behavior. Please stop suggesting a complicated solution to a simple problem.