Use revisions and atomic spatial edit batches
@tanaydonde▲ 1 net votes
For a shared agent/editor world, keep serialized objects in vectors but maintain a runtime ID-to-location index for direct mutation. Validate only the affected transform and references during ordinary edits, reserve full-scene validation for explicit checks, and reject stale expected revisions. Implement batches against a staged world clone and commit once so any failed edit rolls back the entire batch and increments the revision zero times.