Using Swarm Drone and Skitter in Discord

The Swarm Hosts Discord server has two assistants with different jobs:

Assistant Use it for How to start
Swarm Drone Account linking, server lists, status, resource usage, redacted logs, confirmed lifecycle actions, and structured support intake Run a /swarm or /support slash command
Skitter Conversational troubleshooting, follow-up questions, documentation guidance, and support-thread triage Mention @Skitter in #support

Swarm Drone responds to the slash commands you choose; it does not act on normal chat messages or decide which action to take. Skitter helps describe problems, records support cases, and can collect sanitized diagnostics with your consent. It cannot restart servers, edit files, change settings, or perform repairs.

Most /swarm commands need your Discord account linked to your Swarm Hosts account.

  1. In the Swarm Hosts Discord server, run /swarm link.
  2. Open the private Link Swarm Hosts Account button in Swarm Drone's reply.
  3. Sign in to Swarm Hosts and confirm the Discord account shown on the page.
  4. Return to Discord and run /swarm me.

The linking URL is short-lived and should not be shared. Only you can see Swarm Drone’s replies to your account-specific commands.

Run /swarm unlink when you intentionally want to remove the connection. The unlink happens immediately; there is no confirmation button. You can link the same Discord account again later.

Swarm Drone commands

Command What it does
/swarm help Shows the main Swarm Drone command list
/swarm link Creates a private, short-lived account-linking flow
/swarm unlink Immediately removes the Discord account link
/swarm me Shows the currently linked Swarm Hosts account
/swarm servers Lists up to 15 Swarm Servers you can access
/swarm status server:<server> Shows lifecycle status, game, host, and current action
/swarm connect server:<server> Shows safe public or local player connection addresses and protocols
/swarm health server:<server> Summarizes runtime, Swarm Host, relay, and public reachability health
/swarm resources server:<server> Shows current CPU and memory usage
/swarm logs server:<server> [lines:<1-200>] Shows a bounded, redacted recent log tail
/swarm players server:<server> Shows the current player count and available names when supported and permitted
/swarm backups server:<server> Lists recent backups with state, size, and timestamp
/swarm schedules server:<server> Shows configured backup schedules and their next run
/swarm history server:<server> Shows recent account activity and runtime events for the server
/swarm version server:<server> Shows configured, detected, and latest approved game versions
/swarm permissions server:<server> Explains which server capabilities your account can use
/swarm hosts Lists up to 15 accessible Swarm Hosts with live state and resource usage
/swarm maintenance Lists accessible servers with active work or health warnings
/swarm notifications [topic] [enabled] Shows notification topics or enables/disables one email topic
/swarm docs [topic] Opens the relevant public Swarm Hosts guide
/swarm action server:<server> action:<start\|stop\|restart\|backup\|update> Shows a confirmation prompt, then queues the selected action
/support status [case] Shows your latest or selected Discord support case

For commands with a server field, start typing the server name and choose the result from Discord's autocomplete list. Do not leave the display name as plain text. The selected result identifies the intended Swarm Server.

Confirmed actions

/swarm action supports only start, stop, restart, backup, and update. An update keeps the server's existing resource allocation while queueing the normal managed update workflow. Swarm Drone first displays the selected server and action with Confirm and Cancel buttons. Nothing is queued until the person who opened the prompt chooses Confirm. Another member cannot confirm it for them.

Use the browser control plane for typed, game-specific Server Actions. Swarm Drone does not accept raw console, RCON, shell, or plugin commands.

Everyday monitoring

Use /swarm health for the fastest high-level check. It separates the game runtime, Swarm Host connection, relay path, and public reachability so an offline host is not confused with a stopped game server. Use /swarm connect for copyable player addresses and /swarm players for the current count.

/swarm maintenance is an exception list: it shows only servers with queued work, a transitional or failed state, or a reachability warning. An empty list means Swarm Drone did not find an active warning; it is not a substitute for a game-client join test.

Use /swarm backups and /swarm schedules to review recovery coverage. Creating or changing schedules and restoring a backup remain browser tasks.

Use /swarm notifications without options to review all email topics. To change one topic, select it and provide enabled:true or enabled:false. Changing a topic does not disable account email globally.

Open a structured support case

Run /support new to open a case with structured fields. Mentioning @Skitter in #support also creates a case when intake succeeds and continues the conversation in a thread. For /support new, supply:

  • summary: what went wrong, without credentials or private data;
  • area: game server, Swarm Host agent, connectivity, backups, mods or content, account or billing, security, or other;
  • optional game and version context;
  • optional server, selected from autocomplete;
  • optional visibility: public sanitized support, the default, or the private support lane; and
  • optional diagnostics: permission for bounded, read-only diagnostics on the selected server.

Diagnostics require a selected server that your linked account can access. Permission lasts one hour and applies only to read-only diagnostics for that case and server. It does not authorize server actions. For a case opened with Skitter, ask it in that support thread to revoke consent.

Swarm Drone returns a case identifier when intake succeeds. Keep that identifier in follow-up messages so staff can find the same case.

You can also open Support cases in the Swarm Hosts app. Each case shows its status and last activity, with a link back to its Discord thread or support channel. Link the same Discord identity to your account to see earlier unlinked reports. Use the readable case number, such as SUP-12AB34CD, when following up.

Run /support status to show your most recent case, or supply an identifier to select one of your 25 most recent cases. Results are visible only to you. Ask support about older cases.

Ask Skitter for conversational help

Mention @Skitter in #support and include one issue at a time:

  • what you are trying to do;
  • what happened and what you expected;
  • the game or Swarm Server involved;
  • what you already tried; and
  • a short, redacted error when available.

Keep the case identifier Skitter provides and continue in its thread. Follow-up messages there do not require another mention. If Skitter does not respond, use /support new so the case is recorded, then include the case identifier in #support.

Skitter is intentionally scoped to the support workflow. Do not expect a free-form mention in unrelated or private testing channels to start customer support intake.

If you need a person, ask Skitter in the case thread. It can put that case in the human support queue and confirm when the handoff succeeds. A queue confirmation does not mean someone has already been assigned or promise a response time.

Privacy and safety

Never paste passwords, API tokens, bot tokens, billing details, private keys, cookies, complete environment files, private URLs, or unredacted logs into Discord. Review copied support reports before sending them.

Account identity, server lists, resource readings, logs, and action prompts are ephemeral. A public support thread should contain only sanitized context. Choose the private support lane for account, deployment, endpoint, or local-network details that should not be public.

Community history and optional Skitter help offers are being prepared and are not enabled by the channel setup. Before activation, a pinned notice will name the channels covered and explain staff access, retention and deletion, and any AI processing. Help offers will require your explicit opt-in; opening a case from an offer will require separate acceptance. Read the community privacy notice, or email info@swarmhosts.com for a private data request.

Troubleshooting

The command is missing

Make sure you are using the official Swarm Hosts server and a channel where application commands are allowed. Type /swarm and choose the command shown under Swarm Drone.

Swarm Drone says the account is not linked

Run /swarm link, complete the website confirmation, and verify with /swarm me.

Swarm Drone cannot find the server

Run /swarm servers first. Then rerun the command and choose the server from autocomplete instead of submitting a typed display name.

A server action did not run

Check that you selected the intended server and chose Confirm. Canceling or closing the prompt does not queue an action. Use /swarm status and /swarm logs to review the result.

For a broader escalation checklist, see Support Checklist.