Skip to content

Add safe deterministic world processing - #77

Merged
SupaHam merged 2 commits into
mainfrom
codex/world-processing
Aug 17, 2026
Merged

Add safe deterministic world processing#77
SupaHam merged 2 commits into
mainfrom
codex/world-processing

Conversation

@SupaHam

@SupaHam SupaHam commented Aug 17, 2026

Copy link
Copy Markdown
Member

Summary

  • add deterministic, content-addressed Bedrock world processors
  • verify staged mutations while keeping authored worlds immutable
  • integrate processed worlds into development and packaging flows
  • update archive, compiler, and LevelDB dependencies
  • preserve caller-owned chunk coordinates at the mcbe-leveldb 1.21 compatibility boundary
  • add the minor changeset for @blurengine/cli 0.15.0

Why

Projects need reproducible generated world data without mutating committed raw worlds or trusting ambiguous processor output.

Validation

  • npm.cmd run check
  • 295 tests passed
  • build and package validation passed
  • clean worktree and git diff --check

Dependency health

The current registry advisory feed reports 6 advisories (5 high, 1 critical). Four are in the optional native chain @8crafter/leveldb-zlib -> cmake-js -> tar; two are transitive development-tool advisories (brace-expansion and js-yaml). npm audit fix --dry-run produced no compatible lockfile change. The only suggested native-chain action is an invalid major downgrade to mcbe-leveldb 1.1.0, so no unsafe override or downgrade is included.

@SupaHam
SupaHam marked this pull request as ready for review August 17, 2026 23:02
@SupaHam
SupaHam merged commit 88b9690 into main Aug 17, 2026
4 checks passed
@github-actions github-actions Bot mentioned this pull request Aug 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant