Draco18s

The fuck are you doing that causes this?

Its almost as if you've not actually played the game. 1) The F3 screen 2) The /give command 3) Blockstate JSON files (and the associated error messages when they aren't correct) All three of these use string representations of blockstates. Or there's just the sheer point that: anything can be turned into a string if you try hard enough.

That it is, but null has always been Minecraft's air. Block.AIR was null at one point too.

Then table.getPools(); returned null and you didn't check for that.

You can't. ItemStack.EMPTY is meant to be immutable. That's why its a static reference and named the way its named. Its item is Air (and you can't change a stack's item) and Air is always empty.

Its on line 31, whichever line that is.

You don't need to clone the empty stack.

Show what you tried.

Yes, because it can hop in and extinguish itself. Or at least, that's what I suspect.

Yeah, I totally couldn't tell from your previous post with that same code in it.

You should be using EntityEntryBuilder anyway.

That should work just fine.

for now. That said, the "code style" type issues are ones that are just bad practice, not that they cause the game to break. In some cases it makes things more complicated than they need to be (IHasModel) and in some cases simplifies something that shouldn't be (Proxies).

Just because that's how they did it does not mean it is correct. It simply doesn't crash.

I have seen no code that would result in this behavior.

Huh? What? Have you tried....deleting the code?

The "most often" you can update an object is every frame and you have limited numbers slower than that if you consider that they have to be less than 1. i.e. you can't update an object 0.8 (80%) of the time (what are you supposed to do any given frame?). So you end up with 0.5, 0.333, 0.25, 0.2 etc. as allowable values... Or time%n == 0

Because the onItemRightClick method is only called when the player has their mouse over a block and that only happens when the block is within their reach.

Because you never told the server what you were doing. Remember: The client is always a lying, cheating bastard.

Because you registered your event handler class using an annotation, which requires the methods to be static. The part that makes no sense is that your non-static function was not being called for vanilla blocks but was for modded blocks.

This is bullshit and makes no sense.

ModelRegistryEvent is client side only. Code Style Issue #1, #3

This part isn't absolutely necessary.

There's no problems with what he's doing in this regard.

IBakedModel main = event.getModelRegistry().getObject(mrl); You need to insure that this is not failing.