ProjectV-SDK documentation

ProjectV-SDK is the V3 Unity SDK for ProjectV. The game talks to its Nakama backend only through this SDK: the SDK owns sessions, realtime, caching, recovery and every server-authoritative value, and hands the game screen-ready presenters.

Nakama (ProjectZ/Nakama v3)
  -> Shared SDK (com.silvertiger.crosssdk.*, built from ProjectZ-CrossSDK)
  -> ProjectV-SDK (com.silvertiger.projectv.*, this repository)
  -> ProjectV Client (game scenes and UI)

The docs are split by audience. Pick your track.

🎮 Client Guide

For the ProjectV Client (game) team. You present data: inject an IProjectV*Presenter, subscribe to its snapshot, call its typed commands and render the results. You never compose the runtime, call RPCs or calculate wallet, stamina, rewards or progression.

→ Start here: Overview · Install and set up · Presenter reference · Migrating from V1

🛠 SDK Team

For ProjectV-SDK maintainers. You add presenters and typed capabilities, build and release the packages through BuildOps, and keep these docs in sync with the shipped API.

→ Start here: SDK Team overview · Architecture · Add a presenter · Release pipeline

---

The three layers

1. Shared SDK (9 com.silvertiger.crosssdk.* packages, game-agnostic): sessions, realtime, state store, Unity host.
2. ProjectV-SDK (5 com.silvertiger.projectv.* packages): ProjectV contracts, Nakama binding, presenters, VContainer and Google integrations.
3. ProjectV Client: scenes, UI, navigation and gameplay. It uses layer 2 only through presenters.

The Client Guide covers layer 3. The SDK Team guide covers layer 2 and how layers 1 and 2 are released.

V1 (the ProjectZ-CrossSDK Manager APIs such as IPlayerManager) is retired. These pages replace the V1 site; see Migrating from V1 for the Manager-to-presenter mapping.