Regarding block-glitching

/kill would be easily abusable. For example you could hit a player once and then the player would /kill 21 times causing a instant nuke.

 

That could be fixed some way or another, I'm sure of that.

 

I think the easiest solution is the one already mentioned and that is to remove the block glitch altogether.

 

Keep block glitching since if dying upon breaking blocks got removed, the OOM rate would go up by a lot. The best they can do is give mining fatigue to everyone or set the gamemode to adventure again and give C4s some CanPlaceOn datatags.

 

I'm not 100% sure if you're actually able to defy the physics of how fast a block breaks with coding (Coding isn't exactly a god's tool) and if it is, I'm all gung ho for it. But I'll give my best shot here. A Python relatively (and I'm sure many of you know this already) is a golden shovel, and gold items are infamous for breaking blocks at great speed such as granite, stone, sand, gravel and snow. I've encountered this issue plenty considering I have some bad aim and timing is my strong suit, but all I can say really is to watch where you point your gun really. It's pretty annoying but there's also the fact we can't remove the block glitch feature as the iota goes, when they're a glitch, there's bound to be an abundance of people to abuse it.

 

I said that.