Animefan8888

Yeah college and other more important stuff started taking all of my time, now it's time to learn all this new forge code base. ?

Instead of using new ConfiguredFeature<... Use Biome.createDecoratedFeature It gives you more control. In this specific case allows you to control where the ore/block generates.

Provide which item you are working with you gave us no direction to the actual file(s) we are working with.How did you use EntityPlayer$getCooledAttackStrength?

I'm not sure if you have solved this or not, but you need to create more than one instance of the item. Subitems are not standard anymore, and will probably be removed from existence. I assume the only reason something like subitems in creative tabs still exists is probably because what if you want to show two same energy items with different durability(energy values).

Take a look at that items texture along with the .mcmeta file with the same name as the image. Or look at Minecraft's water/lava texture and their .mcmeta file.

A world capability is just a wrapper around a WorldSavedData anyways.

To use that method you need to implement ITickable.

You never use Which you first need to initialize a lot like you do your nbt variable.

You're probably pretty much on your own for this. You've been presented with to options, the BufferBuilder route which may lead to an abrupt dead end or using Voidwaikers approach which may lead to more promising results.

Ok. This is your problem, its not a problem with it being about mods. It is a problem with those methods not existing, they have different names now.

Then you should be able to solve the errors you have. They are errors in method signatures.

Learn that first, modding is incredibly difficult if you don't.

Do you know the basics of Java?

If it is disabled remove any recipes from it after they have been added via whatever condition you want, and do the same for removing it from a creative tab.

They don't all TE's are ticked at the same time from the world being ticked. Generate a random number and determine if the update method is called from that?

Yes, don't do that.

No, Minecraft is really weird about what it uses deprecation for. When they use it for blocks it means don't call it.

Use your IDE to find the correct parameters Block#isOpaqueCube exists in 1.12 and it has an IBlockState parameter.

What version are you modding for?

Did you ever register a block with that name? If so create a new world. Ids are serialized so they can be persistent with the assigned numerical id.

Try isOpaque.

Create a blockstate file for it. And then probably textures.

Why not item.getRegistryName()? Is this where the file is located look at it character by character. You've got a pack.mcmeta file probably set to 3. This means your lang files must be all lowercase aka en_us.lang.

Read the docs.