Local development
Run your game with the development server provided by your framework. Plot
previews will load a loopback URL such as http://localhost:5173, so live reload
and hot module replacement can continue to work while the game is embedded.
Keep two modes easy to exercise:
- Standalone UI mode lets you build screens and game rules by opening the
local URL directly. Do not call
connect()in this mode unless you intentionally want to display the not-in-Plot error state. - Plot preview mode loads that same local URL through a Plot-provided preview so you can test connection and platform behavior.
The public creator preview is still being built. Until it is available to you, the current SDK can be integrated and type-checked, but a successful connection requires a Plot-provided preview environment.
After the first SDK release
The package has not been published yet. Once it is available, games should keep a normal versioned dependency:
Your game framework can then build and serve the app normally. Pin a complete version before publishing so an SDK update cannot change an already-tested game.
During standalone UI work, provide sample player and game data inside your own development setup rather than calling undocumented Plot interfaces. Keep those fixtures out of production behavior, and test the real SDK path again in Plot preview mode before publishing.