Jump to content
Currently supported: All versions

vemerion

Members
 View Profile  See their activity

  • Posts

    390

  • Joined

  • Last visited

  • Days Won

    15

 Content Type 

Everything posted by vemerion

  1. vemerion
    Best to use Global Loot Modifiers
  2. vemerion
    You should save a reference to it before you register it in AddReloadListenerEvent and then you can access that reference from wherever you need it. Here is an example of how Forge itself does it for the LootModifierManager.
  3. vemerion
    That completely depends on what your listener is for. For example, the vanilla RecipeManager has a method 'getRecipeFor()' which is used in various places, one of them being the furnace to see if an item can be smelted.
  4. vemerion
    You can look at the vanilla subclasses to get an idea of how to implement your PreparableReloadListener.
  5. vemerion
    Looks like you forgot to negate the 'warudo.isClientSide()' predicate
  6. vemerion
    You have to call CombatTracker.recordDamage() before you call die().
  7. vemerion
    You can use the 'MissingMappingsEvent' event
  8. vemerion
    You could use the BlockTags.MINEABLE_WITH_AXE tag.
  9. vemerion
    You can register an 'ItemColor' in the 'ColorHandlerEvent.Item' event.
  10. vemerion
    It was replaced with 'IForgeServerPlayer.openMenu()'
  11. vemerion
    You can use the BlockBehaviour.canBeReplaced() method
  12. vemerion
    You can look at the places where the method is called to get an idea of what arguments to supply.
  13. vemerion
    To create your own data driven system you can extends PreparableReloadListener (or its subclass SimpleJsonResourceReloadListener) and then register it in AddReloadListenerEvent.
  14. vemerion
    A block should never be bigger than the standard 16x16x16 size. If you need something bigger than that you should split it into several different blocks (like how tall grass does it).
  15. vemerion
    You need to add this field to the model json file of your block "render_type": "minecraft:cutout" or "render_type": "minecraft:translucent" depending on if if those parts are semi-transparent or fully transparent.
  16. vemerion
    Hmm, I don't see any problems with the code. You could try debugging and put breakpoints in saveNBTData() and loadNBTData() to see make sure that the methods are called and that the code in the methods works as expected.
  17. vemerion
    Can you post the code for your capability provider? Also, you can use NbtUtils.writeBlockPos()/readBlockPos() to more easily write/read BlockPos to/from NBT.
  18. vemerion
    I think the method is 'Player.getAttackStrengthScale();'
  19. vemerion
    The collision in this case is calculated using ProjectileUtil.getHitResult() which uses a slightly different bounding box than the bounding box of the projectile. But that bounding box should be bigger so should not be a problem. Your best bet might be to try and place some breakpoints and step throught the code to try and figure out why the collision does not work.
  20. vemerion
    You are unlikely to get a reply, since jadend has not been online in almost a year. But you can look at the vanilla Monster class to see how updateSwingTime() should be called.
  21. vemerion
    No problem, glad I could help
  22. vemerion
    This is not possible. Modded registries are intentionally fired after vanilla ones.
  23. vemerion
    You can access the player on the client with 'Minecraft.getInstance().player'
  24. vemerion
    Looks like you are missing the blockstate json file for the fabricatormk1.
  25. vemerion
    Can you post what you tried? Then I can perhaps point you in the right direction
×
×
  • Create New...

Important Information

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

  I accept