> For the complete documentation index, see [llms.txt](https://docs.linuxgsm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxgsm.com/steamcmd/branch.md).

# Branch

Allows the selection of specific builds of a game server in SteamCMD

Game developers sometimes make available several builds of the game server on Steam, often to allow beta testing of new releases. These builds are made available via *branches (betas)* and can be entered in the [LinuxGSM Config](https://docs.linuxgsm.com/configuration/linuxgsm-config.md).

## Find Branches

A list of all available branches for a game server are listed on SteamDB under the appid depots.

{% hint style="info" %}
<https://steamdb.info/app/258550/depots/>
{% endhint %}

## Select a Branch

The default SteamCMD branch is `public`. However, it is possible to use other builds by entering a branch name in the `branch` setting in your [LinuxGSM config](https://docs.linuxgsm.com/configuration/linuxgsm-config.md).

```
# Steam App Branch Select
# Example: "latest_experimental"
branch="staging"
```

## Beta Password

Some branches require a password. This can be done by entering a password in the`betapassword` setting in your [LinuxGSM config](https://docs.linuxgsm.com/configuration/linuxgsm-config.md).

```
betapassword="branchpassword"
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.linuxgsm.com/steamcmd/branch.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
