> For the complete documentation index, see [llms.txt](https://docs.allout.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allout.game/going-all-out/publishing-your-game.md).

# Publishing Your Game

### Publishing Checklist

Treat this as a “release candidate” checklist. Aim to check every box.

#### Game readiness

* [ ] Your game has a complete and substantial core loop
* [ ] The win/lose (or end) condition is obvious
* [ ] New players can understand the goal in under 30 seconds
* [ ] You have onboarding: tutorial, signs, NPC dialog, or a first-time flow
* [ ] You have a default session length target (short/medium/long) and it feels right

#### Multiplayer + stability

* [ ] You tested with multiple players (not just solo)
* [ ] Late-join works (joining an in-progress game)
* [ ] Disconnect/reconnect doesn’t break a session
* [ ] Players can’t soft-lock themselves (stuck, no inputs, no escape)
* [ ] Spawns/respawns are safe and consistent

#### Performance + feel

* [ ] The game loads quickly enough for streaming audiences
* [ ] There are no obvious frame drops in busy moments
* [ ] Camera and controls feel consistent across the whole game
* [ ] Audio levels are reasonable (no clipping, no extreme volume jumps)

#### Art + clarity

* [ ] Assets and textures look cohesive
* [ ] UI text is readable at typical play distances
* [ ] Key interactables are visually distinct from background props

#### Metadata (what players see before they join)

* [ ] Title + subtitle describe the game in one sentence
* [ ] Loading message explains the core loop or controls
* [ ] Thumbnail/preview is accurate and not misleading
* [ ] You have a short “streamer pitch” (one-liner) ready to paste anywhere

{% hint style="info" %}
Need help with store-facing assets? See [Uploading Metadata](/creator-portal-web/uploading-metadata.md).
{% endhint %}

#### Community Standards

Games on All Out must be generally appropriate for all ages.

* [ ] Your game must be free from extreme realistic violence/blood, nudity, or romantic content
* [ ] Games cannot claim to offer players sparks or other paid virtual currencies
* [ ] Games cannot reference drugs or alcohol
* [ ] Text in games should be free from all profanity

#### Rights and attribution

* [ ] You have the rights to everything you ship (art, audio, brands, logos)
* [ ] You follow any attribution requirements for external assets (if any)

We reserve the right to remove games at any time, for any reason.

### Publishing flow

{% stepper %}
{% step %}
**1) Save Your Project**

If you have a [Git repository](/going-all-out/collaborating-and-version-control.md), we recommend creating a commit before publishing, so you'll be able to track what's changed between releases.
{% endstep %}

{% step %}
**2) Click the "Publish" button in the top right of the editor**

<figure><img src="/files/8GyVEVq4j35iXZoLgCPb" alt=""><figcaption></figcaption></figure>

The "Set Active" checkbox determines if this version will be available immediately. If you want to stage an update to go live later, you can uncheck the box and publish.
{% endstep %}

{% step %}
**3) Monitor Your Launch**

After you publish a new version, monitor active servers and check [Game Error Monitoring](/creator-portal-web/game-error-monitoring.md)

Use [Managing Servers/Updates](/creator-portal-web/managing-servers-updates.md) to rematchmake or stop servers if needed.
{% endstep %}

{% step %}
**4) Ship improvements fast**

Check player feedback and make adjustments!

Players can leave feedback via [Feedback/Ratings](/creator-portal-web/feedback-ratings.md).
{% endstep %}
{% endstepper %}

### After you publish

* Hop in and hang out with your community!
* Check for player [Feedback/Ratings](/creator-portal-web/feedback-ratings.md) and make adjustments
* Reach out if you need any help! See [Developer Support](/going-all-out/developer-support.md).

If you're publishing an update to your game, decide if you want to use the rematchmaking feature to automatically send players to updated servers with [Managing Servers/Updates](/creator-portal-web/managing-servers-updates.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.allout.game/going-all-out/publishing-your-game.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.