The current minecraft:bee_nest_destroyed trigger is limited to bee nests and hives. To enhance its utility, I propose generalizing it to work with any block, allowing players and creators to define specific block properties and conditions.
Changes:
-
Generalized Trigger:
Rename the trigger tominecraft:block_destroyed, enabling it to apply to any block rather than being limited to bee nests and hives. -
Support for Block States and NBT:
Allow specifying block states (e.g., orientation) and NBT data (e.g., container contents or custom names), giving creators more precise control over the target block. -
Flexible Number Providers:
For fields requiring numerical values, enable both fixed numbers and min-max ranges. For example, this could set conditions like destroying a block with a certain durability (if that is even feasible for NBT).
Example:
{
"criteria": {
"destroy_block": {
"trigger": "minecraft:block_destroyed",
"conditions": {
"block": "minecraft:oak_log",
"state": {
"axis": "y"
},
"nbt": "{CustomName:'{\"text\":\"Special Log\"}'}"
}
}
}
}
This example triggers when a vertically oriented oak log with a custom name is destroyed. By generalizing the trigger and allowing property customization, advancements can become far more versatile and engaging for creators and players alike.
Please sign in to leave a comment.
1 Comments