s&box のアップデート
s&box のツールの最新リリース（新しい順）。 ハブは、自分自身と各ゲームのツールをアプリ内からアップデートします。
- s&box 0.1.8
- Sandbox limits on the Settings page: the prop, explosive and other per-player limits, spawn protection and prop ownership moved from the bottom of the long Server page to the Settings page (which only had backups), where owners look for a game's rules. The Server page's settings card points there. They're saved and applied as before.
- s&box 0.1.7
- Updated before it starts: Facepunch's s&box update of 2026-10-23 (build 26166580) came while the owner's server was stopped, and the half-hourly auto-update only updates a running server, so starting it would have booted the old build that players on the new game can't join. Now, with "Update automatically when Steam has a new build" on, a server on this PC that's behind Steam is updated first whenever it starts (Start, start when s&box Manager opens, planned restarts), the same way as Update (a backup of its config first, the progress on the Server page), and the news says "Updated to build … before starting". If Steam can't be asked (no network, SteamCMD error, no answer in 30 seconds) it starts with the installed build and the console says so. A crash or freeze restart only uses the last known answer (no SteamCMD in a crash loop). With the setting off it starts at once and the news says a new build is out (once per build). Rented servers are updated by their host, as before.
- A game that doesn't load on an old build: s&box's game code is now built for the exact version the server runs, so a server that's behind may fail to load its game. When that happens while it starts and Steam has a newer build (with the same setting on), the server is updated and started again (once per start; if it fails again, it stops with the news as before). The news says "The game didn't load on the old build; updated to … and started again."
- Updates work again on the public branch: seen live on 2026-10-23, SteamCMD was asked for "-beta public" and Steam answered "Access Denied" for the new build, so every update failed; the same update without it went through. Now only a real beta branch (staging) is named. SteamCMD's "state is 0x… after update job" is read as an error and tried again, and a server brought in by its folder gets SteamCMD before its first check.
- Saving the server settings from two places at once (a SteamCMD job and the page) no longer fails with "access denied" on Windows.
- s&box 0.1.6
- Out of preview: s&box Manager has been tried live with real players (joins, chat, kicks, bans, admins, freezes, a game that breaks), so its Preview badge is gone. Adding a rented server keeps its own Preview label until it has been tried on a real host.
- Sandbox limits on rented servers: the Server page's Sandbox limits card now also shows for a rented server running Facepunch's Sandbox (with the panel console set up). The host's start line isn't s&box Manager's, so the limits are typed into the server's console after every start, once its game has loaded (also after a restart from the host's panel, and when s&box Manager opens), and at once when you save while it's connected.
- Admins apply sooner: s&box reads its admins only when the server starts. After Make admin / Remove admin on the Players page or a save on the Admins page that changed who has which claims, a running server with nobody on restarts at once to apply it; with players on, both pages say it takes effect after the next restart, and with the server stopped, at the next start. Changing only a name doesn't restart anything.