Minecraft Snapshot 21w11a Fixes 8 Year-old Bug
Minecraft has received another sample of new features from the Caves & Cliffs update. This time Mojang added, among other things, new features related to copper and lightning bolts. By the way, a bug from 2012 was also removed.
Devs at Mojang continue to test more new features from Minecraft's massive update in subsequent snapshots. The latest one - 21w11a - is now available in the Installations section. Traditionally, we remind you to make a backup copy of your world before activating a snapshot, or to run the snapshot session from a separate folder. Otherwise you risk losing your creation!
Usually the biggest excitement is caused by the novelties in a given snapshot, be it new materials or representatives of flora and fauna. Snapshot 21w11a, however, does not introduce new items, instead modifying the operation of previously added elements. Lightning bolts can be placed in water, and bone meal can be used to accelerate the growth of a large variety of Dripleaf, which, when destroyed, will drop its blocks (or rather, leaves). Furthermore, in the new snapshot, players can reduce copper oxidation levels, whether with a lightning strike or an axe. The tool also lets you peel off wax, which can be applied with a single click - just use a honeycomb on a block.
On top of that, there are some minor updates like a new tablet design and changes to amethyst mining. There's also a new mode of collecting information about how the game works on a given PC via a ten-second recording (called with the F3+L shortcut). The developers have also made it easier to craft selected blocks with moss: just combine the two elements, without the need for laborious collection of jungle vines for the recipe (although this option is still available).
Apart from the aforementioned news, snapshot 21w11a offers primarily nearly a hundred bug fixes. This includes the removal of a bug with inappropriate texture of some blocks after covering them with snow. This bug would not draw much attention if not for the fact that it appeared over 8 years ago. This is already evident from the extremely low issue number (MC-1483; the second youngest bug fixed is MC-12363), and its tab on Mojang's official website reveals that it was reported on October 31, 2012.
