Menu
  Log out
 

Rust Nexus: The Complete Server Clustering & Linking Guide

Rust Guide • Updated Jan 19, 2026

Rust Nexus: Setting Up Server Clusters

The Nexus system, officially matured in early 2026, allows server owners to link multiple physical dedicated servers together. Players can travel between these servers using ferries or vehicles, effectively creating a massive, multi-server world. This guide covers the technical setup for clusters.

🗺️ What is a Cluster?

  • Nodes: Individual Rust servers (e.g., North Island, South Island, Oil Rig Cluster).
  • Seamless Travel: Players retain their inventory, blueprints, and health when crossing boundaries.
  • Requirement: All servers in a cluster must share the same **Steam App ID** and authentication secret.

Architecture of a Nexus Network

A standard 2026 Rust network consists of a **Hub Server** (typically the most stable island) and several **Satellite Nodes**.

📂 Master Database

Clusters require a shared MariaDB/MySQL database to store player state. When a player "leaves" Node A, their data is serialized to SQL and read by Node B upon entry.

🚢 Ferry System

The ferry acts as the physical transition point. You must configure **Nexus Zones** in your map to trigger the server-handoff when a player enters the designated water boundary.

Technical Setup (RustDedicated.exe)

To enable Nexus, you must add specific launch parameters to every server in the cluster. Ensure the nexus.secret is identical across all nodes.

# Startup Parameters for Node A
+nexus.enabled true
+nexus.secret "YourSuperSecretKey123"
+nexus.id "Server_North_01"
+nexus.master "http://your-master-api-url:8080"
+nexus.zone "North"

The Nexus API

You need a middleware service (The Nexus API) to handle the handshakes. While Facepunch provides a basic binary, most 2026 networks use advanced community versions that support Cross-Server Chat and Global Ban Synchronization.

Infrastructure Considerations

  • Latency between Nodes: Physical nodes in a cluster should be in the same datacenter. If Node A is in New York and Node B is in London, players will experience a disconnect during handoff.
  • Unified Blueprints: In your server.cfg, set nexus.sync_blueprints true to ensure players don't have to relearn items when moving between islands.
  • Map Design: Use **Modular Procedural Generation** files (.map) configured specifically for Nexus zones to ensure coastlines align across nodes.

Common Troubleshooting

"Timed out during handoff"?

This is usually a database lock. Node A has not finished writing the player data before Node B tries to read it. Increase your nexus.handoff_timeout to 15 seconds.

Can players raid across servers?

By default, no. Nexus only supports character travel. However, in 2026, some networks use custom plugins to allow Long-Range Artillery or Missile Strikes to target neighboring nodes in the cluster.

Is this for small groups?

Nexus is designed for 1000+ player networks. Small communities are better off staying on a single 4500-size map to maintain player density.

Next Steps

Clustering Made Easy: Supercraft’s **Nexus-Core** dashboard allows you to link your Rust servers with a single click. We provide the middleware API and the shared database backbone as part of our high-tier Rust plans.

← Back to Rust Guides
Top