Jump to content

SeqSEE

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by SeqSEE

  1. Why is your models.block and blockstate the same?
  2. I had not known that. Good to know and tested and you are totally right!! EnumHelper.addArmorMaterial works like a charm
  3. Okay, that makes sense. Thanks!
  4. No.... In the interface IForgeRegistryEntry$Impl you set the registry name and it looks like.... public final T setRegistryName(ResourceLocation name){ return setRegistryName(name.toString()); } public final T setRegistryName(String modID, String name){ return setRegistryName(modID + ":" + name); }
  5. You can look at a project I am working on if you'd like It has more than tools and armor but one thing to note is ItemArmor.addArmorMaterial was/is broken. So you have to add the enum manually with EnumHelper.addEnum in replacement of the broken one. Anyways, I hope this is helpful and here is the link to a working example armor class I made. https://github.com/SeqSEE/HempFarmer/blob/master/src/main/java/com/mch/hempfarmer/item/HFArmor.java
  6. I have not been setting my unlocalizedName to the registry name. In an Item or Block class I do a method like: public Example(String name){ ResourceLocation location = new ResourceLocation("modid" + ":" + name); this.setRegistryName(location); this.setUnlocalizedName(name); } What that does is make it so I can name my Items, for example item.example.name=Example (and not modid:item.example.name=Example), in my language file and the resource location is set and I can set up my models and textures in the correct locations on my end in my resources.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.