![]() ![]() The minecraft:profile component no longer requires the name field to be present.translation_key (string) is a translation key prefix.custom:pattern resolves to assets/custom/textures/entity/banner/pattern.png, assets/custom/textures/entity/shield/pattern.png asset_id (namespaced string) is used to resolve texture locations.Banner Patterns will now be loaded into a dynamic registry from data packs ( data//banner_pattern/).If used alone, it will return total number of items in stacks that match predicates.is the same as item predicate in clear command.can accept single slot (like container.0) or a range (like container.*).entity (selector can return multiple entities).is the same as one used in item command, i.e.execute if|unless items command can be used to count items.Crafting table (or any other slots on other screens) are not included Note: this includes only player's inventory crafting slots.player.crafting.0 - player.crafting.3, player.crafting.* - player's crafting slots.Note: this information is not available in creative mode.player.cursor - item held by player on screen.armor.* - contains armor.head, armor.chest, armor.legs, armor.feed, armor.body.weapon.* - contains weapon.mainhand and weapon.offhand.villager.* - contains villager.0 to villager.7.enderchest.* - contains enderchest.0 to enderchest.26.inventory.* - contains inventory.0 to inventory.26.hotbar.* - contains hotbar.0 to hotbar.8.container.* - contains container.0 to container.53.Unless specified, existing commands can still only work on single slots.Slot names (used in item commands and slots entity predicates) now include slot ranges."condition": "minecraft:entity_properties", For slot ranges, only one slot needs to match for whole entry to pass.The field contains a map of slot names (same as ones used in item commands) to item predicate.New entity field slots allows to check single or multiple slots on any entity.This result now also accepts components data.The result field for recipe types smelting, blasting, smoking and campfire_cooking is now an item stack format without a count, which means you'll need to specify an object with an id field.Recipe types crafting_shaped, crafting_shapeless, stonecutting and smithing_transform now accept components for the result item stack. ![]() If the field is missing in data, will still fall back to 1.For now, the count field on Item Stacks is always stored again, even if 1.The SkullOwner and ExtraType fields in Player Head blocks have been replaced with a profile field, with the same format as the item component. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |