Skip to content

Prevent logging of wind burst explosions and improve BlockExplodeListener (Fixes #830)#873

Open
guss-alberto wants to merge 1 commit intoPlayPro:masterfrom
guss-alberto:explosion-fix
Open

Prevent logging of wind burst explosions and improve BlockExplodeListener (Fixes #830)#873
guss-alberto wants to merge 1 commit intoPlayPro:masterfrom
guss-alberto:explosion-fix

Conversation

@guss-alberto
Copy link
Contributor

This PR fixes #830 by using the new ExplosionResult system introduced in 1.21 through the Bukkit adapter

It also improves logging for other BlockExplosions by logging bed and respawn anchor explosions respectively as #bed and #respawn_anchor, reducing the amount of explosions logged as a generic "#explosion". Due to the .getExplodedBlockState() method only being added in 1.20, it also goes through the bukkit adapter.

I have removed the checks for #tnt and #end_crystal in BlockExplodeListener because they only trigger the EntityExplodeListerner anyways, so there was no point in maintaining them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

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

1 participant