Rust guide

Rust Clan and Team Size Limits: What Facepunch Documents

Rust Clan and Team Size Limits: What Facepunch Documents Facepunch documents separate controls for ordinary teams and locally managed clans. The cited sources verify the scope of these controls, but the cited clan commit does not identify the local-backend convar by name. Team and authorization limi…

Rust Clan and Team Size Limits: What Facepunch Documents

Facepunch documents separate controls for ordinary teams and locally managed clans. The cited sources verify the scope of these controls, but the cited clan commit does not identify the local-backend convar by name.

Team and authorization limit

Facepunch identifies relationshipmanager.maxteamsize as the convar for changing the maximum team and authorization size:

relationshipmanager.maxteamsize <value>

The same documentation describes Softcore as having a maximum team size of four players, with authorization limited to that team size.

Local and Nexus clan limits

Facepunch's implementation history records three distinct clan-limit behaviors:

  • A convar controls the clan-member limit for the local backend.
  • The Nexus clan implementation retrieves its member limit from Nexus.
  • A non-zero maximum clan-member count is shown in the clan interface.

The cited commit summary does not name the local-backend convar. Consequently, these sources alone do not directly verify that clan.maxmembercount is its exact name.

Facepunch separately describes clans as a more advanced version of teams. Its clan announcement documents additional members, roles and permissions, a separate clan-chat channel, announcement or message-of-the-day text, clan names on player nameplates, and nearby clan-member locations on the map.

The documented separation means administrators should verify the effective team, authorization, and clan limits in their actual server environment, particularly when Nexus supplies the clan limit. For related reporting, follow sourced Rust coverage on TOP OF GAMES.

Sources