Bedrocken

Bedrocken is a free VS Code extension for building Minecraft Bedrock behavior packs, resource packs, and add-ons. It is best suited to developers who want a code-first workflow with Bedrock-aware project utilities, rather than a visual authoring environment. Its strongest advantage is bringing setup, linking, generation, and context-sensitive completion into one editor.

Overview

Bedrocken concentrates the recurring mechanics of Bedrock add-on development inside VS Code. Its project commands can create a com.mojang project, switch between projects in a designated folder, and export behavior packs, resource packs, or complete add-ons. Opening a manifest.json provides commands to link behavior and resource packs and to add scripts, which is useful when pack relationships would otherwise be configured manually.

This is a code editor extension, not a broad Minecraft creation suite. The code-only mode favors users comfortable editing JSON and scripts; people looking for visual modeling or drag-and-drop construction should choose a different type of tool.

Key features

Project and pack workflow

The Create New Project command builds a com.mojang project and copies the behavior pack description into the resource pack description by default. That saves initial typing, although projects needing distinct descriptions will require an edit afterward. Project switching is limited to the designated projects folder, so its convenience depends on keeping work organized there.

Direct export for behavior packs, resource packs, and add-ons gives a clear handoff path when a project is ready to package. Manifest actions for linking packs and adding scripts keep common relationships close to the file that defines the project.

Autocomplete and generation

Dynamic autocomplete covers Bedrock identifiers and project content across components, entity files, recipes, loot tables, localization files, and JSON asset files. That breadth is most valuable in add-ons with many interdependent definitions, where contextual suggestions can reduce repeated reference checks and naming errors. It does not replace understanding the underlying schemas, but it makes a code-heavy workflow more productive.

Preset commands and snippets generate files and handle simple tasks. The Generate command specifically supports texture_list.json, sound_definitions.json, item_texture.json, and terrain_texture.json. From a block.json, users can select an item short name or texture path; Bedrocken registers the chosen texture in the item atlas and creates an item.json. These targeted generators are practical for repetitive asset setup, though the documented coverage is centered on the listed file types.

Entities and scripts

Custom entity tools and scripting support extend Bedrocken beyond basic pack editing. Developers building behavior that depends on scripts or custom entities therefore get a more complete code workflow than with a plain text editor, while purely visual creators gain little from these features.

Pricing

There is one free plan, with no paid tier or seat and quota structure described. That makes Bedrocken straightforward for individual developers and small teams that already use VS Code. The trade-off is dependency on a compatible editor installation: projects using an older VS Code release will not meet the stated requirement.

Platforms

Bedrocken is distributed as an extension for Windows, macOS, and Linux. Its editor mode is code, and the package requires VS Code compatibility ^1.87.0. The repository identifies Xterionix as publisher and uses the GPL-3.0 license.

Who it's for

Choose Bedrocken if you develop Bedrock add-ons in VS Code and want project creation, pack linking, exports, scripts, generators, and Bedrock-focused autocomplete in the same environment. It is particularly suitable for structured projects spanning entities, recipes, loot tables, localization, and asset JSON.

It is a weaker fit for creators who need visual modeling, a graphical interface, or a workflow outside VS Code. The designated-project-folder approach also matters to anyone whose projects are spread across unrelated locations.

Pros and cons

Pros

• Bedrock-specific completion: suggestions cover identifiers and a wide range of project files, helping with interconnected JSON work.
• Useful pack operations: linking manifests, adding scripts, switching projects, and exporting packs address common setup and delivery tasks.
• Targeted file generation: presets, snippets, texture and sound definition generators, and block-to-item creation reduce repetitive authoring.
• No purchase barrier: the extension is free on all three desktop platforms.

Cons

• Code-only focus: it does not suit users seeking visual or drag-and-drop creation.
• VS Code dependency: installation requires compatibility with VS Code ^1.87.0.
• Folder-bound switching: project switching works from a designated projects folder rather than an arbitrary collection of locations.
• Default description carry-over: new resource packs inherit the behavior pack description until changed.

Alternatives

Blockception Minecraft Bedrock Development is the closest alternative when you want another free VS Code extension for Minecraft Bedrock add-ons and Minecraft Education Edition. Pick Visual Studio Code instead when you need the general-purpose editor itself rather than Bedrock-specific tooling.

Snowstorm is a better choice when broad platform coverage, including web and mobile, matters. Choose Blockbench for a free, general 3D creation tool rather than a code-first Bedrock extension. JsonForge fits users seeking a free, open-source web or Electron JSON application, while mcblend is the alternative for a Blender add-on workflow.

Minecraft Launcher is for obtaining and launching Minecraft rather than authoring add-ons. McpeTool offers a free MIT-licensed option across API, self-hosted, and desktop environments. For a broader directory of options, see Minecraft Add-on Editors.

Verdict

Bedrocken is a strong choice for Bedrock developers who already work in VS Code and want free, focused help with project structure, pack relationships, generation, scripting, and autocomplete. Its main reason to look elsewhere is equally clear: creators who need visual authoring, broader editor independence, or projects outside its designated folder will find its code-first, VS Code-bound workflow restrictive.