GameCult/CultLib
Watch
9
0
Fork
You've already forked CultLib
 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

Document generated geometry registry ownership

Browse source
This commit is contained in:
Meta Vens 2026-07-22 04:13:43 +01:00
commit 8a7eee717e
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
src/GameCult.Geometry/README.md
View file

@ -44,11 +44,7 @@ using GameCult.Geometry;
using GameCult.Mesh;
using GameCult.Networking;
var geometryDocuments = new CultNetDocumentRegistry(CultDocumentRegistry.Shared)
.Register(CultNetDocumentBinding.ForDocument<CultGeometryDomainDocument>())
.Register(CultNetDocumentBinding.ForDocument<CultGeometryBuildRequest>())
.Register(CultNetDocumentBinding.ForDocument<CultGeometrySelectedCutManifest>())
.Register(CultNetDocumentBinding.ForDocument<CultGeometryChunkArtifact>());
var geometryDocuments = new CultNetDocumentRegistry(CultDocumentRegistry.Shared);
using var node = await CultMesh.CreateNodeAsync("ragnarok-geometry.ccmp", new CultMeshNodeOptions
{
@ -64,6 +60,10 @@ using var chunks = node.Database
.Subscribe(change => ApplyChunk(change.Document));
```
The generated CultDocument metadata owns geometry registration. Consumers pass
the shared registry into CultNet; they do not maintain a second manual binding
list that can drift when the schema cohort changes.
The record key is part of the contract. Rust and C# must compute the same key
for the same geometry record, so stable fingerprints use the Rust canonical
field order and exact IEEE-754 component bits. If this drifts, the same chunk becomes two