Pirates 1 — Set up the game
Welcome to the Pirates Tutorial!
In this lesson you’ll:
- set up your machine for development with SpatialOS
- run the Pirates game locally
- use the Inspector to explore the game world
- learn about entities, components and workers - the core concepts of SpatialOS
This first lesson is mostly background work you need to do before you can get going with development. Once your machine is set up and the game is running, we’ll use the game to explain the basic concepts of SpatialOS. So bear with us!
1. Set up your machine
To set up your machine for developing with SpatialOS, follow the setup guide for your OS:
This sets up the
spatial command-line tool, which you use to build, run, and deploy your game.
You’ll use it later in the lesson to build the Pirates game and run a local deployment.
It’s done when: You run
spatial versionin a terminal, and see
'spatial.exe' command-line tool version: <number>(or
'spatial' command-line tool version: <number>on Mac) printed in your console output.
2. Set up the PiratesTutorial project
In this tutorial, you’ll develop on the PiratesTutorial project.
2.1. Download the source code
Download and unzip the game source code.
2.2. Check your setup
- Open a terminal and navigate to the directory you just unzipped (the directory that contains
This checks that you installed all the software you needed correctly.
spatial diagnosefinds errors with your setup, fix them.
It’s done when: You see
'spatial/spatial.exe diagnose' succeededprinted in your console output.
2.3. Build the game
In same terminal window, run
spatial worker build UnityWorker UnityClient --target=development.
This builds the game. It can take up to ten minutes, so you might want to go and get a cup of tea.
If it doesn’t work first time, you can retry by running
spatial worker clean then
spatial worker build again.
It’s done when: You see
'spatial/spatial.exe build UnityWorker UnityClient' succeededprinted in your console output.
2.4. Run the game locally
In the same terminal window as before, run a local deployment of the game by running
spatial local launch. This can take a
minute to get up and running.
It’s done when: You see
SpatialOS ready. Access the inspector at http://localhost:21000/inspectorprinted in your console output.
2.5. Connect a client
Now SpatialOS is running the server-side part of the game. But for you to connect to it and play, you need to run a client.
There are several ways to run a client, but the fastest one for local development is to run one through the Unity Editor. (SpatialOS’s UnitySDK automatically hooks the client up to SpatialOS.)
Launch the Unity Editor.
In the window that opens, navigate to the folder you unzipped in step 2.1. above, then inside that, open the
In the Unity Editor, double-click on the scene
At the top, click Play ▶.
It’s done when: You see a connection splashscreen in Unity:
CONNECT, then use the
Dkeys to sail your ship.
Explore the world, and have some fun!
3. Open the Inspector
The Inspector is a web-based tool that you use to explore the internal state of a SpatialOS world. You’ll use it right now to find out about the main SpatialOS concepts.
Open the Inspector at
3.1. What you can see in the Inspector window
Entities are the basic building block of a SpatialOS world. Every thing in your game world is an entity.
Entities are made of components, which describe an entity’s properties (like position, health, or waypoints). Later in this lesson you’ll see the values of the components changing in real time; and in future lessons, you’ll add new components to your ship entity.
The main area of the Inspector shows you a top-down, real-time view of the entities in your game world. The entities in this game world include player ships, islands, and fish swimming around:
In the next lesson, you’ll be learning how to add new entities to the game world.
The bottom-right list initially shows how many entities of each type there are right now. We’ll look at this area in more detail shortly.
The top-right list shows the workers connected to SpatialOS.
Essentially, workers are just programs that can read from and write to the entities in the world you see in the Inspector.
In this game, all the workers are instances of Unity. There are two types:
- Unity running in headless mode. These workers handle the server-side logic. In the list,
UnityWorker0is of this type.
- Unity running as a game client. There’ll be one of these in the list for every player connected. At the moment, there’s
just one: yours (
The number next to each worker represents its load: a measure of how much work it is doing. SpatialOS uses this number to start and stop server-side workers as necessary.
In this small local game, you’ll only need one
UnityWorker; but if you expanded the game world, you’d need more.
SpatialOS automatically allocates areas of the world to each
UnityWorker, and seamlessly stitches the world together
3.2. (optional) Stop a worker
To see worker management in action, you can stop the worker running the game logic, and see how SpatialOS starts a new one - without any disruption to players at all. To try this:
- Click the name
UnityWorker0in the list of workers. This shows details about that worker.
- Click the red Stop worker button. This shows a confirmation dialog.
- Click the Stop worker button.
SpatialOS stops the worker immediately. Just a few seconds later, the load-balancing algorithm kicks in, and it starts a new worker. Note that nothing at all happens in the game window - the client isn’t even disconnected. Load-balancing is completely invisible to players.
3.3. Sail around
The Inspector shows you a live view of the game world. You can watch your ship’s entity moving in the Inspector as you move it in the game window:
Select your entity in the Inspector window.
If you can’t easily find your entity, zoom out until the entity list on the right includes a
In the list, click on the word
PlayerShip. Every other entity should be dimmed, making the
PlayerShipentity easier to spot:
In the main view, click on the icon of the
PlayerShipentity to select it.
The bottom right area of the Inspector shows you which components an entity has, and the current values of its properties.
For example, the
PlayerShiphas a component called
Position, which stores its position.
Find the property called
Go back to the game window, and use the
Dkeys to move your ship.
You’ll see the values of the position change as you move.
Components are really what define an entity. They can be anything you like, but common examples might be health, or score.
Every entity needs to have a
Position component, that defines its location in the SpatialOS world.
You’ll learn a lot more about components in later lessons: you’ll adapt and extend the existing components of the ship, and add new ones too.
4. Stop the game running
- In Unity, click the Play icon again to stop your client.
- In your terminal, stop the server side of the game by pressing
Ctrl + C.
In this lesson you’ve set up the SpatialOS SDK on your machine, and run the Pirates game for the first time. You’ve also learned about some fundamental SpatialOS concepts: entities, components and workers.
In the next lesson you’ll add some new entities to the world: enemy pirate ships.