Skip to content

Releases: dadeeen/MCBE_Inventory_Editor

MCBE Inventory Editor v0.8.1

Choose a tag to compare

@github-actions github-actions released this 23 Oct 22:46

What's changed in v0.8.1

  • Apply valid slot edits immediately; write to the world only on Save.
  • Fix undo history, repeated edits and preservation of item data.
  • Recover interrupted database updates and cached banner and axolotl previews.
  • Improve request timeouts, presence polling and write guards; update dependencies.

Updating

Windows: close the editor, extract the new ZIP into a fresh folder and copy your existing data folder. Browser runtime: run setup.bat before start.bat.

Download _windows_x64.zip (WebView2 required, unsigned) or _runtime.zip, with the matching .sha256 file.

Back up your world and stop Minecraft or the Bedrock server before editing. Mount creation remains experimental.

README · Deutsch · Security

MCBE Inventory Editor v0.8.0

Choose a tag to compare

@github-actions github-actions released this 22 Oct 21:52

Release packages for the Minecraft Bedrock Inventory Editor.

What changed in v0.8.0

  • Portable Windows app: A separate x64 ZIP starts MCBEInventoryEditor.exe in a WebView2 window with bundled Python, native file dialogs and an unsaved-change guard. Window preferences and the selected language persist between starts. WebView2 Runtime is required. The window stays on the editor's local origin, and guarded restore recovery works without installing Python separately.
  • Local lifecycle: Browser servers run until explicitly stopped; heartbeat shutdown is opt-in. The desktop closes with its window after active writes finish.
  • Startup recovery: A persistent notice offers a reload if the interface fails to initialize. Repeated local launches reopen an identified editor instance; unrelated port conflicts remain explicit errors.
  • Item inspector: A read-only dialog provides a draft overview, searchable typed NBT tree and JSON view. It distinguishes loaded originals from edits and supports keyboard, touch and copying on narrow screens.
  • Special item editors: Edit shulker and bundle contents, books, fireworks and banners. Contained items share inventory validation and the existing item browser, and inventory search includes nested contents. The picker explains shulker nesting and bundle capacity restrictions. Banner previews use Bedrock textures and work offline after downloading them.
  • Explicit Apply: Slot inputs stay pending until Apply accepts them. A visible notice identifies open inputs, switching slots offers a discard confirmation, and saving remains disabled while inputs are pending. Accepted changes remain in the inventory draft until explicitly saved to the world.
  • Item preservation: Repeated and nested edits preserve unknown metadata and unchanged values. Cancelling retains the parent draft; replacing an item cannot restore old hidden contents. Unsupported special-data formats remain read-only.
  • Controls and history: Item menus, search results and dialogs support keyboard navigation and focus recovery. Accepted edits form distinct undo steps; unchanged edits add none. The session history describes moves, swaps and copies, and clearing it preserves drafts and undo steps. German and English item names follow Bedrock's language data.
  • Item database updates: The preview distinguishes pending changes, current data and partial writes. It explains source-version differences, stack limits and description changes, with compact technical details. Unrelated Microsoft Learn page changes do not trigger recurring updates.
  • Restore permissions: Restores preserve POSIX ownership, permissions and ACLs. Metadata-copy failures stop before replacing the world. The Docker instructions explain the shared UID/GID configuration needed to retain server ownership.
  • Write safety and other fixes: Committed writes and reload-required responses preserve the correct save state. Mount placement is rechecked at the locked write boundary and avoids wither roses. Local probes bypass configured HTTP proxies. The System theme follows OS changes, and dialogs adapt to narrow screens.

Desktop dependencies are pinned separately. Browser/Docker runtime dependencies, the world format and saved preferences remain unchanged.

Validation

Release checks cover Python and browser tests, dependency audits, package contents and desktop/Docker startup. See the desktop validation guide and engine checks for scope and required manual checks. Automated startup checks do not establish clean-machine behavior or Minecraft compatibility. Mount creation remains experimental; verify edited world copies in Minecraft.

Upgrading

Python 3.12–3.14 remain supported for the browser runtime. Run setup.bat once before start.bat to verify its hash-pinned dependencies. The portable Windows app includes Python: close the editor, extract the complete new ZIP into a fresh folder and copy your existing data folder before starting the EXE. Preserve worlds and backups separately; keep the old installation available for rollback.

An installation without a saved layout preference opens in Classic. Existing layout, theme and language preferences remain selected.

For installations with additional packs upgrading from before v0.6.3: update Vanilla icons once to prepare the base texture mappings. Rescanning alone cannot add these mappings to an older Vanilla cache. When skipping several versions, consult the notes of the skipped releases.

Before every edit: stop Minecraft or the Bedrock server and create a complete, independent copy of the world. Keep that copy until the edited world has been verified in Minecraft. App-created backups are an additional safeguard, not a replacement.

Download _windows_x64.zip for the portable Windows app or _runtime.zip for the browser runtime. The Windows app is unsigned. The matching .sha256 file lets you verify download integrity, not publisher identity. The automatically generated Source code archives are repository snapshots, not ready-to-run packages.

Docker images are published to ghcr.io/dadeeen/mcbe-inventory-editor. Prefer the exact tag of the chosen release for deployments; latest and minor tags are intentionally mutable.

MCBE Inventory Editor v0.7.2

Choose a tag to compare

@github-actions github-actions released this 15 Oct 14:01

Runtime package for the Minecraft Bedrock Inventory Editor.

What changed in v0.7.2

  • Visual refresh: Reworked Classic, Studio and Focus layouts with clearer navigation, reorganized controls and better use of screen space. Studio keeps the inventory grid and inspector aligned on wide screens.
  • Write-outcome safety: Import, migration and restore keep further writes blocked after an uncertain response or an explicit reload requirement. Resetting a view or refreshing only the player list cannot release that protection; a successful player or explicit world load can.
  • Restore refresh and context changes: A completed restore with a failed follow-up reload remains protected. Switching players in the same restored world preserves the newer view but requires reloading it before further writes; switching to another world leaves that world untouched.
  • Confirmation lifecycle: Unknown-server confirmation is limited to the current operation and its matching presence-conflict retry. A possibly completed write or a response requiring reload must not trigger another automatic attempt.
  • Editor workflows: Improved effect editing, equipment handling and feedback for updates and file operations.
  • Catalog validation: Item updates report changes and validation results, including localized names, stack limits and durability. Conflicting effect or enchantment identities block the affected editor section while preserving existing player data.
  • Runtime and input handling: Explicit session secrets take precedence over saved setup state. Log access requires authentication for Docker and LAN exposure. Malformed redirects, guard tokens, setup values and player archives produce controlled failures.
  • Backups and desktop paths: Backups accept filesystem dates outside the ZIP timestamp range. Folder dialogs and updater output preserve Unicode text, and updater subprocesses resolve data paths before changing directories. The NBT inspector preserves large integers and non-finite values in its display.

This patch adds no dependencies and does not change the on-disk world format or saved layout preferences.

Validation

Release preparation checks the full Python suite, backend branch coverage, browser flows, JavaScript regressions, seven layout and mount smoke scripts, dependency audits, runtime-package contents and integrity, and Docker startup and graceful shutdown with a read-only root filesystem. Visual checks cover desktop and emulated narrow screens, including the light theme.

These checks use synthetic fixtures and do not establish compatibility with every Minecraft version, gameplay action or add-on. Version-specific engine evidence and its limitations are documented in the engine checks and save contract. Mount creation remains experimental; verify edited world copies in Minecraft.

Upgrading

Python 3.12–3.14 remain supported. Run setup.bat once before start.bat to verify the hash-pinned runtime dependencies. Preserve worlds, backups and runtime data separately when replacing an installation.

An installation without a saved layout preference opens in Classic. Existing layout, theme and language preferences remain selected.

For installations with additional packs upgrading from before v0.6.3: update Vanilla icons once to prepare the base texture mappings. Rescanning alone cannot add these mappings to an older Vanilla cache. When skipping several versions, consult the notes of the skipped releases.

Before every edit: stop Minecraft or the Bedrock server and create a complete, independent copy of the world. Keep that copy until the edited world has been verified in Minecraft. App-created backups are an additional safeguard, not a replacement.

Download the asset ending in _runtime.zip together with its .sha256 file. The automatically generated Source code archives are repository snapshots, not ready-to-run packages.

Docker images are published to ghcr.io/dadeeen/mcbe-inventory-editor. Prefer the exact version tag 0.7.2 for deployments; latest and minor tags are intentionally mutable.

MCBE Inventory Editor v0.7.1

Choose a tag to compare

@github-actions github-actions released this 13 Oct 21:16

Runtime package for the Minecraft Bedrock Inventory Editor.

What changed in v0.7.1

  • Studio status layout: long warnings and errors use the available header width instead of being squeezed into a narrow, tall box. On smaller screens, the server status and message can occupy separate rows. Routine messages remain compact. Authenticated mobile sessions keep the layout, theme and language menus aligned beneath the logout control.
  • Readable status details: Classic keeps the expanded status history inside its panel on narrow screens. Focus anchors the status history and server details to the full header, giving messages useful reading space instead of the width of a small status label.
  • Keyboard interaction: Escape closes an open status history and returns focus to its toggle without also clearing the selected inventory slot. Closing the details preserves active warnings and write locks.

This patch changes presentation and status-panel interaction. World editing, mount creation, placement checks and write safeguards retain their existing behavior. It adds no dependencies and does not change saved layout preferences.

Validation

Release preparation checks the full Python suite, backend branch coverage, browser flows, JavaScript regressions, seven layout and mount smoke scripts, dependency audits, runtime-package contents and integrity, and Docker startup and graceful shutdown with a read-only root filesystem. Visual checks cover desktop and emulated narrow screens, including the light theme.

These checks use synthetic fixtures and do not establish compatibility with every Minecraft version, gameplay action or add-on. Version-specific engine evidence and its limitations are documented in the engine checks and save contract. Mount creation remains experimental; verify edited world copies in Minecraft.

Upgrading

Python 3.12–3.14 remain supported. Run setup.bat once before start.bat to verify the hash-pinned runtime dependencies. Preserve worlds, backups and runtime data separately when replacing an installation.

An installation without a saved layout preference opens in Classic. Existing layout, theme and language preferences remain selected.

For installations with additional packs upgrading from before v0.6.3: update Vanilla icons once to prepare the base texture mappings. Rescanning alone cannot add these mappings to an older Vanilla cache. When skipping several versions, consult the notes of the skipped releases.

Before every edit: stop Minecraft or the Bedrock server and create a complete, independent copy of the world. Keep that copy until the edited world has been verified in Minecraft. App-created backups are an additional safeguard, not a replacement.

Download the asset ending in _runtime.zip together with its .sha256 file. The automatically generated Source code archives are repository snapshots, not ready-to-run packages.

Docker images are published to ghcr.io/dadeeen/mcbe-inventory-editor. Prefer the exact version tag 0.7.1 for deployments; latest and minor tags are intentionally mutable.

MCBE Inventory Editor v0.7.0

Choose a tag to compare

@github-actions github-actions released this 12 Oct 22:33

Runtime package for the Minecraft Bedrock Inventory Editor.

What changed in v0.7.0

  • Three layouts: Classic keeps the familiar interface and remains the default. Studio adds a grouped sidebar and persistent inspector; Focus offers a compact editing workspace. Layout, color theme and language are separate preferences saved in the browser. Switching layouts preserves pending edits.
  • Clearer, responsive controls: world selection, player context and save review avoid duplicate cards and unnecessary scrolling. Layout, theme and language menus use consistent sizing. Item icons scale with the available slot space; equipment numbers have their own space above the icons, including compact Focus slots. Equipment captions and the Enderchest heading have clear spacing from their frames. Dialogs fit narrow and short windows, with readable text and reachable actions. Status feedback is quieter and routine messages keep the workspace position stable, while write locks, errors and important warnings remain visible. Light mode improves the contrast of slot numbers, buttons, fields and diagnostic messages.
  • Mount configuration and preview: a rotatable model previews each supported mount type and horse colors and markings. Custom pixel materials reflect Vanilla coat families, mane colors, distinct forehead markings, larger white fields and fine dark spotting, with species-specific muzzle, hoof and skeleton details; original Mojang assets are not bundled. Intersecting parts occlude correctly while rotating, including the neck's connection to the body. Models use more of the preview area while remaining visible through a full turn; a centered-view icon identifies the reset action. Placement details show the collision footprint and expandable block data. Invalid custom attributes show localized field errors and block staging instead of silently clamping values or displaying impossible speed and jump estimates. Staged mounts remain visible and use the existing review/save workflow. Technical and duplicate hints are reduced without removing placement warnings or write safeguards.
  • More precise placement checks: checks cover the mount's full collision footprint and body height at the position that will actually be stored. Missing chunks, unfinished generation, unsupported data and probe errors have distinct explanations. Known obstructions take precedence over unchecked areas. A nearby chunk is not assumed safe merely because the player can see it in Minecraft.
  • More reliable navigation: rescanning worlds preserves keyboard focus and list position; failed searches clear obsolete results. Stale player and mount responses cannot replace the current editing context. World-folder actions report the handoff to the file manager.
  • Local startup: the local server handles a browser's parallel asset requests with capacity left for API calls and heartbeats, avoiding queue-warning bursts during a normal first page load. Overload warnings remain enabled.
  • Dependency security: the runtime requires Werkzeug 3.1.9 or later; the runtime, Docker and development lockfiles pin the reviewed update. The new layouts and model preview introduce no additional runtime libraries.
  • Docker packaging: recursive build-context exclusions keep local Python caches, logs and private artifacts out of copied source directories. The container smoke test also rejects non-runtime artifacts and verifies the release manifest.

Validation

Release preparation checks the full Python suite, backend branch coverage, browser flows, JavaScript regressions, seven layout and mount smoke scripts, dependency audits, runtime-package contents and integrity, and Docker startup and graceful shutdown with a read-only root filesystem. Visual checks cover desktop and emulated narrow screens, including the light theme.

These checks use synthetic fixtures and do not establish compatibility with every Minecraft version, gameplay action or add-on. Version-specific engine evidence and its limitations are documented in the engine checks and save contract. Mount creation remains experimental; verify edited world copies in Minecraft.

Upgrading

Python 3.12–3.14 remain supported. Run setup.bat once before start.bat to install the updated, hash-pinned runtime dependencies. Preserve worlds, backups and runtime data separately when replacing an installation.

An installation without a saved layout preference opens in Classic. Existing layout, theme and language preferences remain selected.

For installations with additional packs upgrading from before v0.6.3:
update Vanilla icons once to prepare the base texture mappings. Rescanning alone cannot add these mappings to an older Vanilla cache. When skipping several versions, consult the notes of the skipped releases.

Before every edit: stop Minecraft or the Bedrock server and create a complete, independent copy of the world. Keep that copy until the edited world has been verified in Minecraft. App-created backups are an additional safeguard, not a replacement.

Download the asset ending in _runtime.zip together with its .sha256 file.
The automatically generated Source code archives are repository snapshots, not ready-to-run packages.

Docker images are published to ghcr.io/dadeeen/mcbe-inventory-editor. Prefer the exact version tag 0.7.0 for deployments; latest and minor tags are intentionally mutable.

MCBE Inventory Editor v0.6.3

Choose a tag to compare

@github-actions github-actions released this 05 Oct 18:18
04adc2c

Runtime package for the Minecraft Bedrock Inventory Editor.

What changed in v0.6.3

  • World pack icons: icons follow the world's active resource and behavior packs, selected by UUID, version and priority. Static item textures support custom names and references between packs. Missing or ambiguous packs and unsupported rendering rules produce diagnostics; unresolved icons use standard icons or placeholders. Diagnostics follow the selected language. An unreadable optional pack directory does not discard verified local packs.
  • Icon caching and world switching: worlds with the same icon sources share an index, including Vanilla-only worlds. Player loads reuse valid indexes, while pack or item-catalog changes trigger validation and rebuilding when needed. Loading more worlds preserves existing index files. Late responses from an earlier world cannot replace the selected world's icons. Read-only mode uses prepared indexes.
  • Item-catalog updates: an update prepares and validates a complete catalog before replacing the active one. Running operations keep a consistent catalog, and a failed reload leaves the last valid catalog available with an error in the status view. Updates preserve cached player lists for unchanged worlds. Replaced database tables trigger fresh discovery even when their size and timestamps match the originals.
  • Editing: undo keeps separate effect edits in the correct order, including when returning to a previously edited field. Repair all respects protected slots. Applying a converted position allows the next dimension conversion without reopening the form.
  • Backups and restore: corrupt ZIP data, encrypted members and unsupported compression formats do not interrupt listing or count as valid recovery copies. Invalid backup dates fall back to the file time. If a restore leaves the world's state uncertain, the editor clears the loaded player and shows recovery guidance instead of allowing edits against the previous state.
  • Loading and saving: saves reuse parsed source and validated output NBT while retaining output validation and write safeguards. Icon handling avoids duplicate decoding, archive metadata reads and source preparation. Damaged compressed icon images return a handled error.
  • Developer checks: the Bedrock engine harness compares editor enchantment rules and conflict hints with measured behavior, checks combined equipment metadata and exact durability limits, and reports enchantment registry changes. Service and client profiles move and recreate equipment with multiple enchantments and custom metadata. CI and the local release workflow enforce consistent Python formatting.

Validation

Validation includes the full Python suite, browser tests and runtime-package checks. The documented BDS 1.26.52.3 reference covers all 1,623 measured item identifiers, 13,153 item cases, enchantment applicability and conflict comparisons, and engine save/reload cycles. A separate real-client profile covers 45 cases across Inventory and Ender Chest. These checks exercise selected item and save behavior; they do not simulate every gameplay action or add-on. The exact measured source revision, hashes and limitations are recorded in the engine checks and save contract.

Upgrading

This release adds no dependencies. Python 3.12–3.14 remain supported, and existing installations start without running setup.bat again.

For installations with additional packs: update Vanilla icons once to prepare the base texture mappings. Rescanning alone cannot add these mappings to an older Vanilla cache.

If upgrading from v0.5.21 or earlier: run setup.bat once before start.bat to install Waitress. When skipping several versions, consult the notes of the skipped releases.

Before every edit: stop Minecraft or the Bedrock server and create a complete, independent copy of the world. Keep that copy until the edited world has been verified in Minecraft. App-created backups are an additional safeguard, not a replacement.

Download the asset ending in _runtime.zip together with its .sha256 file. The automatically generated Source code archives are repository snapshots, not ready-to-run packages.

Docker images are published to ghcr.io/dadeeen/mcbe-inventory-editor. Prefer the exact version tag 0.6.3 for deployments; latest and minor tags are intentionally mutable.

MCBE Inventory Editor v0.6.2

Choose a tag to compare

@github-actions github-actions released this 01 Oct 22:58

Runtime package for the Minecraft Bedrock Inventory Editor.

What changed in v0.6.2

  • Loading while a server runs: v0.6.1 could fail to load a world that a running Bedrock server was writing, with a message that a table file disappeared while reading. The editor holds a world's table files from the moment it opens them, shares one table budget across all readers and the writer, and reports a world that changed during reading instead of returning a mixed state.
  • Player changed outside the editor: when Minecraft or a server changes the loaded player, the status area shows an error with a "Reload player" action until the player is reloaded. A stale action after a player switch reloads nothing.
  • Status overview: the status overview under Tools follows the server status and write lock shown in the header. Before, it could show "All OK" while the server was online and writing was locked.
  • Error messages: a failed action names its reason once, without a second generic prefix such as "Error while saving: Error saving the player: …". An unexpected error shows "internal error, details in the server log (request ID …)" instead of the exception text, which could contain local paths; an operating system error keeps its description, such as a full disk or a file in use. The log panel of the diagnostics shows why the logs are refused instead of an empty list.
  • Item catalog: eight tooltip lines that the catalog listed as items, such as "Can break:" and "Unbreakable", are gone, and Banner Pattern and Smithing Template carry their names instead of "Field Masoned" and "Applies to:". Existing installations are corrected when the catalog loads; own names stay.
  • Keyboard focus and status colors: after loading, saving and closing a dialog, the keyboard focus returns to where it was or lands at the start of the new view. Status entries keep readable colors in the dark and light themes.
  • Faster loading: a player is parsed once per load, and the item browser computes its sort keys once per item.

Validation includes the complete Python suite and the browser tests, four large readers in a Linux container limited to 1,024 open files, and a Minecraft 1.26.52 client that deleted 48 table files while the editor held them open. The save steps and the database format are unchanged; the in-game check covered reading only. See the save contract for validation boundaries.

This release adds no dependencies. Python 3.12–3.14 remain supported, and existing installations start without running setup.bat again. If upgrading from v0.5.21 or earlier: run setup.bat once before start.bat to install the Waitress server the editor uses since v0.5.22. When skipping several versions, the notes of the skipped releases describe their changes, including the switch to the editor's own database code in v0.6.0.

Before every edit: stop Minecraft or the Bedrock server and create a complete, independent copy of the world. Keep that copy until the edited world has been verified in Minecraft. App-created backups are an additional safeguard, not a replacement.

Download the asset ending in _runtime.zip together with its .sha256 file. The automatically generated Source code archives are repository snapshots, not ready-to-run packages.

Docker images are published to ghcr.io/dadeeen/mcbe-inventory-editor. Prefer the exact version tag for deployments; latest and minor tags are intentionally mutable.

MCBE Inventory Editor v0.6.1

Choose a tag to compare

@github-actions github-actions released this 29 Sep 18:30

Runtime package for the Minecraft Bedrock Inventory Editor.

What changed in v0.6.1

  • World in use: the reason once: when Minecraft, a Bedrock server or another editor instance has the world open, a refused save, import, player migration or mount creation shows the reason once. Before, the message repeated its error prefix ("Error while saving: Error saving the player: …"), and the editor logged the refusal as an internal server error.
  • Mount coordinates in the save overview: the save overview shows the position of a mount to be created with two decimals, as the mount panel does, instead of values such as 101.30000305175781 / 64 / -5.699999809265137.

Validation includes the complete Python suite, the browser tests, a test that refuses a save because the world is in use, and a test for the coordinates in the save overview. The write path and the database format are unchanged, and no new in-game validation was performed. See the save contract for validation boundaries.

This release adds no dependencies. Python 3.12–3.14 remain supported, and existing installations start without running setup.bat again. If upgrading from v0.5.21 or earlier: run setup.bat once before start.bat to install the Waitress server the editor uses since v0.5.22. When skipping several versions, the notes of the skipped releases describe their changes, including the switch to the editor's own database code in v0.6.0.

Before every edit: stop Minecraft or the Bedrock server and create a complete, independent copy of the world. Keep that copy until the edited world has been verified in Minecraft. App-created backups are an additional safeguard, not a replacement.

Download the asset ending in _runtime.zip together with its .sha256 file. The automatically generated Source code archives are repository snapshots, not ready-to-run packages.

Docker images are published to ghcr.io/dadeeen/mcbe-inventory-editor. Prefer the exact version tag for deployments; latest and minor tags are intentionally mutable.

This is an unofficial community project. It is not affiliated with, endorsed by, or associated with Mojang Studios or Microsoft.

MCBE Inventory Editor v0.6.0

Choose a tag to compare

@github-actions github-actions released this 29 Sep 16:34

Runtime package for the Minecraft Bedrock Inventory Editor.

What changed in v0.6.0

  • No native database engine: the editor reads and writes Bedrock worlds with its own Python code. Setup installs only hash-checked prebuilt packages for Python 3.12–3.14; Microsoft C++ Build Tools, the Windows SDK and the Visual C++ Redistributable are not needed, and the runtime ZIP contains no LevelDB wheels. A save adds a new write-ahead log to the world's database and leaves the existing database files unchanged; Minecraft integrates that log the next time it opens the world. Amulet-LevelDB is used only as an independent reference in the tests, so its license terms do not apply to the runtime.
  • Clear refusals: the editor names the reason when it refuses a save because Minecraft, a Bedrock server or another editor instance has the world open, or because the world was not closed cleanly. Loading the world once in Minecraft or on the server and closing it normally resolves the second case. On Linux, a running Bedrock server holds no database lock; there the server-status check is the protection.
  • Unknown save outcome: if a save fails after data may already have reached the disk, the editor reports that the outcome is unknown, keeps the backup and blocks further saves until the world is reloaded. Errors that occur before anything is written remain ordinary errors that can be retried.
  • Faster reload after saving: after an ordinary save of one existing player, the editor keeps the world's player list instead of scanning the whole world again. On large worlds, reloading after a save takes well under a second instead of many seconds.
  • Large worlds on Linux and in Docker: the editor keeps at most 64 database files of a world open at once. Before, reading a world opened every table file at the same time, so worlds with more files than the system's open-file limit (often 1024 on Linux, roughly 2 GB of world data) could not be loaded there.
  • Walking speed that takes effect: the previous walking speed field edited walkSpeed in the player's abilities. In Bedrock that value only sets the field of view: a higher value zoomed the view, but the player did not walk faster. The new Walking speed field edits the minecraft:movement attribute, which Bedrock uses for the actual speed; sprinting still adds to it. It also sets walkSpeed to the same value, so the field of view stays normal. walkSpeed remains available as Walking field of view, with a note on what it does. The walking speed is read-only while the attribute is missing, carries modifiers (for example from sprinting or an effect at the moment the world was saved) or has an unexpected structure; the reason is shown below the fields.
  • Vertical flying speed: a new field edits verticalFlySpeed (0–20, vanilla 1), the speed of climbing and descending while flying. The flying speed field (flySpeed) is labelled as horizontal flight. Player migration copies verticalFlySpeed together with the other speeds.
  • Checkboxes without effect are gone: Minecraft recalculates flying, floating, invulnerability, instant block breaking and build permission from the game mode and the player permission level when a player loads, so edits to these checkboxes were lost in the game. The "Place blocks" checkbox also wrote the Java tag name mayBuild, which Bedrock ignores and removes on its next save. The editor no longer shows or writes these values; change them through the game mode and player permissions in Minecraft. Values already stored in a world stay untouched.
  • Shorter slot details: the NBT details of a slot no longer contain the "Show detail log" section, which repeated the table and the expert NBT shown above it. Copy details still copies the complete text, including player and world path.
  • Safer backup restore: restore writes every extracted file and folder to disk before it replaces the current world. If that fails, the restore stops while the current world is still in place, and the safety backup is kept.
  • Clearer error for oversized requests: a request whose JSON is nested deeper than the decoder allows gets the same "invalid request" error as other malformed JSON instead of a server error.

Validation includes the complete Python suite, the browser tests, comparisons of the new write path with the native LevelDB engine (identical log bytes, randomized alternating sessions, interrupted writes and locking) on synthetic data and on copies of real worlds, Bedrock Dedicated Server 1.26.51.1 engine checks, restore tests in which writing files or folders to disk fails, byte-for-byte comparisons of the new speed writes against an independent NBT implementation, and in-game checks with the Minecraft client 1.26.52 on Windows: inventory, Ender Chest, effects, a new horse and backup restore through the new write path; walking speed with and without sprinting, horizontal and vertical flying speed, and flying, instant block breaking and build permission following the game mode. See the save contract for validation boundaries.

This release removes Amulet-LevelDB from the runtime and adds no dependencies. Python 3.12–3.14 remain supported. Existing installations start without running setup.bat again; an Amulet-LevelDB package left in an existing .venv is not used. If upgrading from v0.5.21 or earlier: run setup.bat once before start.bat to install the Waitress server the editor uses since v0.5.22. When skipping several versions, the notes of the skipped releases describe their changes.

Before every edit: stop Minecraft or the Bedrock server and create a complete, independent copy of the world. Keep that copy until the edited world has been verified in Minecraft. App-created backups are an additional safeguard, not a replacement.

Download the asset ending in _runtime.zip together with its .sha256 file. The automatically generated Source code archives are repository snapshots, not ready-to-run packages.

Docker images are published to ghcr.io/dadeeen/mcbe-inventory-editor. Prefer the exact version tag for deployments; latest and minor tags are intentionally mutable.

This is an unofficial community project. It is not affiliated with, endorsed by, or associated with Mojang Studios or Microsoft.

MCBE Inventory Editor v0.5.29

Choose a tag to compare

@github-actions github-actions released this 28 Sep 14:47

Runtime package for the Minecraft Bedrock Inventory Editor.

What changed in v0.5.29

  • Items show their own names again: some blocks were listed under the name of one of their variants. Sandstone, for example, appeared as "Chiseled Sandstone" right next to the real chiseled sandstone, and the respawn anchor showed the game message "Respawn point set" as its name. Eight selectable items were affected: sandstone, red sandstone, block of quartz, cobblestone wall, prismarine, brown mushroom block, respawn anchor and disc fragment. The editor always created and saved the item ID shown in the item browser; only the displayed name was wrong. 22 older item IDs that can still occur in worlds from earlier Minecraft versions, such as minecraft:wool or minecraft:fireworks, now show the item's general name, or its default variant where Minecraft has no general name, instead of an arbitrary color or wood variant or a game message.
  • Names match the game: 31 item names now follow Mojang's current Bedrock translation, for example "Diamantharnisch" instead of "Diamantbrustplatte", "Kettenhemd-Stiefel" instead of "Kettenstiefel", "Block of Coal" instead of "Coal Block", "Eye of Ender" instead of "Ender Eye", and "Comparator" instead of "Redstone Comparator". Searching for the name shown in the game now finds these items.
  • Existing installations are corrected when the editor starts: the item database in the data folder is not rewritten. When the editor loads it, it replaces each affected name that still matches the previous name exactly; entries changed by hand stay as they are. The next Item DB update may list some of these names as changes; that is expected.

Validation includes the complete Python suite, the browser tests, new tests that fail on the previous item database, and a comparison of every item name with the language files of bedrock-samples v1.26.50.4, the Minecraft release the bundled item database is based on. World data, saves and the write path are unchanged. Because only displayed names changed, no new in-game validation was performed. See the save contract for validation boundaries.

If upgrading directly from v0.5.25 or earlier: since v0.5.26 the server check also detects running NetherNet servers (transport=nethernet). For that, the editor needs TCP access to the server port (MCBE_SERVER_PORT, usually 19132). In Docker, publish it as 19132/tcp or run the editor in the server's Docker network; otherwise the status stays unknown and saving asks for confirmation. See Docker and trusted LANs.

If upgrading directly from v0.5.24 or earlier: the world folder, its db folder and everything inside the world must be ordinary directories and files. Since v0.5.25, backups, and therefore saves, stop at symlinks, Windows junctions and other reparse points. Before editing, replace such links with regular copies, for example resource or behavior packs linked into a world. First-run setup and session signing keys are kept per process: complete setup with a single process, then restart all processes. The bundled Docker configuration uses one process and is unaffected.

Backups continue to contain the complete world. Configured size limits and retention policies are unchanged.

This release adds no dependencies. Python 3.12–3.14 remain supported. If upgrading from v0.5.21 or earlier: run setup.bat once before start.bat to install the hash-pinned Waitress dependency introduced in v0.5.22. Flask and Werkzeug remain required.

If upgrading directly from v0.5.18 or earlier: open Tools & settings → Icons and select Load Vanilla icons (Werkzeuge & Einstellungen → Icons → Vanilla-Icons laden) to rebuild existing PNGs with the resolver corrected in v0.5.19. Rescanning sources alone does not regenerate cached images.

If upgrading directly from v0.5.14 or earlier: the Item DB may show Verification pending even when its data has not changed. This is expected because the verification rules changed in v0.5.15; it does not mean that the database is damaged. If the setup dialog opens, select Load now for Load item database. Otherwise, open Tools & settings → Item DB, run a dry run, and then select Apply update. An apply with no data changes only refreshes the local verification record.

Before every edit: stop Minecraft or the Bedrock server and create a complete, independent copy of the world. Keep that copy until the edited world has been verified in Minecraft. App-created backups are an additional safeguard, not a replacement.

Download the asset ending in _runtime.zip together with its .sha256 file. The automatically generated Source code archives are repository snapshots, not ready-to-run packages.

Docker images are published to ghcr.io/dadeeen/mcbe-inventory-editor. Prefer the exact version tag for deployments; latest and minor tags are intentionally mutable.

This is an unofficial community project. It is not affiliated with, endorsed by, or associated with Mojang Studios or Microsoft.