Running 5+ servers on one PC? When a Wildcard update lands, SteamCMD has to download 5+ copies of the same files. With AASM's Staging Server feature, you designate one server as the staging target - it does the SteamCMD download once, and the other servers copy files from it locally.

Result: 10x faster fleet updates on big patches, less Steam bandwidth, less risk of partial-download corruption.

Prerequisites:

Two or more servers in AASM.
A spare ~30 GB on the staging install's drive.

Step 1 - Open App Settings

Click the gear icon at the top right of the AASM window. The App Settings dialog opens.

Step 2 - Find the Staging Server section

Scroll to the Staging Server section. Three controls:

Enable Staging Server - master toggle.
Install Path - where the staging ARK install lives (recommend a separate folder from your live servers, e.g. D:\Ark Staging\).
Update Schedule - how often the staging server checks Steam for new builds (typically every 30-60 min).

Step 3 - Enable staging and let it do the first download

Flip Enable on. AASM kicks off the initial SteamCMD download of ARK Dedicated Server files into the staging path. This takes 15-30 min depending on your bandwidth.

Step 4 - Watch live servers pull from staging on their next update

Once staging is current, the next time any of your live servers needs to update, AASM copies the files from staging locally (typically <30 seconds for a full update vs 5-15 minutes via SteamCMD).

v0.8.2 fix relevant here: BUG-16 (morkai1150's report) - earlier builds could silently skip on transient Steam fetch fail and you'd be stuck on an old staging build while live servers updated past it. v0.8.2 added a lastError UI badge that surfaces the failure and a 10-min coalesced fast-retry timer.

Step 5 - Watch for the "stuck staging" badge

The dashboard's staging area shows the staging install's current Steam manifest build ID + the latest available. If they don't match for more than the update interval × 2, investigate (usually Steam timeout - retry manually).

Step 6 - Avoid using staging as a donor when broken

Carry-forward note (v0.8.2): staging shouldn't be used as a donor when files exist but Steam manifest/build ID is missing. checkAndUpdate() attempts a validate-repair first. If staging is in this broken state, AASM falls back to per-server SteamCMD downloads rather than pulling from a half-broken staging install.