Document terrain interaction contract v2#116
Merged
Merged
Conversation
This was referenced May 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Defines Terrain Interaction Contract v2 as the long-term rc10 contract for voxel terrain break/place interactions.
This is SDK-only design work after freven-engine#386 smoke showed that local prediction fixes alone are not enough: client presented intent and server authoritative validation need one shared contract.
Why
Current Vanilla v1 payloads carry only target position/face/block id, while the client builds intent from prediction-aware presented cursor state and the server reconstructs validation from authoritative world/player position/block-center visibility. That mismatch can produce valid-looking client predictions that later rollback.
What changed
docs/TERRAIN_INTERACTION_CONTRACT_v2.md.freven_block_apiwithout choosing/wiring a serialized payload schema.Boundaries
Validation
cargo +stable fmt --all -- --checkcargo +stable test --locked --workspacecargo +stable clippy --locked --workspace --all-targets -- -D warningscargo +stable clippy --locked --workspace --all-targets --all-features -- -D warningsgit --no-pager diff --checkRelated: