A better approach might be to allow the constructor to accept a list of BlockTypeTags (or type IDs) that it skips over, and then check those tags (or IDs) when looking at blocks to destroy. That would make it more flexible and enable custom use cases.

Is this the correct approach? I have several options for the variable that stores the list of BlockTypeIds namely :

• $excludedBlockTypeIds
• $ignoredBlockTypeIds

However, I think the name BlockTypeIds is too long, would you prefer $excludedBlockIds?

Should $excludedBlockTypeIds be public?

Well if people wanted to change the blocks affected by the explosion they can always cancel the EntityPreExplodeEvent and make their own explosion

This PR has been marked as "Waiting on Author", but we haven't seen any activity in 7 days.

If there is no further activity, it will be closed in 28 days.

Note for maintainers: Adding an assignee to the PR will prevent it from being marked as stale.

I stalled on merging this because I don't like the solution, but I don't currently have a better one. It's not been at the forefront of my mind lately. Will revisit it soon.