vemerion

Best to use Global Loot Modifiers

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.

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.

You can look at the vanilla subclasses to get an idea of how to implement your PreparableReloadListener.

Looks like you forgot to negate the 'warudo.isClientSide()' predicate

You have to call CombatTracker.recordDamage() before you call die().

You can use the 'MissingMappingsEvent' event

You could use the BlockTags.MINEABLE_WITH_AXE tag.

You can register an 'ItemColor' in the 'ColorHandlerEvent.Item' event.

It was replaced with 'IForgeServerPlayer.openMenu()'

You can use the BlockBehaviour.canBeReplaced() method

You can look at the places where the method is called to get an idea of what arguments to supply.

To create your own data driven system you can extends PreparableReloadListener (or its subclass SimpleJsonResourceReloadListener) and then register it in AddReloadListenerEvent.

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).

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.

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.

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.

I think the method is 'Player.getAttackStrengthScale();'

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.

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.

No problem, glad I could help

This is not possible. Modded registries are intentionally fired after vanilla ones.

You can access the player on the client with 'Minecraft.getInstance().player'

Looks like you are missing the blockstate json file for the fabricatormk1.

Can you post what you tried? Then I can perhaps point you in the right direction