Technical News in Minecraft Snapshot 22w18a: place command

Ladies and gentlemen snapshot 22w18a  included lots of mob fixes that you   can hear about in my gameplay updates video  linked right here but also has a new command,   new tags and more development on the signed chat  system. My name is slicedlime and in this video  

We’ll go through all the technical changes. To begin with, the bundled java runtime is now   version 17.0.3, which really shouldn’t be much  of a change for anyone other than that a few   JVM-level bugs have been fixed. I’ll also mention something about the  

Vanilla data packs – both the built-in pack, the  report generated by the game and the vanilla world   generation reference pack now store their object  keys sorted alphabetically – with the exception   of type fields and parent fields, those get  listed first. This makes diffing the files  

Easier when things change, and avoids false  positive changes from fields moving around.   Let’s jump into the new command… or  rather, let’s start with a removed one.   The placefeature command has been removed.  Instead, there is now a place command,   with three different sub-commands: place  feature, place jigssaw and place structure.  

Place feature works just like placefeature did  before. See what I did there? Place jigsaw does   the same thing as hitting the generate  button inside the user interface of a   jigsaw block – that is, it generates a jigsaw  structure starting in a certain template pool  

At a given jigsaw anchor, then does a given  number of levels of expansion from there.   This means you can generate entire  jigsaw structures with this – like   the ancient cities here, but also you can start  at any level of a jigsaw structure and just  

Generate that. For instance, we can  generate a single village house here.   The last type is place structure, which  places an entire structure just like is   done in world generation, so we can place any  structure – including ones that aren’t jigsaws,  

Like a nether fortress. Keep in mind that there  are some mechanisms that work differently because   we’re running the command later: things that snap  to the height map might snap on top of things like   trees or anything else that has been built…  and the bearding for structures is a part of the  

Terrain generation, not the structure generation –  so you won’t get beards for your villages here.   Let’s move on to data. The goat horn  data no longer has a SoundVariant   int – instead it has an instrument ID. That instrument ID also comes into play with  

Some new tags. There are now instrument  tags, with three of them added in this   version – regular_goat_horns, containing all  the goat horns that drop from regular goats,   which also controls which ones you can find  in pillager outposts. screaming_goat_horns   contains all the goat horns that drop from  screaming goats. and goat_horns contains  

All the available goat horn instruments, where one  additional goat horn item is added to the creative   inventory for every instrument in the tag. Banner patterns can now also have tags.   The ones available in the loom are controlled  by the no_item_required tag, and the ones  

Unlocked by certain items are found under the  pattern_item folder with a tag for each item.   There are also two new block tags in  this version, snow_layer_can_survive_on   and snow_layer_cannot_survive_on. Let’s talk about loot tables.   The function set_goat_horn_sound  added in 22w17a has been removed.  

Instead there is now a set_instrument function  that sets the tags needed for an instrument item   by randomly picking one from a provided tag – that  tag is referenced in the options parameter.   Before we dive into the custom world  and chat changes in this version,  

Please take a moment to roll for loot by clicking  on the like button for the video. If we’re lucky   YouTube will give us some epic views for your  trouble – so I appreciate your help. Thank you!   For custom worlds, a bug has been fixed where  world generation packs didn’t load properly  

When apple .DS_Store files were present in a  datapack. That has been fixed, but note that   you’ll still get errors from having garbage files  inside a data pack, so if you’re a Mac user it is   still a good habit to get into cleaning up  the trash before packing up a data pack.  

In the vanilla data, ancient cities  now use the new start_jigsaw_name   field introduced in the previous snapshot, and  their generation height has changed from -51 to   -27. The city itself will still end up in the  same place, but now generates from a position  

Rather high up and downwards rather than  from a lower corner – but if you want   a good example of how that start_jigsaw_name  works, you can now look at ancient cities.   Let’s talk about servers and the new signed chat  system. Servers can now define chat style formats  

For clients in a new registry called chat_type.  This is currently found under the worldgen   folder in the vanilla report. The styles are  synchronized to clients when they join the   server and control the translation key or format  used and can also change the chat narration.  

This lets you apply styling to the entire  message like italics or colors, but not   click events or hover events currently. If  you want to take a look at the vanilla files,   you’ll need to run the report generator. For a non-chat related server change,  

The game now connects to servers with SRV  entries on non-default ports properly.   If you’re on the code side of things, the  chat system is still evolving there too,   where chat messages from the say, msg, teammsg and  me commands are now all cryptographically signed  

Just like regular chat messages. And that’s all for this time.   Thank you for joining me for this entire video,  I do appreciate it. If you’re curious about   other technical changes for the Wild Update,  check out this other video linked right here!