OpenSpades Classic 0.75

Available in Staging in the launch menu. Desktop game-client testing is deferred. Client joining, master-list discovery, gameplay, progression, crossplay and mod compatibility remain unverified.

Staging — awaiting client validation

Start with disposable vanilla game data. Player joining, discovery, gameplay, crossplay and mod compatibility await manual evaluation.

Launch

  1. Choose OpenSpades Classic 0.75 from Staging in the launch menu.
  2. Select a supported host with room for at least the offered defaults: 1 CPU cores and 1 GiB memory. Leave extra disk and host capacity for downloads, game data and backups.
  3. Enter a server label, review the allocation and launch. The label identifies this deployment in Swarm Hosts; it does not configure the native server name.
  4. Wait for startup to finish. Review logs and monitoring if it takes longer than expected.

Connect

Copy the player connection address from the Swarm Server page. Use the game's direct connection option with a compatible client version. With a managed relay, use the displayed public port rather than the container's default port. Automatic server-browser listing is not promised.

Start with disposable vanilla game data while client evaluation is pending. See Relays and Port Forwarding for connection requirements and the support checklist when reporting an issue.

This server uses Piqueserver 1.4.2 for OpenSpades and Classic Ace of Spades 0.75. It is incompatible with the separate paid Jagex Ace of Spades game. Stored maps and configuration persist; live block edits reset with the round unless saved separately. Public master listing is disabled. UDP gameplay and the read-only TCP world query use different ports; copy the player connection address, not the query endpoint.

Server distribution

The server uses Piqueserver version 1.4.2 and requires no Steam account. Its game package or release is fixed in the server image. Startup does not automatically download or update the game.

Server distribution and startup contract.

Persistent data and backups

/data retains the native configuration and server-owned files. Stop the server before taking a backup, and preserve the complete directory when moving it. A configuration restore does not establish recovery of player progression; test a backup with your own disposable game data before relying on it.

Server Actions

Server Actions are unavailable during staging. Platform start, stop, restart, files, backups, logs and monitoring remain available according to your role. There are no guided native game settings or raw command/RCON fields in Launch.

Mods & Content

Managed Mods & Content are unavailable for this integration. A game's own mod ecosystem does not imply that Swarm Hosts installs, resolves or verifies those mods. Evaluate the vanilla server before making manual changes.