template:
You must manually map each Java property to a Bedrock component. Java recipe (JSON):
"format_version": "1.20.30", "minecraft:block": "description": "identifier": "converted:ruby_block" , "components": "minecraft:material_instances": "*": "texture": "ruby_block", "render_method": "opaque" , "minecraft:destructible_by_mining": "seconds_to_destroy": 2 , "minecraft:destructible_by_explosion": "explosion_resistance": 6
| Feature | Java (JAR) | Bedrock (MCADDON) | |---------|------------|-------------------| | Language | Java | C++ / JSON | | Render Engine | Lightweight / OpenGL | RenderDragon (custom) | | Entity System | NBT + Classes | Component-based JSON | | Scripting | JavaScript (via Rhino) / Java | JavaScript (via GoDot) / TypeScript |
"parent": "block/cube_all", "textures": "all": "mod:block/ruby_block"
import world, ItemStack from "@minecraft/server"; world.afterEvents.itemUseOn.subscribe((event) => if (event.itemStack?.typeId === "converted:fire_sword") event.target.setFire(5); ); A verified MCADDON means Minecraft Bedrock recognizes it as safe, signed, and properly formatted. Unverified addons cause the dreaded "Import Failed. This pack is not valid" error. Step 5.1: Validate Internally Use Microsoft’s Validation Tool (part of the Minecraft Addon SDK):