Use the RCON console on a running ASA dedicated server
The workspace RCON tab is the admin console for a dedicated server that is running: a persistent localhost RCON session, command history, online survivors, BanList.txt, and ASA administrator whitelist settings.
Readiness while starting and graceful stop still use RCON under the hood; see Start, stop, restart.
What you can do
Section titled “What you can do”- Send console commands and review responses in the session history (history survives switching workspace tabs inside the app session)
- Kick / Ban / Unban from the survivors and ban list panels
- Configure admin whitelist with a remote http(s) AdminListURL or a YARK Hosted Resources admin-list URL (Validate, refresh interval). Save writes
GameUserSettings.iniunless the INI Files tab has unsaved edits; Discard restores the draft. - When the URL is a YARK Hosted Resource, add or remove EOS ids from Admins or the Survivors star; third-party remote lists stay read-only (stars show membership only)
- Use SidePanel Save world / Broadcast, which share the same send path
Host is always 127.0.0.1. Auth uses the profile admin password and the runtime RCON port for that session.
Administrator whitelist
Section titled “Administrator whitelist”ASA auto-admins use EOS / Ark ids (32-character), not Steam ids.
Paste a public http(s) list URL (one EOS id per line — for example a GitHub Gist raw link), or pick a typed admin-list Hosted Resource from the field, then Save. Changing the URL needs a Restart so ASA picks it up; after that the dedicated re-fetches on UpdateAllowedCheatersInterval (default 600 seconds; minimum 3). Edits to a YARK Hosted Resource body republish immediately so ASA re-fetches on the interval without another restart.
The whitelist is not stored in YARK’s database (only the URL and refresh interval are profile/INI settings). Removing an admin asks for confirmation first.
When the console is available
Section titled “When the console is available”| Status | Console |
|---|---|
| running | Connected (with auto-reconnect while running) |
| starting | Not ready yet — wait until status becomes running |
| stopping / stopped | Session torn down after stop |
Related
Section titled “Related”- Start, stop, restart — readiness gated on RCON
- Profiles & ports — RCON port uniqueness and host probes
- Logs & diagnostics — events when commands fail