Realtime

Spatial Subspaces

Online

Managed Spatial Subspaces route opaque realtime state by 3D position and interest inside server-controlled AABB bounds.

Each managed server keeps logical compatibility spaces 1 and 2and can add up to 64 user-configured SpatialGrid3D spaces. Logical spaces do not count toward that limit. Host allocates spatial numeric IDs from 3.

Add-only managed definitions

Add a Spatial Subspace from the server Details page with a stable lowercase slug and a display name, each 1–64 characters. Definitions are immutable for the server generation. An exact retry is idempotent; reusing a slug with another name or definition is rejected. Unknown, wildcard, and ad-hoc spaces are not granted or returned to clients.

Dimensions: Three-dimensional Cartesian routing only.
Scale: metersPerUnit: 1
Grid and interest: cellSize: 10, interestRadius: 25, and exactDistance: true
Default bounds: Min (-1000, -100, -1000); max (1000, 500, 1000). Every minimum axis must be strictly less than its maximum.

Connection and routing contract

Connection and monitoring data expose the two logical spaces followed by complete managed spatial definitions, including numeric ID, bounds, scale, cell size, interest radius, and exact-distance policy. Rust QUIC and TypeScript WebTransport clients must use those returned definitions rather than inventing IDs or overriding server policy.

Managed spatial routing is Online. Channel 1 is ReliableOrdered; channel 4 is UnreliableSequenced. Both remain Ephemeral and carry opaque bytes. Persistence beyond Ephemeral and Inference remain Preview.