Andreas Troelsen 17317fa0ae Handle BlockExplodeEvent explicitly. ... This commit cleans up the old fake event show that was implemented when the BlockExplodeEvent was introduced and caused all sorts of issues back in the day. It should have been cleaned up years ago, but "if it ain't broke"... Well, it is now! With this commit, however, we get rid of the constructor invocation that throws up, but we obviously need to replace it with something else to take care of the problem it used to fix. The handler is close to a carbon copy of the EntityExplodeEvent handler, simply because the code isn't very reusable due to direct method calls on the event object itself. But because of the refactoring step of the previous commit, we don't actually have to explicitly repeat the gnarly "repairable" code that handles the block list, yay... We obviously don't have an entity to check for (and remove from the monster manager), and we need to dig a little deeper for the Location object needed for the region check, but other than that, it's the same thing. Fixes #796		2024-07-23 02:22:48 +02:00
..
main	Handle BlockExplodeEvent explicitly.	2024-07-23 02:22:48 +02:00
test	Make LexeMatcher package-private.	2024-01-01 18:26:44 +01:00