Getting Started
Info
Networking is available in beta 82+
This guide walks through the shortest useful setup for trying the PlayMaker networking addon.
The first backend currently implemented is Netcode for GameObjects, so that is the backend used in this guide.
Alpha Workflow
Treat this as the current recommended setup path, not a final compatibility or production-readiness statement.
What You Install
For the current alpha workflow, install:
- The PlayMaker Networking addon
- The Networking Samples package
- A backend implementation
The PlayMaker networking layer provides the PlayMaker-facing components and actions.
The backend addon connects those features to a specific networking runtime.
At the moment, the first backend implemented is Netcode for GameObjects.
The Networking Samples package gives you test scenes that are helpful for understanding the current workflow and for verifying whether a problem is in your project setup or in the addon itself.
Import the Networking Samples
Import the Networking Samples from Addons before building your own test scene.
Recommended approach:
- Open one of the networking sample scenes.
- Confirm the sample can start a host and connect a client.
- Identify the
NetworkManager, the networked prefab, and the PlayMaker FSMs involved. - Trace one simple flow such as spawning an object, sending an event, or syncing a variable.
- Copy that pattern into your own test scene only after the sample flow makes sense.
This usually gives you a faster path than building everything from scratch on the first pass.
Basic Scene Setup
- Create or open a test scene.
- Add a NetworkManager to the scene if one is not already present.
- Configure the
NetworkManagerfor the backend you are using. - Add any transport or backend-specific settings required by that backend.
- Create a simple player or test prefab that you want to spawn or synchronize.
If you already have a working backend scene or a PlayMaker networking sample scene, you can often start there and then add or adapt the PlayMaker networking pieces on top.
Add the PlayMaker Pieces
Once the backend is in place:
- Add a
NetworkObjectto each prefab that should exist on the network. - Add a Netcode Object Proxy to the same prefab.
- Add an FSM that will send events, react to events, or sync variables.
- Add
Network Variable SyncorNetwork Global Variable Synccomponents where needed.
First Goal for Testing
A good first test is:
- Start host
- Connect one client
- Spawn one networked object
- Send one network event
- Sync one variable
If any of those steps are hard to explain in your project, that usually points to a setup or workflow gap worth tightening before you build more features on top.
Recommended Early Test Scene
Build a small scene with:
- One
NetworkManager - One networked prefab with a
NetworkObject - One FSM that sends a test event
- One synced FSM variable such as
Health,Speed, orDisplayName
If the sample package already includes a close match, duplicate that scene and trim it down to the smallest version that still demonstrates the workflow you want to test.
Keep the scene as small as possible.
That makes it easier to tell whether a problem comes from networking setup or from gameplay logic.