News - Minecraft: JAVA Edition 1.19.4

News - Minecraft: JAVA Edition 1.19.4 - Printable Version

+- Sick Gaming (https://www.sickgaming.net)
+-- Forum: Our Game Servers (https://www.sickgaming.net/forum-58.html)
+--- Forum: Minecraft (https://www.sickgaming.net/forum-103.html)
+--- Thread: News - Minecraft: JAVA Edition 1.19.4 (/thread-101435.html)

News - Minecraft: JAVA Edition 1.19.4 - xSicKxBot - 09-08-2023

News - Minecraft: JAVA Edition 1.19.4

<div style="margin: 5px 5% 10px 5%;"><img src="https://www.sickgaming.net/blog/wp-content/uploads/2023/03/minecraft-java-edition-1-19-4.png" width="16" height="16" title="" alt="" /></div><div><div><img decoding="async" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/03/minecraft-java-edition-1-19-4-1.png" class="ff-og-image-inserted"></div>
<h3>Changes</h3>
<ul>
<li>Updated Horse Breeding</li>
<li>Jukeboxes have changed to be at parity with Bedrock</li>
<li>Interacting with armor or elytra items in-hand will now swap them with equipped gear</li>
<li>The camera tilt when hurt is now based on the direction of incoming damage</li>
<li>Potions colors have been adjusted to make different types of potions more distinguishable</li>
<li>Potions no longer have an enchantment glint due to it obscuring the color of the potion contents</li>
<li>Enchantment glint on items and armor is now more subtle</li>
<li>Armor Stands now preserve custom names when placed and broken</li>
<li>Vexes now use a separate charging animation when empty-handed</li>
<li>Tweaks to recipe unlocking to make discovering vital crafting recipes easier for new players</li>
<li>Updated the Create New World screen</li>
<li>New accessibility options and improvements</li>
<li>Updated the Realms screen to be more in line with the Singleplayer and Multiplayer screens</li>
<li>Added a notification system for Realms to tell you important information about your Realm</li>
<li>Added “Credits & Attribution” button in the Options menu</li>
</ul>
Horses, Donkeys, and Llamas
The speed, jump height, and health of a baby are now a variation of the average of the parents’ attributes, rather than being biased toward the average possible value.
This change makes horse breeding a viable way of getting great horses if a player starts with good parents and puts in enough time and Golden Carrots.
Jukebox
<ul>
<li>Emits a note particle above it while playing a music disc</li>
<li>While playing a music disc, it will emit a redstone signal of 15</li>
<li>Droppers and hoppers can now interact with it</li>
</ul>
Creative Menu
<ul>
<li>Added painting variants to the creative menu</li>
<li>Paintings with a pre-defined variant will now display the author and title in the item description when hovered over</li>
</ul>
Recipe Unlocking
<ul>
<li>The Crafting Table recipe is unlocked immediately on creating a new world</li>
<li>The Crossbow recipe is no longer unlocked by sticks</li>
<li>The Soul Campfire recipe is no longer unlocked by sticks</li>
</ul>
Updated Create New World Screen
<ul>
<li>The screen is now organized into three tabs
<ul>
<li>The Game-Tab allows to set the world name, Gamemode, Difficulty, and whether to allow cheats</li>
<li>The World-Tab allows to set the World-Type and Seed, and to toggle the generation of structures and the bonus chest</li>
<li>The More-Tab provides access to the Game Rules and DataPack Selection Screen</li>
</ul>
</li>
<li>Tabs can be switched with the keyboard by pressing Ctrl+Tab and Ctrl+Shift+Tab</li>
<li>Specific tabs can also be navigated by pressing Ctrl+Tab Number
<ul>
<li>For example, Ctrl+2 navigates to the second tab</li>
</ul>
</li>
<li>Removed the Import Settings button and the corresponding Export Settings button in the Edit World Screen</li>
<li>Added a screen to easily enable/disable experimental features
<ul>
<li>The screen can always be found under the More-tab</li>
<li>In snapshots, a shortcut button can be found under the Game-tab</li>
</ul>
</li>
</ul>
Accessibility
<ul>
<li>Added an accessibility onboarding screen for players launching the game for the first time</li>
<li>Auto-Jump is now off by default</li>
<li>Added arrow key navigation</li>
<li>Added high contrast resource pack</li>
<li>The resource pack screen is now keyboard-navigatable</li>
<li>Changed how tooltips in the menu UI are positioned so buttons are still readable</li>
<li>Added a tooltip in the key binds screen that specifies which key binds are conflicting</li>
<li>Added a “Damage Tilt” accessibility option that controls the amount the camera shakes when being hurt</li>
<li>Added two new options in the accessibility menu for adjusting the speed and transparency of enchantment glints</li>
<li>Added a “Notification Time” accessibility option that changes how long notifications such as unlocked recipes, advancements, subtitles, and selected item names are visible for</li>
</ul>
Arrow Kew Navigation
<ul>
<li>Menu screens can now be navigated by using the arrow keys</li>
<li>When navigating with arrow keys, sliders need to be activated by pressing Enter or Space to start changing the value</li>
</ul>
High Contrast Resource Pack
<ul>
<li>Added a built-in resource pack that enhances the contrast of UI elements</li>
<li>Added a new option in the Accessibility menu that enables the high contrast resource pack</li>
<li>This only affects the menu UIs for now, but we’ll be looking to bring this to gameplay UIs in the future as well</li>
</ul>
<h3>Technical Changes</h3>
<ul>
<li>The data pack version is now 12</li>
<li>The resource pack version is now 13</li>
<li>Added a group of entities to display items, blocks, and text</li>
<li>Added entities to detect interactions and attacks</li>
<li>Added data-driven damage types</li>
<li>Added a damage command for applying damage to entities</li>
<li>Added ride command to mount and dismount entities</li>
<li>The clone command now supports cloning to and from different dimensions</li>
<li>A new string source is now available for the data modify command</li>
<li>New execute sub-commands: if dimension, if loaded, on, positioned over, summon</li>
<li>Added a new type of atlas configuration source: paletted_permutations</li>
<li>Pressing F3+S will now dump contents of dynamic textures (like atlases, maps, etc.) to screenshots/debug/</li>
<li>Added fallback fields to translate text components</li>
<li>Out-of-bound arguments in translate formats are no longer silently ignored</li>
<li>Added the following game events:
<ul>
<li>entity_dismount with a vibration frequency of 6</li>
<li>entity_mount with a vibration frequency of 7</li>
</ul>
</li>
<li>Changed the following game events:
<ul>
<li>item_interact_finish now has a vibration frequency of 2 instead of 14</li>
</ul>
</li>
<li>Removed heldItemTooltips option from options.txt</li>
<li>Added a network protocol feature for forcing a bundle of packets to be processed within the same client tick</li>
<li>Added –pidFile argument to the dedicated server command line for printing process id to file</li>
<li>The vanilla resource pack en_us language file is now sorted alphanumerically by key</li>
<li>Added show_notification field to recipes
<ul>
<li>Accepts a boolean which determines if a notification is shown when unlocking this recipe</li>
<li>defaults to true if isn’t specified</li>
</ul>
</li>
<li>A new recipe type smithing_transform has been added for the updated Netherite Upgrade recipe</li>
<li>A new recipe type smithing_trim has been added for the new Armor Trim recipe</li>
<li>A new recipe type crafting_decorated_pot has been added for the new Decorated Pot recipe</li>
<li>New registries trim_pattern and trim_material have been added for the armor trim system</li>
<li>Smithing table has temporarily two menu types
<ul>
<li>Old menu without the Smithing Template slot has been renamed to legacy_smithing
<ul>
<li>Will be removed when the Armor Trim feature stops being an experimental feature</li>
</ul>
</li>
<li>New menu with a Smithing Template slot was added called smithing</li>
</ul>
</li>
<li>Added new flag (value 128) to HideFlags NBT field for hiding armor trim item tooltips</li>
</ul>
Resource Pack Format
<ul>
<li>The enchantment glint now has two separate texture files: enchanted_glint_entity.png and enchanted_glint_item.png</li>
<li>The texture format used to dynamically scale buttons and sliders has been updated to always include fixed 20px borders on the left and right</li>
<li>Slider textures are now defined in a separate slider.png file</li>
<li>The Create New World screen now uses a separate light_dirt_background.png for its background, unlike other screens</li>
</ul>
<h3>Commands</h3>
<h4>Clone</h4>
The clone command now supports specifying the source and target dimensions.
New syntax:
clone [from <sourceDimension>] <begin> <end> [to <targetDimension>] <destination> …
Parameters:
<ul>
<li>sourceDimension: id of dimension to clone from</li>
<li>targetDimension: id of dimension to clone to</li>
</ul>
<h4>Damage</h4>
New command to apply damage to entities.
Syntax:
<ul>
<li>damage <target> <amount> [<damageType>] [at <location>]</li>
<li>damage <target> <amount> [<damageType>] [by <entity>] [from <cause>]</li>
</ul>
Parameters:
<ul>
<li>target: The entity to damage</li>
<li>amount: Amount of damage to inflict</li>
<li>damageType: The type of damage to inflict
<ul>
<li>This determines how the damage affects the entity as well as which death message is displayed</li>
</ul>
</li>
<li>entity: The entity inflicting the damage</li>
<li>cause: The cause of the damage, in the case of indirect damage
<ul>
<li>Example: When shot by an Arrow, the entity is the Arrow projectile while cause might be a Skeleton</li>
</ul>
</li>
<li>location: The location the damage originated at (when no entity caused the damage)
<ul>
<li>For instance, location might represent the location of a Bed exploding in the Nether</li>
</ul>
</li>
</ul>
<h4>Data</h4>
New source available:
<ul>
<li>string <entity|block|storage> [path] [start] [end] – reads a value as text, resulting in a string value</li>
</ul>
New arguments:
<ul>
<li>start: Index of first character to include at the start of the string</li>
<li>end: Index of the first character to exclude at the end of the string</li>
</ul>
<h4>Effect</h4>
<ul>
<li>infinite is now a valid option for effect durations
<ul>
<li>Infinite effect durations show up as “∞” in the player inventory view</li>
</ul>
</li>
</ul>
<h4>Execute</h4>
<h4>Execute If|Unless</h4>
New conditions available for the execute if|unless sub-command:
<ul>
<li>execute if|unless loaded <pos> – checks if the position given is fully loaded (regarding both blocks and entities)</li>
<li>execute if|unless dimension <dimension> – checks if the execution is in a matching dimension</li>
</ul>
Parameters:
<ul>
<li>pos: Block position to check</li>
<li>dimension: A dimension id</li>
</ul>
<h4>Execute On</h4>
New execute sub-command for selecting entities based on relation to the current executing entity:
<ul>
<li>execute on <relation></li>
</ul>
Relations:
<ul>
<li>vehicle – the entity that the executing entity is riding</li>
<li>passengers – all entities directly riding the executing entity (no sub-passengers)</li>
<li>controller – the entity that is controlling the executing entity (for example: first passenger in a boat)</li>
<li>owner – the owner of the executing entity, if it is a tameable animal (like cats, wolves, or parrots)</li>
<li>leasher – the entity leading the executing entity with a leash (might be a leash knot in case of being attached to a fence)</li>
<li>target – the attack target for the executing entity</li>
<li>attacker – the last entity that damaged the executing entity in the previous 5 seconds</li>
<li>origin:
<ul>
<li>shooter, if the executing entity is a projectile (like Arrow, Fireball, Trident, Firework, Thrown Potion, etc.)</li>
<li>thrower, if the executing entity is an item</li>
<li>source of effect, if the executing entity is an Area Effect Cloud</li>
<li>igniter, if the executing entity is a Primed TNT</li>
<li>summoner, if the executing entity is Evoker Fangs or a Vex</li>
</ul>
</li>
</ul>
If the relation does not apply to the executing entity or no entities are matching it, the selector returns zero elements.
<h4>Execute Positioned Over</h4>
New execute sub-command for finding positions on top of a heightmap. Changes the height of the execution position to be on top of the given heightmap.
Syntax:
<ul>
<li>execute positioned over <heightmap></li>
</ul>
<h5>Heightmaps</h5>
A heightmap records the highest position in a column of blocks according to some criteria. Available options:
<ul>
<li>world_surface: Any non-air block</li>
<li>motion_blocking: Any motion blocking material (e.g. ignores flowers and grass)</li>
<li>motion_blocking_no_leaves: Any non-leaf motion blocking material</li>
<li>ocean_floor: Any non-fluid motion blocking material</li>
</ul>
<h4>Execute Summon</h4>
New execute sub-command for summoning a new entity and binding the context (@s) to it. Meant to simplify entity setup and reduce the need for raw NBT editing.
Syntax:
<ul>
<li>execute summon <entity id></li>
</ul>
<h4>Fillbiome</h4>
<ul>
<li>The amount of network data transmitted when using the fillbiome command has been optimized</li>
</ul>
<h4>Title</h4>
<ul>
<li>All time arguments to title times are now time durations and work with t, s, and d suffixes</li>
</ul>
<h4>Weather</h4>
<ul>
<li>The duration of the weather change now matches the game’s regular weather cycle if not specified</li>
<li>The duration parameter is now a time duration in ticks and works with t, s, and d suffixes
<ul>
<li>To retain existing functionality, you need to add an s suffix to pre-existing commands</li>
</ul>
</li>
</ul>
<h4>Ride</h4>
New command to allow entities to start or stop riding other entities.
Syntax:
<ul>
<li>ride <target> mount <vehicle>
<ul>
<li>Makes a single target mount a single vehicle</li>
<li>The command will fail if:
<ul>
<li>vehicle is a player</li>
<li>target is already riding a vehicle</li>
<li>target and vehicle are the same entity</li>
<li>vehicle is already a passenger (direct or indirect) of target</li>
</ul>
</li>
</ul>
</li>
<li>ride <target> dismount
<ul>
<li>Dismounts target from any vehicle it is riding</li>
<li>Fails if target is not riding anything</li>
</ul>
</li>
</ul>
<h3>Damage Types</h3>
Damage Types are a new registry that can be extended through data packs. A Damage Type determines how damage is handled by the game. This includes which attributes the damage has as well as which death message is used when an entity dies due to that type of damage.
Example:
<pre><code>{ "exhaustion": 0.1, "message_id": "arrow", "scaling": "when_caused_by_living_non_player"
}
</code></pre>
Fields:
<ul>
<li>message_id: The message id used for deaths caused by this damage type
<ul>
<li>Will be combined with other string fragments to form a translation key</li>
</ul>
</li>
<li>exhaustion: The amount of hunger exhaustion caused by this damage type</li>
<li>scaling: Whether this damage type scales with difficulty levels. Possible values:
<ul>
<li>never: Damage is always the same</li>
<li>always: Damage always scales with difficulty</li>
<li>when_caused_by_living_non_player: Damage scales with difficulty if it was caused by a living entity who is not a player</li>
</ul>
</li>
<li>effects: Optional field controlling how damage manifests when inflicted on players. Possible values:
<ul>
<li>hurt (default): the default hurt sound</li>
<li>thorns: Thorns hurt sound</li>
<li>drowning: Drowning sound</li>
<li>burning: A single tick of burning sound</li>
<li>poking: Berry bush poke sound</li>
<li>freezing: Freeze tick sound</li>
</ul>
</li>
<li>death_message_type: Optional field that controls if special death message variants are used. Possible values:
<ul>
<li>default (default): No special death message logic is applied</li>
<li>fall_variants: Show a variant of fall damage death instead of a regular death message, e.g. death.fell.assist.item</li>
<li>intentional_game_design: Show the intentional game design message instead of a regular death message</li>
</ul>
</li>
</ul>
Damage type tags control many aspects of how damage from different sources is interpreted.
<h3>Predicates</h3>
<h4>Damage Type Predicates</h4>
The following fields have been removed from damage type predicates: is_projectile, is_explosion, bypasses_armor,bypasses_invulnerability, bypasses_magic, is_fire, is_magic, is_lightning.
A new tags array has been added, with the predicate matching if all entries match. Each entry has two fields:
<ul>
<li>id: The ID of a damage type tag</li>
<li>expected: Whether the damage is expected to have or not have the tag for the predicate to match</li>
</ul>
<h3>Game Rules</h3>
<ul>
<li>Added commandModificationBlockLimit, controlling the maximum number of blocks changed in one execution of clone, fill and fillbiome</li>
<li>Added doVinesSpread game rule, determining if vines will spread to nearby blocks
<ul>
<li>Defaults to true</li>
</ul>
</li>
</ul>
<h3>Text Components</h3>
Added an optional fallback field to translate text components.
<ul>
<li>The new field is a string that will be used in place of translation if it is missing</li>
<li>If fallback is missing, the old behavior (i.e. using the key itself as the translation) is preserved</li>
</ul>
<h3>Display Entities</h3>
Three new entities have been added for flexible display of items, blocks, and text
<ul>
<li>Those entities, similarily to markers, don’t tick and have no collisions or physics</li>
<li>Models render at entity position, with normal rotation around X and Y axis (so it can be controlled by teleport commands), but also with additional arbitrary model transform</li>
</ul>
<h4>Common Data Types</h4>
Tag contents for display entities include some new data types with a complex structure. Any form can be used for modifying data, but only one form is used for saving.
<h4>Transformations</h4>
Arbitrary affine transform.
<ul>
<li>Matrix form: array of 16 numbers, describing row-major matrix</li>
<li>Decomposed form (used for saving): object with following fields:
<ul>
<li>translation – 3d vector</li>
<li>left_rotation, right_rotation – rotation</li>
<li>scale – 3d vector</li>
<li>Transforms are composed in order translation, left_rotation, scale, right_rotation</li>
</ul>
</li>
</ul>
<h4>Rotations</h4>
<ul>
<li>Quaternion form (used for saving): array of 4 numbers, describing components (x, y, z, w)</li>
<li>Axis-angle form: object with following fields:
<ul>
<li>axis – unit 3d vector</li>
<li>angle – in radians</li>
</ul>
</li>
</ul>
<h4>Interpolation</h4>
Some properties of display entities can be interpolated. That means that clients will see gradual changes over time instead of instantaneous jumps.
Display entities keep track of current and previous values of interpolated values:
<ul>
<li>All properties marked as “interpolated” are part of a single interpolation set</li>
<li>Any update to interpolated property will cause all values of interpolation set to be saved as “current”
<ul>
<li>Data command executions that do not change value of property (even if it’s present in NBT) do not count as updates</li>
<li>Updates are synchronized to clients at most once per tick, so multiple updates within command will still count as a single update</li>
</ul>
</li>
<li>The last values generated before an update are saved as “previous”</li>
<li>If interpolation is enabled, the entity will transition between “previous” and “current” values over interpolation_duration ticks</li>
<li>Interpolation can be started by writing to the start_interpolation field (this field is not normally present in NBT)
<ul>
<li>The value in this field is a delay in ticks between client receiving the update and interpolation start</li>
<li>A value of 0 ticks means that interpolation will start in next client tick after receiving the update</li>
<li>Positive values increase this delay further</li>
</ul>
</li>
<li>Interpolation will end (entity fully in “current” state) in start_interpolation + interpolation_duration ticks after receiving the update</li>
<li>The interpolation target can be updated without setting start_interpolation, but it will still behave as if it was started at the moment of the last update to start_interpolation
<ul>
<li>That means that if the value is updated, but more than interpolation_duration ticks have passed since last start_interpolation update, the entity will immediately jump to new values</li>
</ul>
</li>
</ul>
<h4>Common Properties</h4>
All display entity types have the following fields:
<ul>
<li>transformation – the transformation applied to model (after normal entity orientation). Defaults to identity. Interpolated</li>
<li>billboard – option to control if entity should pivot to face player when rendered:
<ul>
<li>fixed – no rotation (default)</li>
<li>vertical – entity can pivot around its vertical axis</li>
<li>horizontal – entity can pivot around its horizontal axis</li>
<li>center – entity can pivot around its center point</li>
</ul>
</li>
<li>brightness – if present, overrides light values used for rendering. Omitted by default (which means rendering uses values from entity position). Object has two fields:
<ul>
<li>sky – value of skylight, 0..15</li>
<li>block – value of block light, 0..15</li>
</ul>
</li>
<li>view_range – maximum view range of this entity. Actual distance depends on client-side render distance and entity distance scaling. Default value 1.0 (roughly the same as fireball)</li>
<li>shadow_radius – size of shadow. Defaults to 0 (no shadow). Interpolated</li>
<li>shadow_strength – strength of the shadow. Controls the opacity of the shadow as a function of distance to block below. Defaults to 1. Interpolated</li>
<li>width, height – describe size of culling bounding box
<ul>
<li>Bounding box spans vertically y to y+height and horizontally width/2 in all directions from entity position</li>
<li>If either field is set to 0, culling is disabled</li>
<li>Both default to 0</li>
</ul>
</li>
<li>glow_color_override – override glow border color. Defaults to -1 (use team color). Alpha component is ignored</li>
</ul>
<h4>Item_Display</h4>
Displays a single item stack.
<ul>
<li>Stack can be changed with commands by setting slot container.0</li>
</ul>
Fields:
<ul>
<li>item – item stack to display. Same format as in inventory (example: {id: “minecraft:dirt”, Count: 1})</li>
<li>item_display – describes item model transform applied to item (as defined in display section in model JSON)
<ul>
<li>Values: none (default), thirdperson_lefthand, thirdperson_righthand, firstperson_lefthand, firstperson_righthand, head, gui, ground, fixed</li>
</ul>
</li>
</ul>
<h4>Block_Display</h4>
Displays a block state.
<ul>
<li>Does not display all block entities, even if they would normally be created on block placement (like chests)</li>
</ul>
Fields:
<ul>
<li>block_state – block state to display. Same format as item held by endermen (example {Name:”minecraft:dirt”})</li>
</ul>
<h4>Text_Display</h4>
Displays a text component.
Fields:
<ul>
<li>text – text to display. Components are resolved with the context of the display entity</li>
<li>line_width – line width used to split lines (note: new lines can be also added with \n characters). Defaults to 200</li>
<li>text_opacity – opacity (alpha component) of rendered text. Defaults to 255. Interpolated</li>
<li>background – color of background. Includes alpha channel. Defaults to 0x40000000. Interpolated</li>
<li>default_background – if true, rendering uses default text background color (same as in chat). Defaults to false</li>
<li>shadow – whether the text should be displayed with a shadow. Defaults to false</li>
<li>see_through – whether the text should be visible through blocks. Defaults to false</li>
<li>alignment – how the text should be aligned
<ul>
<li>Values: center (default), left, right</li>
</ul>
</li>
</ul>
Note: text display backgrounds uses new shader types rendertype_text_background and rendertype_text_background_see_through.
<h3>Interaction Entities</h3>
A new type of entity that records attacks (“left clicks”) and interactions (“right clicks”). Interactions are invisible and of a custom size.
Fields:
<ul>
<li>width: Width of the entity’s bounding box (default 1)</li>
<li>height: Height of the entity’s bounding box (default 1)</li>
<li>attack: Records the last attack action on the entity</li>
<li>interaction: Records the last interaction action on the entity</li>
<li>response: Boolean specifying if interacting should trigger a response (arm swing, sound effects, etc – default false)</li>
</ul>
<h4>Action Format</h4>
When an action is stored, it always has two fields:
<ul>
<li>player: The UUID (in standard integer array format) of the player performing the action</li>
<li>timestamp: The timestamp of the game tick when the event happened (stored as a long)</li>
</ul>
<h4>Advancement Triggers</h4>
<ul>
<li>Interacting with an Interaction entity triggers player_interacted_with_entity</li>
<li>Attacking an Interaction entity triggers player_hurt_entity</li>
</ul>
<h4>Execute On With Interactions</h4>
The Interaction entity targets the player who last interacted with it. That makes the following possible:
<ul>
<li>execute on attacker: execute as the last player who attacked the entity</li>
<li>execute on target: execute as the last player who interacted with the entity</li>
</ul>
<h3>Tags</h3>
<h4>Block Behavior</h4>
<ul>
<li>Fire burns out faster in certain biomes, and this is now controlled by the increased_fire_burnout biome tag</li>
</ul>
<h4>Mob Spawning</h4>
<ul>
<li>The only_allows_snow_and_gold_rabbits biome tag has been renamed to spawns_gold_rabbits to match its behavior</li>
<li>White Rabbit variants are now controlled by the spawns_white_rabbits biome tag</li>
<li>Fox variants are now controlled by the spawns_snow_foxes biome tag</li>
</ul>
<h4>Mob Behavior</h4>
<ul>
<li>Snow Golems melting in warm biomes is now controlled by the snow_golem_melts biome tag</li>
<li>Only mobs in the dismounts_underwater entity tag will now force the rider to dismount when underwater</li>
</ul>
<h3>Network Protocol</h3>
<ul>
<li>Clients now reset their Secure Chat session state when receiving the login packet</li>
</ul>
<h4>Packet Bundles</h4>
<ul>
<li>Added new delimiter packet to clientbound game protocol</li>
<li>All packets between two delimiters are guaranteed to be processed within the same tick</li>
<li>For security reasons this feature is not supported in the serverbound direction</li>
</ul>
<h3>Paletted Permutations</h3>
<ul>
<li>paletted_permutations is a new type of atlas configuration source used to dynamically generate new textures in memory based on a set of color palettes</li>
<li>Color palettes allow you to swap out the colors of a texture without having to supply all files for the variants of a texture in a resource pack</li>
<li>This is useful for things like armor trims, where you want to be able to change the color of parts of the armor without having to create a new texture for each color</li>
<li>The paletted_permutations source has a set of required parameters:
<ul>
<li>textures A list of namespaced locations of base textures
<ul>
<li>These textures will be used to generate variants of them that have been modified by color palettes</li>
</ul>
</li>
<li>palette_key A namespaced location of a color palette key file
<ul>
<li>A color palette key is used to define the set of key pixel colors we want to swap out with the color palettes defined below</li>
</ul>
</li>
<li>permutations A map of permutations from suffix to a namespaced location of a color palette file
<ul>
<li>The suffix is appended at the beginning to the resource location of the output variant textures, with a _ character separating the suffix and the base texture name</li>
<li>The color palette is a texture file with a set of pixels that are used for replacing pixels that match the color palette key in each base texture</li>
<li>The number of pixels in each color palette must be the same as that of the palette_key defined for this source</li>
<li>Key matching is done by comparing the RGB values of each pixel in the palette_key to the RGB values of each pixel in the color palette</li>
<li>The alpha channel is ignored for key matching, but in the resulting texture the alpha channel is multiplied with the color palette’s alpha channel</li>
<li>Pixels that do not match the palette_key are copied over to the resulting texture as-is</li>
</ul>
</li>
</ul>
</li>
<li>After defining a paletted_permutations source, you can then reference those namespaced output textures in other resources in your resource pack</li>
</ul>
For example, if you have the following paletted_permutations source:
<pre><code>{ "type": "paletted_permutations", "textures": [ "minecraft:item/leather_helmet", "minecraft:item/leather_chestplate", "minecraft:item/leather_leggings", "minecraft:item/leather_boots" ], "palette_key": "minecraft:colormap/color_palettes/leather_armor_color_key", "permutations": { "red": "minecraft:colormap/color_palettes/red", "green": "minecraft:colormap/color_palettes/green", "blue": "minecraft:colormap/color_palettes/blue" }
}
</code></pre>
You can then reference the resulting textures in other resources like this:
<pre><code>{ "textures": { "layer0": "minecraft:item/leather_helmet_red", "layer1": "minecraft:item/leather_chestplate_green", "layer2": "minecraft:item/leather_boots_blue" }
}</code></pre>
<h3>Trim Patterns & Maternals</h3>
<ul>
<li>Trim patterns and materials for armor are defined by the server through the trim_pattern and trim_material registry respectively
<ul>
<li>As a result, new trim patterns and materials can be added via data packs</li>
</ul>
</li>
<li>These are synchronized to clients when they join the server
<ul>
<li>However, clients must have an accompanying resource pack to see those registered trim patterns and materials</li>
<li>The paths to these textures are inferred based on the filename of the pattern json, and will try to find the textures within the same namespace as the trim pattern’s name field</li>
</ul>
</li>
<li>The following data is defined by a trim pattern:
<ul>
<li>asset_id which is a namespaced id used to infer texture locations and localization</li>
<li>template_item which is the id of the smithing template item used to apply the trim pattern</li>
<li>description which is a text component used for displaying the pattern name of an armor trim when hovering an armor itemstack</li>
</ul>
</li>
<li>The following data is defined by a trim material:
<ul>
<li>asset_name which is a string used as a suffix for armor trim texture locations</li>
<li>ingredient which is the id of the ingredient item used to apply the trim material</li>
<li>item_model_index which is a float which defines the item model override each armor item model should target to change their visuals for this material</li>
<li>override_armor_materials which is an optional map of armor material to overridden color palette
<ul>
<li>Map key is the armor material that this trim material wants to override with a different color palette</li>
<li>Map value is the name of the color palette that will be used when this trim material is applied to an armor piece with the corresponding armor material</li>
</ul>
</li>
<li>description which is a text component used for displaying the material name of an armor trim when hovering an armor item stack
<ul>
<li>The style defined in this description is applied to the armor trim pattern description as well</li>
</ul>
</li>
</ul>
</li>
</ul>
<h3>Experimental Features</h3>
The following changes only apply when one or more Experiments is turned on, either by activating the corresponding experimental data pack or by turning it on in the Experiments screen while creating the world.
<ul>
<li>Added Smithing Template items</li>
<li>Redesigned the Smithing Table</li>
<li>Changed how Netherite equipment is crafted</li>
<li>Added a new armor trimming system to visually customize your armor</li>
<li>Added Sniffer mob and Torchflowers</li>
<li>Added the Cherry Grove biome</li>
<li>Added Archaeology</li>
<li>Mob Heads can now be placed on top of Note Blocks without sneaking</li>
</ul>
<h4>Smithing Templates</h4>
<ul>
<li>Smithing Tables have been redesigned into a workstation for physical equipment upgrades and modifications</li>
<li>Alongside slots for combining a piece of equipment and materials, there is now a required slot for an item type called Smithing Templates</li>
<li>Smithing Templates define what type of upgrade you will be making to equipment
<ul>
<li>It specifies both what type of items you can upgrade, and which ingredients are valid to customize the upgrade</li>
<li>There are currently two categories of Smithing Templates: Armor Trim and Netherite Upgrade</li>
</ul>
</li>
<li>Smithing Templates are consumed when used to upgrade an item in the Smithing Table</li>
<li>You can craft a copy of a Smithing Template in the Crafting Table with 7 diamonds + 1 block of material that the template is made out of + 1 smithing template, which will output 2 of the same Smithing Template</li>
</ul>
<h4>Netherite Equipment</h4>
<ul>
<li>Netherite equipment crafting now also requires a Netherite Upgrade Smithing Template</li>
<li>Netherite Upgrade Smithing Templates can be found randomly in all Bastion Remnant chests, and there is a guarantee of 2 in every Treasure Room Bastion Remnant</li>
<li>This change was made for a variety of reasons:
<ul>
<li>Increase the time players utilize Diamond equipment before Netherite</li>
<li>Make Netherite equipment a more significant achievement in the game’s progression</li>
<li>Adapt Netherite more naturally into the new Smithing Table crafting system</li>
</ul>
</li>
</ul>
<h4>Armor Trims</h4>
<ul>
<li>You can now visually customize your armor with a variety of unique trims at the Smithing Table</li>
<li>Armor trims are purely visual with no gameplay benefits, and can only be applied to Helmets, Chestplates, Leggings, and Boots
<ul>
<li>All trim patterns are visually the same on an armor’s item icon, but the color will still change based on the trim material</li>
<li>To check which trim pattern a piece of armor has, you can hover over it in the inventory</li>
</ul>
</li>
<li>Armor Trim Smithing Templates can be found all throughout the world, and each of the following structures contains its own unique Smithing Template:
<ul>
<li>Pillager Outpost: Sentry Armor Trim</li>
<li>Desert Pyramid: Dune Armor Trim</li>
<li>Shipwreck: Coast Armor Trim</li>
<li>Jungle Temple: Wild Armor Trim</li>
<li>Ocean Monument: Tide Armor Trim</li>
<li>Ancient City: Ward Armor Trim</li>
<li>Woodland Mansion: Vex Armor Trim</li>
<li>Nether Fortress: Rib Armor Trim</li>
<li>Bastion Remnant: Snout Armor Trim</li>
<li>Stronghold: Eye Armor Trim</li>
<li>End City: Spire Armor Trim</li>
</ul>
</li>
<li>Smithing Templates are found in chests in their respective structure
<ul>
<li>The Ocean Monument has no chests, Elder Guardians sometimes instead drop a Smithing Template upon death</li>
</ul>
</li>
<li>Some Armor Trim Smithing Templates are rarer than others, so be on the lookout for them to impress your friends!</li>
<li>An armor trim has two properties: a pattern and a material
<ul>
<li>The pattern is defined by the Smithing Template used to apply the trim and represents the visual pattern of the trim</li>
<li>The material is defined by what ingredient you used to apply the trim and represents the color of the trim</li>
</ul>
</li>
<li>The viable ingredients you can use to define the color of your armor trim are the following:
<ul>
<li>Iron, Copper, Gold, Lapis, Emerald, Diamond, Netherite, Redstone, Amethyst, Quartz</li>
</ul>
</li>
</ul>
<h4>Sniffer</h4>
<ul>
<li>The Sniffer is the mob vote winner of Minecraft Live 2022</li>
<li>Sniffers cannot be tempted or tamed</li>
<li>Sniffers are passive, friendly mobs</li>
<li>Sniffers sniff the air and occasionally dig for seeds, which produce a Torchflower Seed</li>
<li>Sniffers can be bred by feeding them Torchflower Seeds</li>
<li>The Sniffer is currently only available as a Spawn Egg in the creative inventory</li>
</ul>
<h4>Torchflowers</h4>
<ul>
<li>The Torchflower seed can be planted on farmland and grows into a flower</li>
<li>The seed can be used to breed two Sniffers</li>
<li>The full-grown flower can be harvested and replanted but can also be crafted into a dye</li>
</ul>
<h4>Cherry Groves</h4>
<ul>
<li>Added a new Cherry Grove biome, with pretty cherry blossom trees
<ul>
<li>The biome can be found in the mountains, in similar places as Meadows</li>
</ul>
</li>
<li>Added a new Cherry wood set, with all the corresponding wooden things you can make from it</li>
<li>Cherry Leaves have pink particles falling underneath</li>
<li>Added a new Pink Petals block with lots of pink flowers on the ground
<ul>
<li>Each pink petal block can contain up to 4 petals</li>
<li>Using bone meal on it increases the number of petals</li>
<li>Placing a petal on a block increases the number of petals</li>
<li>Mining the block gives you the number of petals in the block</li>
</ul>
</li>
</ul>
<h3>Archaeology</h3>
<h4>The Brush</h4>
<ul>
<li>The brush is a craftable item you can use to brush things</li>
</ul>
<h4>Suspicious Sand</h4>
<ul>
<li>Can be found in Desert Temples and Desert Wells</li>
<li>This fragile block is hard to spot and easy to destroy, so be careful!</li>
<li>Brushing the Suspicious Sand with a Brush will extract objects that were buried long ago</li>
</ul>
<h4>Pottery Shards</h4>
<ul>
<li>Pottery Shards have pictures on them</li>
<li>They cannot be crafted and are only found by brushing Suspicious Sand</li>
</ul>
<h4>Decorated Pots</h4>
<ul>
<li>Crafting four Pottery Shards together will create a Decorated Pot with a picture on each side</li>
<li>Brick items can be used instead of Pottery Shards in the Decorated Pot recipe
<ul>
<li>The sides that were made from Brick items will not have pictures</li>
</ul>
</li>
<li>Smash a Decorated Pot with any block-breaking tool to break it apart and get the Pottery Shards back
<ul>
<li>Hitting the pot with bare hands, silk touch tools, or any other item, will drop an intact pot instead</li>
</ul>
</li>
</ul>
<h3>Fixed Bugs in 1.19.4</h3>
Around 150 bugs were fixed in this release. View the <a href="https://bugs.mojang.com/issues/?filter=27608">list on the issue tracker</a>.
</div>

https://www.sickgaming.net/blog/2023/03/14/minecraft-java-edition-1-19-4/