Skip to content

Restricted Servers ​

A community server is open to anyone by default. Turn on Restricted under Settings → Access on the server's page and only the players you choose can join it. Everyone else:

  • does not see it on the Public Servers page, or on its own page,
  • gets no connect address from the panel,
  • is refused by the Player Management plugin if they connect anyway, with the message "This server is private: you are not on its access list".

Who gets in ​

A player gets in if any one of these lets them in:

RuleWho it covers
Moderators and aboveAlways, so a restricted server can still be moderated
Minimum RoleEveryone at or above the role you pick. No role rule turns it off
PlayersPlayers you add by name. They can always join
EventsMembers of the events you add, only while the event is live: from its start until its end, or indefinitely if it has no end date

Event members are the event's organizers and players, the rosters of its teams, and the rosters, organizers and team owners of its tournaments. The list follows the event: a player added to it, or an event that starts or ends, changes who gets in without anyone editing the server, from the plugin's next sync (every 30 seconds).

Saving ​

Access changes save with the rest of the server's settings, but they need no restart: the panel tells the server's plugin to refresh, and it applies within seconds. This works on external servers too, since all it needs is the Player Management plugin.

The plugin does the refusing

A restricted server is hidden by the panel, but only the Player Management plugin can keep someone who knows the address out. If the plugin has not checked in within the last 3 minutes, the Access section says so: nobody is kept out yet.

How it is enforced ​

  • The plugin holds the server's access list and only fetches it again when the panel reports that it changed.
  • If the panel cannot be reached, the last list stays in force: the server is neither opened up nor locked to everyone.
  • SwiftlyS2 refuses a player at connect, before they load in. A player on the list does not need the server's connect password: the plugin lets them past it.
  • CounterStrikeSharp has no connect hook in this plugin, so a player who is not on the list is kicked as soon as they join. Allowed players still need the connect password, if the server has one.

The SwiftlyS2 connect hook is the one part of the plugin that relies on a game signature. If a CS2 update breaks it, the plugin logs it and falls back to kicking after join until the signature is fixed.

Restricted servers need the Player Management plugin, so they are CS2 only.