> 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/getting-started/playtesting-your-game.md).
# Playtesting Your Game
### Testing your game
Once you're ready to play your game, hit the green play button at the top of the editor. This will launch the server and client on your local PC to play!
### Testing with multiple local clients
After each feature you build, it's important to launch multiple clients at the same time to make sure that the game functions even when multiple players interact with your game world. This is a common source of bugs, so we make it easy to do this testing.
> Use the +/- buttons next to the play button to determine how many instances of the client to start a time. You can also use the "Add Client" button while testing to add additional clients any time you need.
### Testing with friends
To test your game with friends, publish the game with the upload button in the top right of the editor and set the game's visibility in the creator portal to "Unlisted". Then send the link to the "View Public Page" to your friends!
### Testing on mobile
Since nearly 90% of All Out's player base is on mobile, it's super important to make sure your game plays well on phones!
We make it easy to test on mobile by automatically exposing your local editor server to devices on your local network.
To join, launch your game from the editor with the play button, then open your mobile device. **It must be connected to the same Wi-Fi/network as your PC**.
At the top of the All Out mobile app you'll see a yellow "Join Editor Game" prompt after refreshing.
### Making changes while playing/hot reloading
You can make adjustments to your world and scripts while you have the game running and TODO to hot reload your changes quickly.
---
# 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/getting-started/playtesting-your-game.md?ask=&goal=
```
`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.