Draco18s

And even if it did (and somehow enforced it), IBlockState implementations are still allowed to call it.

You have the latest, huh.

Very rarely. You have to subscribe to them, have the console log which side it thinks its on, and run the code in single player. If you get 2 loggings you'll know it runs on both sides. If you get one, it'll tell you which side its on.

It will only work if the event is actually even fired client side. Not all events are.

BlockContainer does literally nothing useful for you. You think it does, but it does not. Of all the things it "does" for you, only hasTileEntity and createTileEntity are things that you want. Forge has already made better versions of these methods (states instead of metadata integers!) available in the Block class. There. Is. Nothing. Else. You want from this class. You extended it without knowing what it did, assuming that it was full of magic and candy without actually looking. You blindly said "I want a block that holds items, therefore it is a "container" I am going to use BlockContainer because it obviously does those things" when it does not. Items are stored in the tile entity, not the block and the only important thing for tile entities is hasTileEntity and createTileEntity which you can get from the Block class. Every thing else that class does is detrimental to your code and causes one problem or another. No, they aren't. People "have disdain" for the newer versions of Forge because it's for newer versions of Minecraft, and there's a large section of the community that thinks that 1.7.10 was the "bestest version ever" of Minecraft because of the combat changes added in 1.9/1.10. Forge for 1.10+ is amazing. Capabilities are the most awesome system that Forge has ever added to a modder's toolbox, increasing inter-mod compatibility massively. Now, all that said (I'm late for work), For a problem that has occurred hundreds of times, there's no point. You want to know more? Search the forums. How many times should I have to explain the innermost workings of a problem to a new modder? Ten of you join the forums every day. And the thing is, of those ten, nine point nine of them want anything more than "solve my problem" or "give me teh codez." You never asked for anything more, so how was I supposed to know you needed more? So. Welcome to my ignore list, as obviously you won't be interested in anything I have to say, so why should I be interested in what you have to say?

You don't implement writeToNBT and readFromNBT.

But you never asked why. You only kept asking "how do I fix this?" And you kept yelling at me that I wasn't reading your posts. But all you ever asked was "how do I fix it?" And the answer was Stop Using BlockContainer. Done. That's it. Problem solved. You want to know why BlockContainer fucks things up? Actually ASK. But you know what, good on you for digging into the vanilla code base and figuring it out on your own. Congradulations, you now know why we tell you not to use BlockContainer because it fucks everything up. We solve problems for people, for free, all day long, every day of the week. We've seen the same problems so many god damn times Diebiesen07 made a god damn common problems thread. And for reference, you're one "but you didn't answer my question" away from being added to my ignore list because I can't give any fewer shits any more. My first post in this thread solved your problem and all you've done since is bitch that I didn't tell you why it solved your problem without ever actually stating "what is it about the vanilla code that causes this to happen?" And no, I'm not going to answer that question now either. Because I have no shits left to give. There's vanilla code for vanilla blocks like the chest, and it's crappy vanilla code that you should never use. End of story. You probably know more about it than I do, because I stopped using BlockContainer because it is garbage and didn't care to learn why. I learned the better way and moved on with my life.

For reference, here's everything you said about your problem, all of which goes away when you stop using BlockContainer. Only here, after you solved the problem, did you even remotely tangentailly ask, why it happened: What did you miss? You used BlockContainer. What would cause this issue? Using BlockContainer.

Ok, how about this: BlockContainer fucks up everything. Not just rendering, it fucks up a bunch of other stuff too. Has done since forever, that's why you aren't supposed to use it.

Yes, that one. Derp.

If you'd followed the advice and stopped using BlockContainer your problem would have been fixed, by your own admission:

livingSpawn(LivingSpawnEvent.NameOfSubEvent event)

The LivingSpawnEvent has sub-events IIRC.

Your registerItems(ModelRegistryEvent event) method is missing the @EventHandler annotation. Also, that method needs to be in your client proxy: The ModelRegistryEvent is @SideOnly(Client)

Oh. Looks like my first comment was the problem all along. I think I'll take a few minutes of justified smugness.

YES, I KNOW. AND EVERY THREAD I'VE EVER READ HAS HAD TO DO NOTHING SPECIAL. Except call addDomain. It uses the standard block json file and standard block model file, pointing towards the obj file. That's it. Nothing else.

Whatever that is, you don't need it. All you have to do to load obj models is this: OBJLoader.INSTANCE.addDomain(Refrence.MOD_ID);

Looks like it's rendering just fine. With the exception that the texture UVs are incorrect.

Problematic Code Issue #4 As for OBJ models, you still need to tell the game that you need an Obj Loader.

Not sure.

1) This board is for people making (progrmaming) mods, not running servers 2) This entire forum no longer supports 1.7.10

I am unsure about that. Double check that you're only performing it in the overworld.

Like I said, you're a better programmer than I am. I figured there was a reason why it wasn't that way, but I asked anyway. Seriously, that was uncalled for.

To make sure I understood correctly: "For legacy reasons we can't. (Only if it's too long or not lcased)." Would it be viable to only complain if Forge is running in a dev environment? Anyway, I'll stop bugging you about it, just was one of those things that I swore was a Thing at some point and isn't now, but fully recognize that sometimes I invent details like that out of nothing. If it's not possible, its not possible: you're a better developer than I am. Forge does things I can't even comprehend and develops those things far faster than I ever could.