Data & Schema
Define your schema and manage records in the Backoffice, then query, subscribe to, and mutate that data from the SDK.
Schema Object ReferenceDefinitions of core schema concepts in PlayServ — Entity, Entity Part, Enum, fields, field kinds, and Singleton.Building a Game SchemaHow to create Entities, Entity Parts, Enums, and fields in PlayServ Backoffice to build a complete game schema.Working with Game DataHow to create, edit, and manage data records in PlayServ Backoffice — including bulk import from JSON and CSV.Publishing ChangesHow to review, apply, and track schema migrations in PlayServ Backoffice.Query Language & Data RetrievalHow to retrieve single objects and collections using the PlayServ LINQ-like query language — Where, With, nested relations, and server-side translation.Data Subscriptions & Live UpdatesHow to subscribe to live data updates in PlayServ — initial payload, reactive deltas, JSONPatch optimisation, and subscription restoration.Data Mutation & Model ExtendingHow to persist data changes in PlayServ using Update and Delete, and how to extend models with domain behaviour as RPC methods.Backoffice MCP IntegrationHow to use the MCP integration in PlayServ Backoffice to manage projects, generate schemas, and work with existing data through an AI assistant.Access ControlHow PlayServ decides who can read and write each table — table-level authority for client, server, and backend, composed with per-player row ownership.