Talk:Java Edition 20w16a

False Bug Fix

It says: "MC-171020 – New nether biomes don’t work properly in buffet worlds" however, hoglins still turn into zoglins in crimson forests and nether wastes biomes, also placing water does not result in it evaporating, wet sponges do not dry, day and night exist resulting in beds working and respawn anchors not working, furthermore, it is possible to go into the nether using a nether portal despite the overworld essentially being the nether--82.37.14.115 17:33, 15 April 2020 (UTC)

I don’t believe any of the examples you provided are bugs and are all intended features by Mojang, because they are all intended behaviour in the Overworld Dimension.

I’m assuming that you’re basing your examples off the assumption that creating a Buffet World with a Nether Biome creates it in the Nether Dimension, when it doesn’t. All Buffet Worlds, regardless of Biome, are created in the Overworld Dimension. This is why you can sleep in Beds in any Biome in a Buffet World, because you are still in the Overworld Dimension, same with the Respawn Anchor blowing up.

This is also why you can successfully create a Nether Portal to the Nether Dimension in any Buffet World, because regardless of if you are using a Nether Biome or any other Biome, you are still linking the Overworld Dimension to the Nether Dimension, so saying that “it is possible to go into the nether using a nether portal despite the overworld essentially being the nether” is incorrect, as a Nether Biome Buffet World isn’t the Nether Dimension, it’s just using one of the Nether Biomes to generate its terrain and Mobs in the Overworld Dimension.

As another example, if you create a Buffet World using the Nether Wastes Biome, you’ll often find large shallow puddles of Water (not evaporated), and Netherrack only generates around 3-4 blocks deep, while regular Stone generates underneath for the rest. The same applies to Buffet Worlds created using End Biomes, just with End Stone instead of Netherrack. None of the Nether Biomes in Buffet Worlds generate the same as they do in the Nether Dimension, even if you use the Caves World Generation option, which actually does use the Nether Dimension’s World Structure when generating the world (so things like the bedrock ceiling), but that’s it.

Also, on Hoglins turning into Zoglins in Buffet Worlds, I noticed you only included the Crimson Forest and Nether Wastes Biomes, so I created 3 Buffet Worlds using the Warped Forest, Soul Sand Valley, and the Basalt Delta, spawned Hoglins in all 3 of them, and sure enough, they turned into Zoglins in all 3 of them. It isn’t an oversight, it’s just the intended feature of the Hoglins in the Overworld Dimension, regardless of Biome. Same with Piglins turning into Zombified Piglins.

If you still feel like none of these features should be intended behaviour, I would suggest taking it to the Minecraft Feedback website, as what you have is more of a feature request than a bug report.--45.44.33.204 17:54, 23 April 2020 (UTC)

JMX MBeans

JMX stands for JAVA Management Extensions and the JMX API was added to JAVA SE in J2SE platform 5.0. "The JMX technology provides the tools for building distributed, Web-based, modular and dynamic solutions for managing and monitoring devices, applications, and service-driven networks. By design, this standard is suitable for adapting legacy systems, implementing new management and monitoring solutions, and plugging into those of the future."

JMX Homepage: https://www.oracle.com/java/technologies/javase/javamanagement.html

MBeans or Managed Beans is a management tool that send custom or defined metrics to the JMX Monitor via the JMX Agent. This Data is stored and accessed on an MBeans Server.

Here is the official tutorial and introduction from Oracle: https://docs.oracle.com/javase/tutorial/jmx/mbeans/index.html

The snapshot release notes do not provide enough detail as to how many types of MBeans are being employed however it is Minecraft JAVA Edition specific and would typically be used for server or client analysis, diagnostic and management. It could hint at future optimizations. The built in JAVA SE version would at some point need to be upgraded to a newer JAVA SE release to best utilize all features as JAVA SE 8 version is deprecated and the current version is SE 14.

Wikipedia page with additional details: https://en.m.wikipedia.org/wiki/Java_Management_Extensions GeorgechambersIII (talk) 02:27, 16 April 2020 (UTC)