Animefan8888

Yes. Sadly you are repeating yourself an awful lot. Imagine for (type in tool_types) // COPPER/TIN, IRON/LEAD, etc setup(new Item(new Item.Properties()), type + "_pickaxe"); setup(new Item(new Item.Properties()), type + "_axe"); // ETC

What are you trying to do here? You iterate every biome for the oreType for every biome in the game. News flash This is not the biome that you want to add it to. Right now your code will try to add it to every biome. This is not the correct event to do this in. You should be doing this in the FMLCommonSetupEvent.

This isn't really a problem. From my experience it always says that. Was there an actual error?

There is another command gradlew eclipse. However you opened the project as a gradle project as such I'm not sure how necessary it is. I always gradlew eclipse gradlew genEclipseRuns Import Project as a Java Project.

You could also do. Item::getToolTypes // Which returns a Set<ToolType> Set::contains Check if the Item::getToolTypes contains ToolType.PICKAXE. Generally all Pickaxe Items even ones that do not extend PickaxeItem will have ToolType.PICKAXE in their tool types.

When you call RenderTypeLookup.setRenderLayer which takes a predicate. I'm not sure exactly what this is used for but you can allow for multiple render types. Have you tried using the translucent render type. What happens when you just use that one.

1.12.2 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support. For more information read the LTS at the top of the page.

Are you testing in creative mode? If you are PlayerEntity::addItemStackToInventory returns true even if the players inventory is full.

Post more of your code.

World::addEntity

No. Minecraft::displayGuiScreen seems like a good bet. Remember that is client only code and must only exist on the dedicated client.

Does this get called?

Did you register your packet?

The vanilla shield actually has two model files that it uses. minecraft:item/shield.json and minecraft:item/shield_blocking.json. You need to use the ItemOverrider you have in the constructor to tell it to point to the second model.

You need to override IForgeItem::isShield to return true. And I'll need more information to help you with the animation. What exactly is happening versus what you expect to happen.

You need to override Entity::createSpawnPacket and inside use NetworkHooks.getEntitySpawningPacket. I believe this is automatically handled for LivingEntity subclasses. But I'm unsure.

RenderTypeLookup.setRenderLayer and RenderLayer.getCutoutMipped is the one you will want i think.

People who don't want to move onto the newer versions because all the big mods have yet to be updated. Similar to you except they have been doing it for a while. It's the same for 1.8.9. A decent portion of the community that didn't like the combat update refuses to update and people still make mods for 1.8.9 they don't get support here.

It specifically says 1.12 is no longer supported. It says this to make it clear. "Other Versions" means not the latest and the one immediately before the latest in this case.

No.

It's really not. It's just not supported on this forum anymore. There are other forums where you can go for modding help. Yes because everyone reads the rules or the appropriate information before posting on a forum. Also how would you enforce that? Would you have a warning system? Just make more work for the very few mods that this forum has? Sure you can say this is true, but imagine not touching a large code base like Minecraft/Minecraft Forge(specifically pre 1.14) for a few months perhaps years in the cases of 1.8.9 then being asked a question about those versions? Honestly my answer may be a bit spotty. And I may lead you in the absolute wrong direction.

Sorry 1.12.2 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support. For more information read the LTS at the top of the page.

I doubt anyone would want to. Why not wait for their creators to update them. It's not that the version has become obsolete. It just can you imagine having to support 10 different versions of a codebase that has been heavily modified over each version? Like if there is a bug found in Minecraft 1.15.2 at this point do you think Mojang is going to release 1.15.3 in order to fix that bug or just fix it in 1.16+ when it comes out? Also you can easily find many resources for 1.12.2 out there as it was the primary version for Minecraft Forge for a long time. Or even outside of Minecraft would you expect Microsoft to offer support for older versions of Windows like Windows XP even though they have explicitly discontinued support for it.

Show what you've tried.

What do you mean other entities? Try taking a look in the class and it's parent classes.