by y.st. » Sat Aug 08, 2015 17:11
This is a bug in the game, and in fact, Celeron55 wrote a patch to fix the bug. The patch even allowed servers to reenable the glitch on a per-player basis for servers that still wanted it. <https://github.com/minetest/minetest/pull/760#issuecomment-20988912> However, this patch was never pulled to Minetest 0.4.*. From the looks of it, PilzAdam has added the fix to 0.5.* <https://github.com/minetest/minetest/commit/15be2659eae6da2c3807713eb6e068d8aa436423>, but it could be a while before 0.5.0 is released. My guess is that it wasn't added to 0.4.* because it's a client-side fix which would require bumping up the protocol version, which would cause a compatibility break between old servers and new clients as well as new servers with old clients.
For now, what you're after is not doable, sorry.