What changed in v0.9.2
v0.9.2 is our biggest feature update so far: 43 community-requested features and fixes, plus a security and stability pass across both apps. The headline is that AASM is no longer a single-machine tool — you can now manage ARK: Survival Ascended servers running on other machines from one dashboard. The complete item-by-item list is in the full changelog.
Remote Control
Register a remote AASM instance and its servers appear on your local dashboard, each opening in its own tab beside your local servers. All eight settings tabs — ASA API, mods, backups, maintenance, RCON, access control, cluster and overrides — work against a server on another machine. Access is governed by ten per-token capability grants (lifecycle, config, ASA API, mods, backup, RCON, cluster, maintenance, overrides, access, filesystem) that you tick when minting a token and can change afterwards without re-issuing it; unticking one applies on that token’s very next request. New tokens start at lifecycle-only, first contact pins the remote’s certificate (SSH known-hosts style), and tokens are encrypted at rest.
Security model: a remotely-administered token can never grant itself a capability the calling token does not already hold, and no token can edit its own registry row. Installing native ASA API plugins, wiping data and the rollback family stay administrator-only and local by design.
Server build rollback with pinning
Roll a server back to a previously installed build and pin it so the nightly auto-update cannot silently move it forward again. AASM records a build-history entry on every install and update, every update path respects the pin, and the pin clears the moment you deliberately move off it or press “Return to Latest.” A pre-rollback backup runs first and your saves are never touched.
Config Sets v2 with server-enforced preview
Share configuration across servers with per-server membership and global defaults. Preview-before-apply is enforced by the server, not just the interface: the confirmation is a hash of the exact change set, so a stale preview can never be applied. Every setting shows a badge for what governs it — set, global, override, or nothing.
Player-profile backups with live restore
Automatic profile snapshots on join and leave, a scheduled player-backup tier with retention, and one-click restore. Restore is blocked only when that specific player is online — verified by a live RCON check at the moment you press it — so you can restore an offline player while the server keeps running. If RCON cannot answer, the restore is refused rather than guessed.
More requested capabilities
v0.9.2 also adds multiple fixed daily restart times (a list of up to six, with automatic migration of your existing single time), an omniserver shared-install pattern (several server instances on one install and one update with separate save trees).
Reliability, Linux and community-reported fixes
- Forced stops no longer look like crashes: a bulk shutdown no longer triggers a false crash-restart cycle.
- Update button reliability: the ASA API update action no longer disappears from servers that need it, including when GitHub rate-limits the version check — a failed check is now its own visible state.
- Destructive operations fail closed: delete, move, wipe, restore and update now confirm with the operating system whether a server is running instead of trusting cached status, and refuse when uncertain.
- Configuration safety: blank settings can no longer overwrite a populated INI, and additional INI writers gained line-break protection.
- Linux monitoring: a running server is re-detected after AASM is closed and reopened, and the monitor no longer manufactures false crashes on Linux.
- Companion app: the bundled ASA RCON Manager is version-synced to v0.9.2 with its own stability and safety fixes.
Platform and file details
| Platform | Package | Size | Requirements |
|---|---|---|---|
| Windows | .zip | 377.3 MB | Windows 10/11 or Windows Server 2019+ |
| Linux | .tgz | 291.4 MB | 64-bit graphical session; Ubuntu 22.04+ or Debian 12+ recommended |
For either platform, use at least 16 GB RAM. AASM recommends 32 GB when running multiple ASA servers, plus SSD storage and sufficient free space for server files, staging data and backups.
Upgrade guidance
- Stop active server maintenance and wait for backups or updates already in progress to finish.
- Create a current backup of every world and any shared cluster data.
- Update in-app through Settings → Check for Updates, or download the correct platform archive from this domain and verify its SHA-256 fingerprint.
- Confirm v0.9.2 in AASM before restarting the fleet.
- Run one manual backup and restore-point check before relying on the normal schedule.