Minecraft Technical Wishlist

wishlist.md

Minecraft Technical Wishlist

• Ability to detect block NBT within loot tables
• Addition of an optional loot table argument in /loot ... mine
• New entry type in loot tables that runs a function
• data resolve to resolve text components in NBT
• Loot table tags. With a new entry type loot_table_tag, similar to tag. It also has expand that acts the same.
• New entry type in loot tables that drops xp. If the loot table is used in a container, the container will store the xp, like it does currently with furnaces.
• New entry type in loot tables that will insert the loot table that you are replacing. For example if you want to add a new drop to a vanilla loot table without copying the vanilla loot table. This allows multiple datapacks to each add their own drops to an existing loot table. https://gist.github.com/misode/728b6251adfcdef5f71e50e51e002059
• Selecting sublists in NBT arrays with nbt paths. This could have the following syntax: Items[2..5]
• Limiting the selection of an NBT path. This could have the following syntax: Items[{id:"minecraft:stone"}:1]
• Ability to manipulate NBT strings with /data just as if they were lists. This includes appending to string and taking a character from a string.
• Events. This would be a separation between triggers and the actual advancements. The events could be triggered not only by players. More triggers would be available, and the correct execution position and executor would be set depending on the trigger. For example we would be able to know the coordinates of placed/mined blocks.