$ dps check --strict examples
loading 7 manifests · profile 26.2
PASS generator-output.dps.json
PASS player-events.dps.json
PASS full-stack.dps.json
Run, test, and debug datapacks before shipping
A clean-room local runtime for Minecraft Java datapack authors. Run with the CLI, lock regressions into manifests, and debug interactively in VS Code.
ONE RUNTIME · THREE WORKFLOWS
Use the same deterministic runtime from the terminal, a manifest suite, or your JVM tests. Reports share the same outputs, traces, diagnostics, and snapshots.
Read packs and version-specific resource formats.
Execute commands, functions, ticks, and player events.
Compare observable output and world state.
$ dps check --strict examples
loading 7 manifests · profile 26.2
PASS generator-output.dps.json
PASS player-events.dps.json
PASS full-stack.dps.json
DESIGNED FOR TRUST
Datapack Sandbox is intentionally explicit about what it models. Use it for deterministic development feedback, then reserve vanilla integration runs for behavior that genuinely requires the game engine.
Stable seeds, snapshots, and structured reports make failures reproducible.
Every command can expose source locations, output events, traces, and state diffs.
Built-in profiles cover modern datapack formats from 1.20.4 through 26.2.