Server Actions¶
Server Actions are safe, game-aware tools for interacting with a running server. They are separate from deployment lifecycle controls and game configuration:
| Area | Use it for | Typical effect |
|---|---|---|
| Server Actions | Player, session, world, and communication tools | Runs against the current server without accepting raw console text |
| Settings → Game Settings | Game configuration such as map, player limit, password, or gameplay rules | Saves configuration and usually recreates or restarts the server |
| Settings → Deployment Settings | CPU, memory, relay, sharing, and other platform controls | Changes how Swarm Hosts runs or exposes the deployment |
| Start / Stop / Restart | Container lifecycle | Changes whether the server process is running |
Open a deployment and choose Server Actions. The page only shows actions that the selected game, server image, current state, and your role allow. Actions remain disabled while the server is stopped, another operation is queued, or a required game-management connection is unavailable.
Swarm Hosts does not provide a raw browser console. Each available action has a fixed identifier, typed fields, server-side validation, role checks, and an audited result. Disruptive actions ask for confirmation.
Current public-game tools¶
| Game | Available tools |
|---|---|
| Minecraft Java | Common Actions, Give Item, Saved Kits, and bounded helper Bots |
| Counter-Strike: Source | Server status, List players, List installed maps, Broadcast message, Set bot quota, Set bot difficulty, Restart round, Change map, and Kick player |
| ARK: Survival Ascended | No browser Server Actions in the current public runtime |
| Factorio | No browser Server Actions in the current public runtime |
| Garry's Mod | No browser Server Actions in the current public runtime |
| Left 4 Dead 2 | No browser Server Actions in the current public runtime |
An unavailable Server Actions page does not mean the deployment cannot be managed. Settings, files, backups, versions, logs, monitoring, and lifecycle controls remain available according to the game and your permissions.
Minecraft¶
Minecraft divides Server Actions into four focused pages:
- Common Actions: Broadcast message, Give XP, Teleport player, Change game mode, Heal, Feed, Clear inventory, Kick player, Ban player, Pardon player, Whitelist add, Whitelist remove, Set weather, Set time, and Set difficulty. The exact options available to you depend on your role.
- Give Item: searches the deployment item catalog, previews generated commands, targets known players, and supports policy-controlled delivery.
- Saved Kits: stores reusable single-item presets or multi-item kits and grants a versioned snapshot through the same preview and audit flow.
- Bots: starts and stops bounded Observer, Greeter, Patrol, or Survival helpers on eligible private or test servers.
Minecraft requires a running server and RCON-enabled settings. Raw RCON commands, shell input, free-form bot behavior, and client-supplied command previews are not accepted.
Counter-Strike: Source¶
Set a non-empty RCON password under Settings → Counter-Strike: Source Settings, save, and wait for the restart. The available action catalog then includes:
- read-only server status, connected players, and installed maps;
- bounded broadcast text;
- bot quota and difficulty;
- round restart;
- change to a discovered installed map; and
- kick by the numeric user ID returned by List players.
Map changes and player kicks require deployment admin access. Arbitrary RCON, unbounded console-variable changes, plugin loading, shutdown, and shell access are intentionally unavailable.
API use¶
For games with a typed action catalog, API clients can fetch the catalog, preview an action, and queue the validated action. See API Access for the endpoint and payload shape.