Minecraft: Java Edition Snapshot 21w38a Continues Work on Part 2 of Caves and Cliffs Update
As predicted when Minecraft: Bedrock Edition Beta 18.104.22.168 released yesterday, Mojang Studios is now releasing the second official snapshot of Patch 1.18 Caves and Cliffs Part 2, which includes a new lineup of fixes and tweaks, Return of Strongholds, and a new way for Mojang to collect vital performance-related telemetry data (more details below).
Minecraft: Java Edition Snapshot 21w38a follows its predecessor with fewer new features and changes, but it does include a few important changes nonetheless. In addition to the return of strongholds, which had been removed in the previous shot, copper is now more common in this shot. A lot of bugs were also fixed which should hopefully provide a more stable experience.
VPN offers: lifetime license for $ 16, monthly plans for $ 1 and more
For many, however, the most interesting aspects of this release will be on the technical side of things. This snapshot allows the global generation to enjoy more background processor threads, which will be especially useful for those who play on high-end gaming platforms. Mojang also improves telemetry collection in this snapshot and will collect vital information while the world is loading which will ideally help the studio improve performance for building and loading the world in future snapshots.
If you are interested in what information will be collected by Mojang while playing this snapshot, be sure to check below.
Minecraft is one of the best games ever, and the Java Edition certainly deserves its designation as one of the best PC games. This is further proven by the long list of the best Minecraft toys and gifts, which includes something for everyone.
The full changelog for Minecraft: Java Edition Snapshot 21w38a includes:
- This snapshot is still not compatible with older worlds – to play in this snapshot you will need to create a new world
- Saving the world can sometimes take a very long time – if you see the world stop moving for a while, that’s why
- Sprinting is no longer reduced to walking by gently rubbing your sleeve against a wall
- Fixes for mineral distribution
- Previously, any collision with a block reduced the sprint to walking. Now, for very minor collision angles with a block, players keep their sprint. For larger collision angles, the old behavior is retained
- Copper ore generates up to 95 y (as originally designed)
- Increase in the amount of copper
- Lapis lazuli is generated in drops, like other minerals (instead of spreading)
- A new parameter has been added: “Simulation distance”
- Increased maximum number of background threads
- Added telemetry for world loading
- Features will not be updated outside the simulation distance
- Allows higher rendering distance with less CPU load
- A new slider in the video settings on the client
- A new simulation distance property in the dedicated server properties
- We will continue to work on this with a simulation distance goal also affecting the ticking of blocks and fluids.
- Various background tasks, including worldgen, run on a background thread pool. Its size is equal to the amount of available CPU threads minus one, but there was an upper limit of 7. Now that upper limit is 255. This should help high end machines with world generation performance.
- The upper limit can be exceeded by
max.bg.threadsJava system property, for example when running multiple servers on a single machine
- In this release, we’re reintroducing diagnostic tracking, which was part of Minecraft: Java Edition until 2018. We’re bringing it back to better understand our players and improve their experience. Specifically, we hope to ensure higher performance for the extremely heavy world generation in Part 2 of the Caves & Cliffs update later this year.
- In practice, this can mean identifying technical issues in the game, such as the performance of less powerful hardware on very complex terrain. This information will also help us prioritize various aspects of development, balance the game’s functionality (learning, for example, that goats push every player off cliffs), and give new Minecrafters a hand (after they’ve gotten to know each other). realized that many of them are stuck at the same points). All data is processed according to GDPR and CCPA best practices and is used to develop a better and generally more enjoyable Minecraft: Java Edition.
- Global charging event
- Sent when loading single player world or connecting to multiplayer server
- Contains the following information:
- launcher id
- user ID (XUID)
- client session identifier (changes on restart)
- global session ID (modifications by global load, to be reused for later events)
- game version
- operating system name and version
- Java runtime version
- if the client or the server is modified (same information as on the crash logs)
- server type (solo, Realms or other)
- game mode
- The game fails to switch audio output from one device to another after starting the game (from title screen)
- No sound for using the shears on crying, twisting, cave vines or kelp
- Fortresses do not generate in 21w37a
- Liquids sometimes do not spread
- Random light level of 0 in the sky
- Crash when changing render distance /
java.lang.ArrayIndexOutOfBoundsException: Index 28084out of range for length 26136
- Memory leak in 21w37a
- Large spruce trees do not generate in Groves
- Starting and stopping JFR profiling multiple times during the same minute overwrites previous JFR results recorded during that minute
- Runoff caves generate above ground
- Cannot start with alternate JVM due to JFR requirements
- Problems with JFR event metadata
- Too many aquifers on the biome surfaces at Y = 63 and below
- Aquifers often generate with hard straight boundaries