# Managing Your SCP:SL Game Version (Auto-Update & Branches) (/docs/scp-secret-laboratory/game-version-and-branches)



import { Step, Steps } from 'fumadocs-ui/components/steps';

By default your SCP: Secret Laboratory server updates itself to the latest game build. That's usually what you want — but after a big update you may want to **pin** the current build for a day or two while your plugins catch up. These controls live on the **Startup** tab.

Auto-Update [#auto-update]

| Variable      | Default | What it does                                                                                                                                             |
| ------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `AUTO_UPDATE` | `1`     | On (re)start, the server pulls the latest build from Steam before launching. Set to `0` to stop auto-updating and stay on the currently-installed build. |

When to pin the build [#when-to-pin-the-build]

If a game update breaks your plugins — for example EXILED hasn't updated yet (see [EXILED Compatibility](/docs/scp-secret-laboratory/exiled-compatibility)) — you can buy time:

<Steps>
  <Step>
    Turn off auto-update [#turn-off-auto-update]

    On the **Startup** tab, set **Auto Update** to `0`. The server stops pulling new builds and stays where it is.
  </Step>

  <Step>
    Wait for plugins to catch up [#wait-for-plugins-to-catch-up]

    Once LabAPI/EXILED and your plugins support the new build, set **Auto Update** back to `1`.
  </Step>

  <Step>
    Restart to update [#restart-to-update]

    Restart the server; it updates to the latest build on boot.
  </Step>
</Steps>

<Callout type="warn">
  Pinning is temporary. While you're on an old build, players who've updated to the newest game version **can't join** — the client and server versions must match. Only pin deliberately, and re-enable auto-update as soon as your plugins support the new build.
</Callout>

Beta / Testing Branches [#beta--testing-branches]

Steam beta branches let you run a pre-release or a specific build.

| Variable         | Default   | What it does                                                              |
| ---------------- | --------- | ------------------------------------------------------------------------- |
| `SRCDS_BETAID`   | *(blank)* | The Steam beta branch name to install (blank = the public/stable branch). |
| `SRCDS_BETAPASS` | *(blank)* | The branch's access password, if it requires one.                         |

Set these on the **Startup** tab and restart. Leave them blank to stay on the normal public branch.

<Callout type="info">
  Beta branches are for testing upcoming builds. Your players must be on the **same** branch/version to connect, so a beta branch is best for a dedicated test server rather than your main community server.
</Callout>

Related [#related]

* [Update Your Server](/docs/scp-secret-laboratory/update-your-server)
* [EXILED Compatibility](/docs/scp-secret-laboratory/exiled-compatibility)
* [Install Plugins](/docs/scp-secret-laboratory/install-plugins)