Draco18s

Like I said, find another hobby. Being a programmer professionally, there is certainly a degree of knowing libraries and APIs, but it is still about problem solving. I can't add two numbers together to save my life (no joke, I just asked wolfram alpha to do some polynomial multiplication for me), but I still need to know the process, the reason why I need to add two numbers and not multiply them, or what a dot product is vs. a cross product. Sure, I might just be gluing a bunch of tools together to get the result I want, but I still need to know which tools to glue together and in what order. And that is problem solving. And you know what else I have to do? Recognize when an API or library has changed and made one method out dated and replaced it with a better, more flexible way of doing things. And that's what Minecraft did with the JSON model system: models can now be defined by resource packs, not just textures. Recipes too, once data-packs are finalized. Doing that requires changing how the system works, but the end result is far and above worth the effort that it costs us modders. What did this guy say? Oh right:

In your IDE, do this:

No. You already have it. I even told you how to find it. Go fucking look at it.

Jesus mother fucking christ on a crutch. You do know how to create your own variant blocks, yes? createBlockState, getMetaFromState, and getStateFromMeta?

Look at vanilla.

Feel free to read up: https://en.wikipedia.org/wiki/Quaternion This is expected for one of two reasons: 1) GL deals with rotation as a quaternion and when you make an adjustment in Euler, the end result is not neccessarily the same Euler (to avoid gimbal lock) 2) Rotation around a rotated axis changes all of the Euler values from a non-rotated reference frame.

checkAndDropBlock and canBlockStay. The class is only 336 lines long and 26 methods, it shouldn't have been that hard to find.

Programming is not for you. Programming is all about making your own Advanced level 5D sodoku/rubiks/crossword puzzle hybrids and then solving them. If this makes you frustrated and angry, then you need to find some other hobby.

Use capabilities.

You might have some luck in looking into the code Vanilla uses to render name tags.

Lore. L-O-R-E. Also more correctly called "tooltip information". Lure is something else entirely.

Look at what BlockDoublePlant does to make that happen.

...what?

BlockDoublePlant It contains a variant you don't want, don't need, and is fucking up your ability to create a valid blockstate file.

Don't do that. Do this: new ModelResourceLocation(FastCobbleItem.getRegistryName().toString(),"inventory") Problematic Code #1 Not visible in your code, but worth checking: #7, #10 As to your actual problem: I can't actually find your problem in your post.

Overriding items is an intended feature but only one mod can override any given item. It's a necessary sacrifice.

Uh...duh? When you buy more socks, the odds that you grab a white one out of your sock drawer at random changes. Vanilla doesn't want to spawn more total mobs as the variety increases (otherwise you reach a hyperbolic example of a billion different mobs and vanilla insures that at least one of each is spawened at any given time, making it impossible to move without running into something) so the actual percentage chance goes down.

I renamed a parameter in a function once. I'd have done it more, but I forgot the syntax MCPBot uses to override the protections on letting people rename anything (as you can't edit the javadoc without said override).

I think your problem here is that rotations are fundamentally a 4-axis object and you're trying to piecemeal it with three. Yes, Euler Angles are a Thing, but they suffer from gimbal lock. This is the closest thing I can find that has the right math: https://stackoverflow.com/questions/14720264/create-a-rotation-matrix-from-a-position-and-a-look-at-position

I'd assumed it was to query whether or not a cap existed, and if so, get the cap. Hence my lazy-programmer implementation of has() being return get() != null

This is because you're not overriding getSubItems, but a parent class is, providing variants you don't want. Every single one of your model problems is likely also related to that fact. Stop extending that class. (You also didn't do anything about 2,3,and 4 in my bullet list, but whatever)

Where do you put other client-side-only code?

No one cares, this isn't a chat room. Anyway, ok, that looks less awful than I'd originally thought. ModelRegistryEvent is client-side only. It can't live here. IHasModel is a fucking stupid convention. Seriously. ALL ITEMS HAVE MODELS Your IHasModel does nothing to insure that your block class registers an ItemBlock for itself, leading to a possible crash if you forget. The method your IHasModel interface supplies just redirects to your client proxy with no additional information from the block/item. proxy.registerModel(item, item.getRegistryName(), "inventory") will work just fine (or if the code is already in the client proxy--see #1--then you don't need the proxy. part...or really, you just just call ModelLoader directly).

You shouldn't be accessing that line at all. Use the registry registration events like you're supposed to.