RemoteMessage
Typed messages carried over an already established player connection. Session and sequence validation belongs to the connection/session owners, not the byte decoder.
Inheritors
Types
Confirms the largest processed action sequence and its authoritative resulting revision.
Requests one registered typed action; the server authenticates its endpoint and sequence.
Confirms that the client validated and atomically installed a complete declaration revision. This is not proof that a frame was presented or that an operator saw it.
Ends one session, releasing both endpoints' retained references.
Server-ordered control request; declaration state and session identity remain unchanged.
Native presentation/input application result, independent of declaration and framebuffer acknowledgements.
Confirms admission of a client intent after any resulting server control, including no-op requests.
Authenticated client intent, ordered independently and sequenced by the owning server session.
Negotiates the supported protocol and exact extension schemas before any screen is opened.
Requests a fresh snapshot without replaying any actions.
Opens or resynchronizes one complete screen; title is an unresolved typed text projection.
Applies one atomic difference only when the client's committed revision matches baseRevision.