02b45cc4

Guide
- Move sets
- Pose constraints
- The variation harness
- Getting content into a running game
- Components
- Entity queries
- Booleans and handoff
- The editing pipeline
- Element selection
- Face materials
- Foliage mode
- Icons
- The editor shell
- Editable meshes in a scene
- Editor modes
- Building to a number
- Scene menus
- The shape tool
- Snapping
- Sub-object picking
- Sculpt and paint mode
- Writing an editor plugin
- Block-out shapes
- Booting an application
- Character movement
- Editable meshes
- Growing a forest
- Foliage instances
- Grass
- Mesh booleans
- Mesh operations
- Mesh surfaces
- Networked players
- Players and possession
- Splines
- Terrain brushes
- The terrain heightfield
- Painting a terrain
- Sculpting a heightfield
- Saving and restoring a world
- Admission, health and the control plane
- Durable state and the ledger
- Placing players
- Placing realms
- Shards, keys and specs
- The cluster
- The service plane
- Transfer tickets
- Transferring players
- Upgrading a fleet
- Writing a realm
- Drawing foliage
- Drawing grass
- Impostors
- Culling and streaming instances
- Turning on dynamic global illumination
- Meshes and materials, type by type
- Drawing particles
- Lighting a scene in lux and lumens
- Making a room look different
- The post-processing node kinds
- Making everything cast a shadow
- Drawing a terrain
By kind
- Components39
- Systems48
- Controls165
- Shaders48
- Graph nodes64
- Importers22
- Annotations45
- Diagnostics8
- Log events64
All namespaces275
Releases1

IPersistence

interface

Live/Vixen.Live.Persistence/Repositories.cs:203

csharp

public interface IPersistence

Everything behind one connection, so a caller composes one object rather than three.

Read the guide page for this →

Remarks

⚠ The three are one store, and the ledger's fence is why. An append names the acting realm's lease epoch and the fence it is checked against is the character's row — so a deployment that put the journal in one database and the characters in another would have no way to make the check and the write one transaction. Handing them out together is the interface admitting what the implementations already require.

Fields and properties (3)

IAccountRepository Accounts
Accounts.
IPlayerRepository Players
Characters.
ILedger Ledger
The journal.

Methods (1)

Task<int> MigrateAsync(CancellationToken cancellation)
Brings the schema up to date, and says nothing if it already is.

Used by (3)

GateServiceVixen.Live.Gate
MemoryPersistenceVixen.Live.Persistence
SqlPersistenceVixen.Live.Persistence