Implemented EntityDamageDoorEvent

[CMarcoo]

EntityDamageDoorEvent: Handle Door Damage Interactions

Description

I've introduced a new event called EntityDamageDoorEvent in the PaperMC server software. This event is triggered when an entity (currently limited to Zombies and Pillagers by default) damages a door. It provides essential information about the damaged door, the break time, and the total door break time.

This implementation takes into account differences in breaking time between zombies (240 ticks) and pillagers (60 ticks).

Event Details

• Event Name: EntityDamageDoorEvent
• Trigger: When an entity damages a door
• Purpose: To allow developers to handle door damage interactions

Key Components

1. Entity: The damaging entity (e.g., Zombie, Pillager).
2. Door: The door being damaged.
3. Break Time: The ticks spent breaking the door.
4. Door Break Time: The total ticks required to break the door.

Usage Example

@EventHandler
public void onEntityDamageDoor(EntityDamageDoorEvent event) {
    Entity damagingEntity = event.getEntity();
    Door damagedDoor = event.getDamagedDoor();
    int breakTime = event.getBreakTime();
    int totalBreakTime = event.getDoorBreakTime();
    
    float percentage = ((float) breakTime / totalBreakTime) * 100f;
    if (percentage > 50.0f) {
        e.getNearbyEntities(5, 3, 5).stream()
            .filter(Player.class::isInstance)
            .map(Player.class::cast)
            .forEach(p -> p.sendMessage("Your home door is halfway broken, watch out dude :("));
    }
    // Additional logic...
}

[lynxplay]

Please merge the patches, instead of committing your changes as a new patch.
See our contribution.md for instructions.

Moving break time up also seems a bit meh in terms of diff.
What is stopping us from just passing this.breakTime + 1 to the event?

Looking through the code a bit more, I'd also add a notice in the javadocs that this even will be fired even if breaking the door is disallowed by the mob_griefing gamerule as that may be wrongly assumed to not be the case.

You also missed the import org.bukkit.craftbukkit.block.impl.CraftDoor; line in your import inlining.

Beyond that, is it worth to expose the "swing arm" part of the logic to the event?
E.g. allow plugins to define/overide if the entity will swing their arms in the damage tick.

[Leguan16]

If you don't know what lynxplay is talking about: Read the contributing guidelines here: https://github.com/PaperMC/Paper/blob/master/CONTRIBUTING.md

[CMarcoo]

yes I noticed I forgot to merge my patches :(

[lynxplay]

Are you going to fix the patch situation or do you want me to do that?

[CMarcoo]

Are you going to fix the patch situation or do you want me to do that?

Yes please. I truly don't know how to do it. I tried merging my patches and it became even worse.

[maxcom1]

So the event is called every tick OR only when new damage progress level is displayed? This is a bit unclear, at least for me

[CMarcoo]

Every tick that the door is being progressively damaged to its destruction.

[Lulu13022002]

Missing internal annotation and what is not a good name here

[Lulu13022002]

This is not resolved yet

[Lulu13022002]

This field should be at the bottom of this group

[Lulu13022002]

No need to reference the event itself in that link since you're already in that class

[Lulu13022002]

This is redundant with the interface

[Lulu13022002]

The second part of the name is not needed and implicit and no dots are required at the end