Jump to content

vemerion

Members
  • Posts

    326
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by vemerion

  1. I think the full log is needed track down what the problem is. You can use pastebin for example to upload the log.
  2. If you could post the full log in pastebin or similar that would be great ๐Ÿ™‚
  3. Can't you instead use one of the blocks in the Blocks class (such as Blocks.AIR) to do the measurements?
  4. Probably not a sure-fire way, but you could check if the entity is an instance of 'Enemy', or check if the entity type has the mob category 'MONSTER'.
  5. This question came up recent in another post, I think you can find the answer there:
  6. Sure! You need to create your own BlockEntityRenderer and render the item, and then register the BlockEntityRenderer to your block in the EntityRenderersEvent.RegisterRenderers event
  7. Yes, I would say a custom network message is the best way to do this (at least to my knowledge)
  8. The registry name should be all lowercase, so "item" and not "Item"!
  9. I think specifying "render_type": "minecraft:cutout" in the model json should fix the issues!
  10. Looks like you need to specify "gui_light": "front" outside of the "base" object.
  11. First you need to create the model, for example with Blockbench, and then you need to export it as a java file. Then you need to implement IClientItemExtensions.getHumanoidArmorModel() to return your custom model, and Item.initializeClient() to provide you custom IClientItemExtensions.
  12. In the class ModEventBusEvents you are registering a recipe type using a vanilla registry! You should instead use the Forge registry, ForgeRegistries.RECIPE_TYPES, similar to how you register block and items. Also, looks like you missed an 's' in 'foodstuffs' in the smoked_steak.json file
  13. Try adding a call to '.noOcclusion()' on the BlockBehaviour.Properties when you create the block.
  14. You should use the Forge registry when registering features. You can read more about how to do it here.
  15. Looks like your modid is "mymod", but you specified it as "warmod_perekur" in the sounds file!
  16. You also have to take item enchantability into account: https://minecraft.fandom.com/wiki/Enchanting_mechanics#Enchantability
  17. You need to synch the inventory of the blockEntity to the client! You can do it either with a custom packet, or by overriding relevant methods in your block entity (getUpdatePacket/onDataPacket/getUpdateTag/handleUpdateTag).
  18. You could do it like this: player.setItemInHand(InteractionHand.MAIN_HAND, ItemStack.EMPTY);
  19. You should use Attributes.ATTACK_DAMAGE and not EntityAttributes.GENERIC_ATTACK_DAMAGE ๐Ÿ™‚
  20. No problem, glad you were able to figure it out!
  21. Aha, so you are using some kind of plugin for Minecraft modding for IntelliJ? Either way, en_us is the default localization file, so maybe the path is wrong somehow after all?
  22. Perhaps you accidentally registered the event twice?
  23. You would need to listen to the LivingDeathEvent and check if the player is holding your custom totem and if so prevent the death. You need to manually play the sound TOTEM_USE and create the particle TOTEM_OF_UNDYING when you prevent the death.
×
×
  • Create New...

Important Information

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