Draco18s

I understand that. What I'm saying is, because you have everything being created in a static initializer, you can't control the order in which they are initialized, and something is going too soon, generating a Null Pointer Exception. You need to not use a static initializer.

I think this is caused by you having an overabundance and excessive overuse of static fields. Namely, this line. As far as I can tell, that line is being invoked before your Blocks have initialized. In any case, it's definitely getting called before your blocks have been registered.

Because the area outside your test location is flat and unbounded in all directions.

1) Include more of the error 2) Include more of the log 3) I need to see more of the log and error to identify which of several possible problems you are having and to identify which class this is occurring in. 4) Why is your /blockstates and /models folders not inside /resources? You have not correctly created a workable git repository. It should look like this.

You forgot to register your client proxy as an event handler: http://mcforge.readthedocs.io/en/latest/events/intro/#automatically-registering-static-event-handlers

Post your log. There's always a message when the game fails to load a model or texture. Additionally, this: https://github.com/Hillage/ExtremeLlamas/blob/master/src/main/java/tech/hillage/extremellamas/ModItems.java#L15 Is silly. You can just call ModelLoader.setCustomModelResourceLocation from here, there's no reason to have the item class do it.

For example, the client controls all player motion directly and as far as the server is concerned, the player basically teleports around in small increments. The server can still say "nope, you are not allowed to go there" and the client is forced to listen, but in general, the client is in control.

http://mcforge.readthedocs.io/en/latest/concepts/sides/ specifically the @SidedProxy section as well as the getSide and SideOnly portion:

This is not how to use SideOnly

JACKPOT You have done all of the things that Forge doesn't support. A winner is you.

Code?

What? No. Christ. Build two of your cannons near each other. Do they both work? I bet not!

You must acquire the TE from the world every time.

Because your instance fields are not saved. Because they shouldn't exist at all.

https://github.com/Draco18s/ReasonableRealism/blob/1.12.1/src/main/java/com/draco18s/ores/block/BlockMillstone.java#L74

Gasp. So easy.

Problematic Code #4

Oh cool, a crash log. Mind providing...I don't know... any context?

You can't do this easily. And your "attempt" makes no sense because a subclass of a class can't change the way other subclasses act.

Yes

Its not about the proper way to register a block state mapper, my point is YOU DO NOT NEED TO DO THIS AT ALL EVER unless you are doing something like "I want to split my blockstate file into two files based on X property."1 How did I register my blocks in 1.10? Like this: https://github.com/Draco18s/ReasonableRealism/blob/master/src/main/java/com/draco18s/hardlib/client/ClientEasyRegistry.java#L33-L42 https://github.com/Draco18s/ReasonableRealism/blob/master/src/main/java/com/draco18s/hardlib/client/ClientEasyRegistry.java#L80-L83 Do you see anything about a custom block state mapper? 1 This being a thing I actually did.

Sorry, I missed that. It was a little buried. Nothing in the log... https://github.com/bxz2311196368/someusefulthings/blob/1.10.2/src/main/java/com/bxzmod/someusefulthings/blocks/BlockRenderLoader.java#L18 Why are you registering state mappers at all? You're using the default state mapper, you shouldn't need to do this.

You should always check the log. And then scroll down the log some more until you see something helpful. If you still don't, then post here, and include the log.

bone_meal is not an item that exists in minecraft. You want minecraft:dye with a metadata value of 15 Second, if you have entirely blank lines and collumns in your recipe, omit them, otherwise your recipe can't be crafted at any location in the crafting grid, but are instead forced into the corner.