In this snapshot we're bringing you an additional advancement, updates to telemetry, as well as a fix for an 11 year old bug!
Happy stepping!
If you find any bugs, please report them on the official Minecraft Issue Tracker. For any feedback and suggestions on our upcoming 1.20 features, head over to the dedicated Feedback site category.
-
The Power of Books: Read the power signal of a Chiseled Bookshelf using a Comparator
-
For ease of use, the Smithing Table no longer requires a Smithing Template to be in the template slot before placing an itemstack into the other slots
-
Jukebox has been added to the Redstone Blocks creative tab
-
Walking on a block will now always play a step sound
-
It was previously not the case if you were walking along the edge of a block with air or fluid besides it
-
-
Walking on the ocean floor will produce a step sound for the block you are walking on at a lower volume and pitch
-
The data pack version is now 15, accounting for sign data format, item display orientation and advancement changes
-
Advancement trigger changes:
-
Added
recipe_crafted -
Changed format of
placed_block,item_used_on_blockandallay_drop_item_on_blocktriggers
-
-
Loot table condition/predicate changes:
-
Renamed
alternativetoany_of -
Added
all_of
-
-
Updates to telemetry
-
A new property has been added to every event:
launcher_name -
The
world_loadedevent now has a new property:realms_map_content -
Added two new opt-in telemetry events:
game_load_timesandadvancement_made
-
-
All fields in
placed_block,item_used_on_blockandallay_drop_item_on_blockhave been collapsed to a singlelocationfield -
New
locationis similar toplayerfield - it's a list of loot conditions/predicates -
All conditions in this list must match for a trigger to run
-
Conditions are evaluated in a new loot context called
advancement_location. It has access to:-
Player as
thisentity -
Position of placed block
-
Block state of placed/interacted block
-
Held/used item as "tool"
-
-
Migration guide:
-
Contents of old
locationfield should be migrated tolocation_checkcondition -
Contents of
itemfield should be migrated tomatch_toolcondition -
Contents of
block+statefields should be migrated toblock_state_propertycondition
-
Example (from make_a_sign_glow advancement):
Before:
{
"conditions": {
"item": {
"items": [
"minecraft:glow_ink_sac"
]
},
"location": {
"block": {
"tag": "minecraft:all_signs"
}
}
},
"trigger": "minecraft:item_used_on_block"
}
After:
{
"conditions": {
"location": [
{
"condition": "minecraft:match_tool",
"predicate": {
"items": [
"minecraft:glow_ink_sac"
]
}
},
{
"condition": "minecraft:location_check",
"predicate": {
"block": {
"tag": "minecraft:all_signs"
}
}
}
]
},
"trigger": "minecraft:item_used_on_block"
}
-
Loot condition
alternativehas been renamed toany_of -
Added new loot condition
all_ofthat passes only when all sub-conditions pass. It has the same syntax asany_of
This release includes a new global property sent with every event, a new property in the required WorldLoaded event, as well as two new opt-in events. The updated required events will help us troubleshoot launcher bugs more efficiently, and understand how Java Realms content is interacted with. The updated optional events will help inform game design decisions, and allow us to track and improve game load speeds.
-
Added new property:
launcher_name-
This is set based on the
minecraft.launcher.brandsystem property. This will help us troubleshoot game launch related bugs more effectively, as we will be able to see whether the issue originated in the Minecraft launcher or a third-party program.
-
-
world_loaded-
Added new property:
realms_map_content-
When loading into a Realms Map Content world (Minigame), the
world_loadedevent will receive the name of that map. This is to help us understand how Java Realms users interact with Java Realms adventure or minimap content.
-
-
-
advancement_made-
This event is triggered when a player completes an advancement, and allows us to see the advancement ID and the time when the advancement was completed. This helps us as a studio understand player progress and limits, which informs our game design.
-
-
game_load_times-
An event that is triggered when the game client is loaded and includes the time it took for the client to load. This is so that we can work on improving and reducing the time it takes to load the game client.
-
-
MC-1133 - Whether or not a player experiences some effect is calculated based on the block under the center of the player
-
MC-48923 - Slime/magma cubes not affected by jump boost potion effect
-
MC-257269 - Sculk sensor detects player walking between carpet and wool
-
MC-261417 - The hitboxes of sniffers are not adjusted when they lay down
-
MC-261952 - Clocks flicker rapidly when enchanted and in an unnatural dimension
-
MC-262003 - Bundle tooltip does not show its interface
-
MC-262067 - The type of sniffer digging particles that are produced is determined by the block that sniffers are located on instead of the block that sniffers are digging
-
MC-262069 - Sniffers continue digging after their target block is destroyed
-
MC-262104 - Rendering of FPS graph seems to be performing worse than before
-
MC-262123 - Advancement titles of new advancements introduced in 23w17a are improperly capitalized
-
MC-262133 - Strong lag spikes when moving above a cleared area with exposed void
-
MC-262218 - Block light updates don't cross chunk borders properly in 23w17a
Snapshots are available for Minecraft Java Edition. To install the Snapshot, open up the Minecraft Launcher and enable snapshots in the "Installations" tab.
Testing versions can corrupt your world, please backup and/or run them in a different folder from your main worlds.
Cross-platform server jar:
For previous changes for Minecraft 1.20, see the previous snapshot post. Read more about the changes in the Wild update in the release post
Comments
0 comments
Article is closed for comments.