I woke up this morning to quite a surprise. I hopped out of bed, eager for a Minecraft 1.8 pre-release, only to be greeted by a tweet from Dinnerbone which stated:
Confused, I dug a little deeper, and found a post made to the Bukkit Forums by none other than EvilSeph himself. At the time, the post had already been heavily edited, and after flipping back and forth between the post and the Twitter feeds of Dinnerbone and Jeb,. . .
Recently, I made a major change to one of MGLib's subsystems to fix a semi-rare bug. Said bug occurred often enough to make it a point of concern, but just rare enough to make it difficult to determine the cause or really anything about it. I couldn't figure out why it was happening, and to this day, I still don't know.
I suppose I should elaborate on what the bug was. MGLib has a feature where it can override the vanilla Bukkit
PlayerDeathEvent (which is ordinarily uncancellable) and instead call its own custom event so that the player effectively stays alive and the minigame using MGLib can do what it wishes instead. For example, TTT utilizes it to effectively turn the player into a sort of "ghost," where they become invisible, can fly, and can't interact with the world. However, because death events aren't cancellable, it has to use a workaround.
Before. . .