Draco18s

The Item class (and all of its subclasses) are templates by definition. The only way you can add completely customized tools is through Capabilities: data added to each itemstack that has the data for the behavior.

No they're not.

Oh, it can be larger, but you'll run into all kinds of issues...like frustum culling, being able to place blocks inside it, being unable to collide with it, unable to prevent mobs moving through it, and so on.

You could look at Tinker's Construct. It's open source. https://github.com/SlimeKnights/TinkersConstruct You still need to have textures, TiC just combines multiple textures using a Custom Mesh Definition

What I mean is, just because the code updated on the server side does not mean that those values have propagated to the client.

Are you sure that you're not looking at a client side update and a server side update?

That's what happens when you bind a texture and don't rebind what Minecraft was already using. In this case, you bound the font texture (which the FontRenderer class does for you, automatically) during the rendering of non-font UI objects.

You don't need TEs or TESRs for this, is possible with blockstates. Take a look at GreyGhosts's Minecraft By Example mod: https://github.com/TheGreyGhost/MinecraftByExample/tree/master/src/main/java/minecraftbyexample/mbe04_block_dynamic_block_model1

Translate (-0.5,-0.5,-0.5) Rotate Translate (0.5,0.5,0.5)

You can't register items with the ore dictionary if they haven't been registered with the game yet. PreInit is too early.

Or more accurately: All blocks get models automatically All items (including itemblocks) require models to be registered None of the information relating to model registering requires private access

Cool! What's this do? Also: Seriously? 1) You don't use it 2) Where did you get it 3) Any method you might want is static

I presume all of those have javadoc that says, "use the XYZ sensitive version" on them? In such cases I presume that I can read.

Yes. Normally. But in the current environment, it doesn't because Mojang.

Deprecated means "do not invoke" not "do not override." Just do what vanilla does.

Good to know. Hadn't heard about this, or if I did, I didn't know it was different.

He is:

There is no 1.13 branch for Forge on github yet, so we're still a ways off.

its en_us if you're using pack_format 3 in your pack.mcmeta file. If a value isn't specified it uses version 2.

The slime is likely changing rendering flags and your code doesn't correctly account for it. Namely, slimes are transparent.

Minecraft does not ship with this package, you have to shade it into your compiled jar.

As null is a perfectly valid value, all objects are initialized to null.

This registers your class to the bus, and the bus can only invoke static methods on it, but your @SubscribeEvent methods are not static.

Jaysus christ what on earth is this? Are you jar modding?

Never name your instances the same as the class name.