behavior_pack/manifest.json example:
"format_version": 2,
"header":
"name": "My Converted Addon - BP",
"description": "Behavior pack from Java mod",
"uuid": "<generate a unique UUID>",
"version": [1, 0, 0],
"min_engine_version": [1, 20, 0]
,
"modules": [
"type": "data",
"uuid": "<generate another UUID>",
"version": [1, 0, 0]
]
resource_pack/manifest.json is similar but with "type": "resources". Use online UUID generators.
Example mod.json file:
"name": "My Mod",
"description": "This is my mod",
"version": "1.0",
"author": "Your Name"
Your MCAddon file is now ready to be installed and used in Minecraft.
Rename the .zip file to .mcaddon and place it in your Minecraft addons folder. The location of this folder varies: how to convert jar to mcaddon
Then, launch Minecraft: Bedrock Edition. Your addon should now be available.
Key Insight: Only the assets (textures, models, sounds) and simple data-driven parts (like loot tables or recipes) can be reused. All entity behaviors, custom blocks, and logic must be rewritten. behavior_pack/manifest
Alternative: Look for an existing Bedrock add-on that does something similar, or commission a developer to rewrite the mod properly.
There is no tool that magically converts .jar to .mcaddon. This guide provides a manual recreation method for simple mods only. For complex mods, consider using Minecraft Bedrock’s Script API (JavaScript) to add custom logic, but even that has significant restrictions compared to Java modding. "format_version": 2, "header": "name": "My Converted Addon -
Good luck, and happy converting!