Draco18s

Your getMetaFromState and getStateFromMeta don't deal with the FACING property at all. Your onBlockPlaced method does fuckall. As I said in your other thread:

You haven't included your entire block class. The only code you've posted (besides your JSON files) is a single method that you overrode in order to do....nothing.

No, they aren't. According to https://jsonlint.com/ (for drill.json): Error: Parse error on line 48: ...", "y": 90 }, }} --------------------^ Expecting 'STRING', got '}' Although the actual problem is not with the 90, but a few characters later. I have to edit the tabs into 4 spaces to get the error to line up properly: Error: Parse error on line 48: "y": 90 }, }} --------------------^ Expecting 'STRING', got '}' You have an extraneous comma.

Also, seriously? MATH, MOTHERFUCKER, DO YOU KNOW IT? info.add(ChatFormatting.BLUE + (damage/2) + " uses left"); You can even get the formatting to change by doing easy checks, rather than this giant..massive...ugly...copy-pasted mess.

Why aren't you using the vanilla itemstack damage/metadata for this?

Ignore it. It's deprecated because you aren't supposed to call it. Overriding is fine.

Ok, so, 1: https://github.com/jonesto95/RaceCarMod/blob/master/src/main/java/tnsoft/racecarmod/RaceCarMod.java Your main mod file does dick. Nothing in your mod should work at all, as no items, blocks, or entities are created or models registered. Some of this is handled via your registry event handler. 2: Even if you called this method in your proxy, the server has no idea that your items or entities exist because this method only does stuff on the client. 3: This method does not appear to be called from anywhere.

Your blockstate json file is missing.

Like this: And then you post the text of your code in there, not a link. I don't know why you thought an embedded script tag was the right thing to do at all.

You need to use Reflection again to remove the final modifier. https://stackoverflow.com/a/3301720/1663383

The number of situations where your code isn't necessary numbers precisely zero.

Use Capabilities.

You will have to look at the code Minecraft uses to do what you want, then copy it for your own effect.

Yes. If I recall correctly, there is a method in the Item class called shouldShowEquipAnimation or showReequip or something like that, override that and return false when all that has changed is your NBT data.

I think that's Kotlin, which can cross-compile to Java. Don't quote me on that though. Anyway, the problem is here: getSubItems(tab: CreativeTabs ALL items have this method called for ALL tabs, which tab is the current one is passed in in this parameter. If you want to only have your item show up in one tab, you need to only return your item stack list when that tab is active.

Do it by binary halves: PIck half of the mods (alphabetically works). Doesn't need to be an exact half. Just make sure that Animania stays in each time. Remove those mods. If the problem persists, remove half of what remains. If the problem goes away, put half of the most recently removed mods back. Repeat until adding/removing a single mod causes the problem. This should take no more than 7 iterations for ~100 mods.

Well... 1) Use BlockPos.allInBox(...) instead of new BlockPos(...); and iterate over the list it returns instead 2) The more blocks you change all in one go, the longer the hitch will be 3) Look at the flag parameter to setBlockState() and see if you can avoid doing lighting recalculations until you're done

Yes, the forum is FUBAR. If you have any conversations, your inbox is considered "full."

TileEntities and NBT do not belong together. NBT is only for saving and loading from disk. If you have a TileEntity that has stored data, then that data is just kept as a raw field on the TE. Also: Show your code.

A thread from two years ago will never be worth replying to. If the original poster is even still around and if the version of Forge/MC being used is still supported, then maybe it's still relevant. But it's likely not.

No

Lets see... Create your own topic. Don't reply to old topics because "you are having the same problem." Instead, create a new topic.

Yeah, which is why some of my recent posts are like this one:

You bumped a two year old thread, that's why. If you HAVE a problem, start a new thread, is what D7 actually said.

Making a thread going "HEY GUYS, IMPORTS ARE A THING!" helps no one, because the only people who should need that help fail the "You are expected to have basic knowledge of Java before posting here to ask for help" part of the equation.