# Getting Started
This guide walks you through everything you need to build and publish your first game on RUN.game — from installation to your first deploy.
{% stepper %}
{% step %}
**Install Node.js**
You'll need version 20 or higher.
Install Node.js
{% endstep %}
{% step %}
**Install the RUN.game CLI**
The RUN.game CLI is what you'll use to initialize, manage, and deploy your games.
**MacOS / Linux**
Open a Terminal and run:
```bash
curl -fsSL https://github.com/series-ai/rundot-cli-releases/releases/latest/download/install.sh | bash
```
**Restart your Terminal after installation** so it can find the CLI.
**Windows**
Open PowerShell and run:
```powershell
irm https://github.com/series-ai/rundot-cli-releases/releases/latest/download/install.ps1 | iex
```
{% endstep %}
{% step %}
**Verify installation**
```bash
rundot --help
```
You should see a list of available commands. If not, see [Troubleshooting](https://series-1.gitbook.io/rundot-docs/readme/troubleshooting).
{% endstep %}
{% step %}
**Install the RUN.game SDK**
From your project's root folder:
```bash
npm install @series-inc/rundot-game-sdk@latest
```
{% hint style="info" %}
The SDK is updated frequently. To update it, simply re-run the command above.
{% endhint %}
{% endstep %}
{% step %}
**Create your game project**
You have two options: start from a template, or set up a project from scratch.
**Option A: Start from a template**
Templates make it easy to get started. Pick the one that fits your game:
2D game template (Phaser)
3D game template (React)
2D - UI-heavy React game template
Unzip the template, open it in your code editor, and install dependencies:
```bash
npm install
```
**Option B: Build from scratch**
If you're an experienced developer and prefer setting up projects manually:
1. **Use relative file paths.** When deployed, your game is served from a subdirectory. If you use Vite, add this to `vite.config.js`:
```javascript
{
base: './',
}
```
2. **Build to `./dist`.** The CLI looks for your build there by default. You can [customize the build path](https://series-1.gitbook.io/rundot-docs/deploying-your-game#advanced-options) if needed.
{% endstep %}
{% step %}
**Initialize your game**
From your project's root folder:
```bash
rundot init
```
This walks you through naming and configuring your game for the RUN.game platform. It creates a `game.config.prod.json` file that stores your game ID and build settings.
See [Initializing Your Game](https://series-1.gitbook.io/rundot-docs/readme/initializing-your-game) for more details and manual options.
{% endstep %}
{% step %}
**Deploy to RUN.game**
Build and deploy your game:
```bash
npm run build
rundot deploy
```
You'll get a shareable link, playable by anyone on web or in the RUN.game app. The link is unlisted by default — no one will find it on the platform unless you publish it.
See [Deploying Your Game](https://series-1.gitbook.io/rundot-docs/readme/deploying-your-game) for publishing, versioning, and advanced options.
{% endstep %}
{% endstepper %}
## Updating the CLI
The CLI will alert you when a new version is available. To update manually:
```bash
rundot update
```
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://series-1.gitbook.io/rundot-docs/readme/getting-started.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.