Build Horizon Rust parity foundations and differential validation

Add version-bound core, world data, geometry, generation and feature implementations with native client/server comparison tools and scoped evidence reports. Apply Horizon project branding.

Workspace tests, Clippy and 147 Python tests passed. Full 51-family survival and expanded provider comparisons are still running; complete gameplay parity and a playable Rust client remain unfinished. Private game artifacts and the isolated simple-block placement work are excluded.
This commit is contained in:
Ludovic Marie
2026-10-06 11:24:51 +02:00
parent b3dda5152c
commit cb19660fbe
558 changed files with 73754 additions and 58 deletions
+7
View File
@@ -8,6 +8,13 @@ Inspect both pinned game JARs locally, retain bytecode as the reference, and mea
Whole-game translation is a long-term research objective. Decompiled Java is an inspection artifact, not the original source tree: build configuration, comments, tooling history, and some source-level constructs cannot be recovered faithfully. A mechanically translated Rust game would also have to preserve behavior, data formats, networking and rendering. An isolated hot-path replacement is a useful first experiment.
The Rust rewrite now has an original `horizon-core` foundation and a bytecode
differential runner for selected position, random-stream and packed-storage
operations. [Rust parity status](rust-parity.md) distinguishes that tested slice
from the unimplemented gameplay and renderer. This establishes compatibility
testing infrastructure; it does not select an FPS bottleneck or supply a playable
Rust client.
## Local code map
These entry points were verified present in the decompiled 26.3 client. Paths below are relative to `.local/minecraft/26.3/sources/client/net/minecraft/`; shared/server logic can also be inspected in the dedicated-server tree.