Skip to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Animefan8888

Forge Modder
  • Joined

  • Last visited

Everything posted by Animefan8888

  1. Show where you call ModelLoader.setCustomModelResourceLocation
  2. It also overrides the method and returns a more proper value.
  3. That can all be done in the Block class. Look at BlockFurnace for an example of the particles. And you can look at the vanillas json files for examples of those.
  4. The registry name should follow these two rules It should contain the modid as the domainName. It should be unique. Though i need to clear something up and it will be easier done through this modding video I made for 1.10.2, which doesn't use the events so ignore that part, but what it does do correctly is how to call the ModelLoader.setCustomModelResourceLocation method. At the bottom you will see how it is called, you may need to pause the video.
  5. Don't do new ResourceLocation(String, String) Block#getRegistryName() returns a ResourceLocation.
  6. Do you plan on having movement or the model being dynamic? If not use the JSON system.
  7. What is the registry name of your Block and the unlocalized name of your block.
  8. You didn't do it for the ItemBlock though.
  9. Don't extend BlockContainer instead extend Block and override createTileEntity(World, IBlockState) and hasTileEntity(IBlockState)
  10. It is necessary because we need some form of id that will not change. Numerical ids will change and are not mod specific, while using a ResourceLocation allows a Block, Item, etc to be traced easily back to its mod, and they are also mod specific because of the modid. So in other words a register name is just an id. You make two new ItemBlock instances in your ModBlocks class. Every time you make a new instance of any Item, Block, etc you need to set it's registry name.
  11. What went wrong was it is looking for beeboxers.mtl not bee_box.mtl
  12. If you are going to call ModelLoader.setCustomModelResourceLocation do not call ModelBakery.registerItemVariants. The later overrides the other. The problem is that you do new ResourceLocation(Reference.MODID, "items/essence_chariot") having the "items/" there adds it to the path so instead of looking for assets/modid/models/item/model.json it instead looks for assets/modid/models/item/items/model.json.
  13. new ItemBlock(block).setRegistryName(block.getRegistryName);
  14. That is not true, what it says is You never set the registry name for the ItemBlock.
  15. OBJLoader.INSTANCE.addDomain(Reference.MODID.toLowerCase()); is already called in your proxy.preInit class.
  16. And you call it in the init method, so you should call proxy.preInit in your ancientmod class's preInit method.
  17. Look at where you call proxy.init
  18. I think you will also need a Item Registry event to register the ItemBlocks, but I am not really sure. I haven't started updating to 1.12 just yet.
  19. Also are you calling ModelLoader.setCustomModelResourceLocation in the Block Registry event? If so it has its own event ModelRegistryEvent. You are not registering the ItemBlock for them.
  20. Where do you call proxy.preInit
  21. I do not believe so but you register your models the same way you did before, it just needs to be in the event.
  22. Code and ModelLoader.setCustomModelResourceLocation needs to be called from ModelRegistryEvent.
  23. In your block object/field/variable call getRegistryName() instead of getUnlocalizedName() as you do right here You are the one with the code...check. You call it in your ClientProxy, it is just you never call the method ClientProxy#preInit
  24. getRegistryName is from IRegistryEntry.Impl which all registry types (Block, Item, etc) extend.

Important Information

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.