Blocking custom explosions #5605
Labels
bug: unconfirmed
Potential bugs that need replicating to verify.
Comments
100petr
added
the
bug: unconfirmed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Type of bug
Other unexpected behaviour
/ess dump alloutputhttps://essentialsx.net/dump.html?id=e2d65972988d46bd97377002c06f6da6
Error log (if applicable)
No response
Bug description
Grenades from the itemsadder plugin destroy blocks even when explosion protections are enabled in essentialsxprotect. Probably missing support for explosions that are artificially created. I tried to post it to itemsadder already, but it seems to be a thing in essentials PluginBugs/Issues-ItemsAdder#3166 (comment). "EssentialsX should listen to the proper Bukkit event and avoid explosions triggered by the Bukkit API from damaging blocks."
Steps to reproduce
Create an explosion using createExplosion
The blocks will be destroyed
283991825-7b5c5840-b7b1-4f84-83dc-15234c5528fb.mp4
Expected behaviour
Essentials will protect against these explosions
Actual behaviour
Essentials does not block these explosions and the blocks are destroyed.
The text was updated successfully, but these errors were encountered: