[Bug] Maces with wind charge errorniously log blocks broken by #explosion when used

[RandomBagel420]

When you land a hit with a mace with wind charge, it causes a bunch of false block destroyed by #explosion log events, as if an explosion went off in that area. This by itself isn't a huge issue, but when rolling back that area, and then undoing, it causes those blocks to be destroyed.

Steps to reproduce:

Go to an area with no coreprotect log data

Give yourself a Mace with any Wind Burst enchantment

Summon a mob and kill it with a smash attack

Run /co lookup radius:10 time:1m

You will see that there is a bunch of false #explosion broke block events

Run /co rollback radius:30 time:1m

Coreprotect will think that all of those blocks were exploded but rolled back

Run /co Undo

An explosion hole that never should have happened will appear

Here is a Video demonstrating this issue

Minecraft version: 1.21.8
Server running Paper version 1.21.8-60-main@29c8822 (2025-09-06T21:49:13Z) (Implementing API version 1.21.8-R0.1-SNAPSHOT)
Coreprotect Community Edition v23.0

[Alex1337F]

I also noticed this problem. Saw that some blocks had logged #explosion, but were still there. I thought my database was getting corrupted or something before I stumbled upon this issue.