Choonster

Please don't post your email address publicly. I've removed it from your post.

Duplicate of the following topic:

Duplicate topic.

Duplicate of the following:

The bots have been banned.

Duplicate of this topic:

Read Paint_Ninja's message again, there's an additional requirement that you're not meeting.

Use DamageSource#getDirectEntity to get the projectile entity.

The debug.log includes the crash report and other information, there's no need to post crash reports separately. Regardless, 1.16.3 is no longer supported on this forum.

It's entirely possible for crafting table recipes to customise their output (including setting NBT/damage) by overriding IRecipe#assemble. I have a recipe that does a similar thing for armour here.

ServerChatEvent was overhauled in the 1.19.1 update to support the secure chat system, it's probably not going to be possible to fix this without updating to 1.19.1 or 1.19.2.

If you look at the loot table for cows, you'll see that it checks whether the entity is on fire to determine whether to drop steak; not whether the tool has Fire Aspect.

I never found a way to ignore the errors; but I eventually replaced HWYLA with Jade, which doesn't have this issue.

Instead of using an interface and extending the vanilla entity classes, could you use a capability? You could have a base class with the shared logic and then entity-specific implementations attached to different entity classes. If you need to do stuff every tick, you'd need to use LivingUpdateEvent.

ObfuscationReflectionHelper methods always take SRG names, even in the development environment. In development, the SRG name is automatically remapped to the corresponding MCP name.