@MartenMooij

You can't hide names on entities without making the entire entity invisible.

Also, that suggestion sounds more within the scope of mob-spawning plugins (ahem, like OtherDrops).

Hey, Awesome plugin! I was wondering if you could make it so there is about a 1% chance to spawn a rainbow sheep (A sheep named jeb_), maybe also hide the name? Thanks.

Last comment for now - I promise!

@Dad_Yoshi

• Mining overhead without helmet = chance for concussion. The only problem is that nothing actually hit your head, so you just got an imaginary concussion. This should be nuanced to, "if FallingBlockEntity" lands inside of player, check player for "if wearing Hat" and if that returns "false", apply "concussion effect", whatever that effect may be.
• When you break "x" block with appropriate tool, chance tool gets stuck and block does not break on that try. This is more annoying than interesting. I find events where you hilariously take light damage, or suffer some benign potion effect to be interesting. If I wanted to clear out an entire landmass, even if the chance were really small, this wouldn't work well for anyone, really. Here's a better idea: the block does break, but the tool you used in your hand gets moved elsewhere in your inventory and takes an extra point of damage.
• Chance of catching fire when walking over lit torch. Makes perfect sense, although this should only apply to torches that are standing straight up. Don't want people catching fire when navigating long, narrow hallways. ;)
• Chance of a dead bush scratching you when you walk over it. Instead, you could've suggested the "Roses Have Thorns" feature to expand to other blocks too. Pine leaves are prickly and could scratch you, but it would be inappropriate if I suggested this as a separate feature, because we'd have three features that do similar things (roses, dead bushes, and pine leaves).
• Wood planks splinter into nothing if "wooden item is used again". I assume this means, if you break the plank for a second time. The problem with this is that you have to track down each wooden plank to figure out if it's a "clean plank" or a "damaged plank". This is more annoying rather than interesting, and would only put a strain on any server's wood economy as wood planks can then only be placed twice - I don't see a reason why this should be added to begin with. A better, but unrelated idea would be wood planks giving you splinters when you break them.
• Cobblestone breaks into gravel if broken up. A better idea if it were worded as "Cobblestone has a chance of breaking into gravel when a player breaks it."
• Chance of getting stuck when walking on clay. Sounds like the Quicksand feature. Or if by stuck, you mean slow, then sounds like the Sticky Tar feature.
• Chance of losing boots when walking on clay. I've mentioned this before, that it's a bad idea if you essentially "drop" your boots. I don't exactly see the point of this, because you can lose any kind of footwear by tripping, so long as it's not sufficiently fastened to your feet. (Arguably, though, Minecraft lacks a conception of laces. They do have leads, though.)
• Chance of blindness if mining overhead sand/gravel. This is a really good idea, but it should also extend to mining sand when you're too close to it, and getting blinded if a FallingBlockEntity hits you, and its ID is sand or gravel.
• Chance of damage if landing in water from a great height. It shouldn't be a chance, and the damage should be as if you landed on solid ground, but divided by some sort of configurable integer. This is Minecraft, after all, and you wouldn't want to completely ruin players' "water drops".
• Chance of retrievable arrow if you miss. This is already a part of vanilla Minecraft.
• Chance of damage if sleeping too close to burning furnace. Saying you take damage because of carbon monoxide poisoning is not good enough reasoning. The nether is a giant cave full of burning things. Don't you think you'd instantly suffocate upon setting foot in there? (Not to mention all them lava lakes.) And why does it have to be sleeping? People don't only get poisoned by CO in their sleep. A better, "getting-damaged-by-furnace" idea would be removing items from a burning furnace and burning yourself in the process.
• Chance of anvil falling on you (by erasing the block below it) if not placed on sturdy block. This screams out an opportunity for vandals everywhere. I could also imagine that it would bring about more issues than just this, but I don't believe this to be a good idea.
• Chance of bookshelf falling over if not placed near a wall. Structure/block-detection is rather hard to implement without hogging a lot of resources. That's the first issue with this idea. Second issue is that it doesn't quite make sense in conjunction with Minecraft. In Minecraft, there's no such thing as "walls" - it's a bunch of blocks and your imagination. If I piled on bookcase blocks on each other, I could call it a stack of books instead of a wall of books, or a bookshelf. Then, the reasoning behind falling stacks of bookcases wouldn't add up. Third issue is that, much like the anvil-idea, there could arise many potential problems.

Sorry about the double-comment (going on triple), but it might be necessary for the sake of not keeping one constant stream of text-walling. Also, that's a habit I've got to stop. But I'm going to respond to each comment point-by-point because I love this plugin that much. :D

@forchark

There is no easy way to distinguish between scraping against lava (presumably a wall of lava or a lava-fall) and "diving" into a pool of lava (in other words, entering lava vertically). I would imagine implementing such a feature would be resource-intensive, but it should be able to be done. It will probably have a few issues, though.

Lava dripping is a client-side particle effect; again, no easier, resource-free way to do this. The most direct way I could imagine would be to detect if a player is "x" blocks away from a lava block, is directly under the lava block, and if there is only one solid block in between player and aforementioned lava block. But to make sure damage doesn't multiply by the "depth" of the lava pool (because the check would be reiterated for each lava block, as lava blocks aren't solid), this mechanic would also have to factor in lava-blocks as solid blocks, or just take the closest lava-block directly above the player. I'm not a developer, so let's just say I don't actually know anything about this stuff. ;)

Similar issue with your slow-mining wet-block idea, although I'm not exactly sure why mining a wet block would be slower. I'd imagine the pressure the water exerts on the block, in addition to the fact that it's soaked in water, would make it easier to "collapse". But hey, "wet" stone blocks ain't all that realistic either.

"Chancemod" is the "dividing factor" for the "chance" parameter. The chancemod is the number you divide the chance by, so a higher chancemod means a smaller chance.

Minor bleeding is a good idea, and should be a part of crazy combat. But let's not take it too far and consider, "Oh, but what if it gets infected?" Anyone can get infected with anything at anytime, given the right vector. :)

Gaining stamina would require tracking players and keeping data on each player - completely out of the scope of this plugin. The idea of this plugin is to focus on "chance occurrences" that are seemingly unlikely to happen, but could happen anyhow.

@Techwolf77

Electrocuting then becoming slow (and perhaps even weak) makes sense - I've gotten electrocuted in real life, and couldn't walk straight for two seconds afterwards. But because you soiled your pants? You could soil your pants at anything - for example, something frightening you. And people don't soil their pants that easily. And if you actually soiled your pants in Minecraft, there'd be a big problem: Minecraft doesn't have any bathrooms. :D

Vomiting to reduce food poisoning duration sounds like a good idea, but I'm not exactly sure what "vomiting" does to the player. I'm just going to assume it means to instantly lose some hunger.

....I'm pretty sure I criticised your third suggestion too harshly, so no need to elaborate on this point. :|

Some of the crazy suggestions that have recently come up are hilarious, but are a bit way too specific. I don't mean to shoot anyone down, but let me take one as an example:

"When shot with a bow in the "naughty places" it also gives a chance for soiling your pants but makes the player who did that laugh uncontrollably, giving him resistance."

With this logic, I can make any event follow any event, no matter how improbable it may be (which is strange for me to say, considering the title and aim of this plugin). For example, I could easily suggest an idea where if I were to hit someone with my fist, it would count as "smacking", my hand might get hurt, and I would take light damage from it. Who knows, I might even bust my wrist causing me to be unable to attack for 2-6 seconds.

I will concede that while the ideas suggested in the last few comments are funny and lighthearted, they're (I would think) too specific to implement as they are now (they can be nuanced into something much more generic). I'm very aware that one could just "turn off" any feature they don't want, but that's not the issue. If there's too many features (think CraftBook or Essentials) to sift through, the plugin's structure could easily get confusing.

For example, in addition to "hurting your fist", I could also suggest a very similar feature, but with a different scenario. But wait, I don't have to because I know the plugin already has one: CraftingThumb. You craft something and accidentally smack your thumb with a sawblade. If all the suggestions were like this and kept on coming, the list would quickly become endless. I'm not saying CraftingThumb should be removed, I'm saying there should be some sort of filter for newer suggestions, which leads me to my next paragraph...

So, I might suggest a "filter" for some ideas, consisting in two parts: "How flexible is the idea" and "How realistic is it". All (or maybe most, but it doesn't matter) the ideas currently implemented, and all the ideas on the todo list pretty much have both covered.

"Flexibility" refers to the "reasoning" behind the scenario. If the reasoning behind the event is far too specific, and/or does not necessarily follow, then chances are it's not a good idea to implement (although probably hilarious). For example, nailing someone in the "naughty parts" with an arrow, then laughing, then getting resistance is far too specific. First off, one can easily laugh without the plugin's help: it's called chat (you can say "lol"). Second off, why resistance? Why not any potion effect? But then, why would you get a potion effect from laughing?

"Realism" is somewhat self-explanatory. Here, I'm talking Minecraft realism, so it goes hand-in-hand with the aforementioned criterion. Getting a leak in your boat is realistic. Getting potion effects from laughing is not. Getting struck by lightning while mining underground is not (not that anyone has suggested this idea). Events that are insignificant, and rely on coincidence as why events should follow, rather than any sort of "logic" are not necessarily realistic. For example, "chance of losing boots by walking on clay," doesn't necessarily follow. Why does it have to be clay, and why do you have to lose your boots? They could be made of diamond, and a thief could be nearby. But that would be a big coincidence too...

Eh, I sound a bit of a nitpicky ass, but I only want what's best for the plugin - and I didn't mean to be harsh on anybody. Perhaps just their ideas (I'll be honest here), but no one in particular. To be fair, there are some good ideas too: "vomiting" to decrease poisoning duration, going blind when digging overhead gravel/sand, and "chance" (should be a guarantee actually) that jumping into water too hard hurts you. The rest of the ideas... well... that's up to the dev to decide. ;)