McpeTool vs Minecraft Bedrock Debugger

McpeTool is a free, offline utility for reading and writing Minecraft Bedrock Edition world data. Its command-line interface and local HTTP API provide get, put, and delete operations. Database commands list, retrieve, write, and delete key/value pairs in a world’s LevelDB store. Level-data commands retrieve or replace level.dat contents using JSON, YAML, hex dump, base64, or binary formats. NBT data can be converted to JSON and YAML, and relevant commands accept or produce base64 and binary data. The API starts a local HTTP server and handles GET, PUT, and DELETE requests for database keys. The tool runs on Linux, macOS, and Windows and can be self-hosted or used through its API. It is MIT-licensed and intended as a basic access layer for people building more capable world editors. McpeTool cannot be used while Minecraft is running the world because LevelDB allows only one process at a time. The maker calls it a work in progress, says input validity is not currently checked, and advises backing up worlds before changes.

Minecraft Bedrock Debugger is a free, open-source Visual Studio Code extension for developers building Minecraft Bedrock behavior packs and add-ons with JavaScript or TypeScript. It connects through script debugger commands, using port 19144 by default, and supports breakpoints, stepping, a Locals pane and watches. Developers can run Minecraft slash commands and keep shortcuts for favorite commands. Performance tools provide diagnostics and a script profiler that saves captures to a configured local path. Minecraft 1.21.10 or later can expose server statistics including entities, chunks, memory, tick time and network usage. Client diagnostics include FPS, memory, entity systems and CPU profiling, but require Minecraft’s “Enabled client diagnostics” creator setting. Scripts can add live diagnostics through the @minecraft/debug-utilities module. TypeScript projects can use source maps through sourceMapRoot and generatedSourceRoot. Dedicated Server debugging requires enabling inbound or outbound script-debugging settings in server.properties, which are disabled by default. Changing variable state and immediate mode are unsupported.