Signs

Supported software

Server type	Plugin support
Paper and forks	Yes
Spigot	No

Sign registrations and their world must stay together. A persistent hub is the simplest place to run this plugin.To prepare a temporary group server, configure the signs on a persistent staging server, stop it cleanly, and then copy the world and plugins/simplecloud-signs/locations/ into the group template. Do not copy a live world into the template.

Install the plugin

Install the server plugins

Download Signs from GitHub and place it in the Paper server template’s plugins/ folder. Standard SimpleCloud templates already include simplecloud-api; add it through the target’s Plugins setting or the CLI if you use a custom template.

Generate the layouts

Start a matching server. The plugin creates its default layouts under plugins/simplecloud-signs/layouts/.

Place a sign, look directly at it, and run one of these commands:

/sign add group Lobby
/sign add persistent MainLobby

Use the first form for a server group and the second for a persistent server.

Test the sign

Wait for the sign text to update, then click it. A group sign sends the player to the server currently assigned to that sign. A persistent-server sign sends the player to that persistent server when it is available.

Commands

The command is available as /simplecloudsign, /simplecloudsigns, /scsigns, /scsign, /cloudsigns, /cloudsign, /signs, and /sign.

Command	Description
`/sign help`	Show command help
`/sign list [page] [group]`	List registered signs, optionally filtered by target
`/sign add group <group>`	Register the sign you are looking at for a server group
`/sign add persistent <persistent-server>`	Register the sign you are looking at for a persistent server
`/sign remove`	Unregister the sign you are looking at
`/sign remove <target>`	Remove all signs for a registered group or persistent-server target

You must look at the sign block you want to add or remove. The command checks up to 8 blocks away.

Permissions

Permission	Description
`simplecloud.command.signs`	Use the base signs command
`simplecloud.command.signs.list`	List registered signs
`simplecloud.command.signs.add`	Register signs
`simplecloud.command.signs.remove`	Remove the targeted sign
`simplecloud.command.signs.remove.group`	Remove all signs for a target

Layouts

Layouts define what a sign displays for a matching server state. The plugin ships layouts for STARTING, OFFLINE, MAINTENANCE, FULL, EMPTY, and ONLINE. Restart the server after editing a layout because the plugin reads layout files during startup.

name: "online_default"
rule: "ONLINE"
priority: 9
behind-block: "LIME_CONCRETE"
frame-update-interval: 1250

frames:
  - lines:
      - "<color:#22c55e>⚡</color>"
      - "<group>-<numerical-id>"
      - "<player-count>/<max-players>"
      - "<color:#22c55e><b>ONLINE</b></color>"

Field	Description
`name`	Unique layout name
`rule`	Built-in rule name used to decide when the layout applies
`priority`	Higher priority layouts win when multiple layouts match
`type`	Optional target type: `ALL`, `GROUP`, or `PERSISTENT`
`matcher`	Optional name matchers that limit which servers use the layout
`serverName`	Optional proxy registration name; defaults to `%server-name%`
`behind-block`	Optional block material placed behind a directional sign
`frame-update-interval`	Animation interval in milliseconds
`frames`	One or more four-line sign frames

Placeholders

Use MiniMessage placeholder syntax inside layout lines.

Placeholder	Description
`<server-name>`	Group server name or persistent-server name
`<group>`	Group name for group servers
`<numerical-id>`	Numerical ID for group servers
`<persistent-server>`	Persistent-server name
`<server-id>`	Server UUID
`<host>`	Serverhost ID
`<ip>`	Server IP address
`<port>`	Server port
`<min-memory>`	Minimum memory in MB
`<max-memory>`	Maximum memory in MB
`<max-players>`	Maximum players
`<player-count>`	Current player count
`<state>`	Server state
`<property:name>`	Custom server property named `name`
`<property:name:default>`	Custom server property with a fallback value
`<player_name>`	Player name when a player-specific update runs
`<player_sender>`	Player’s current server when available

Server name patterns

The serverName field supports these replacement tokens:

Token	Description
`%server-name%`	Default group server name or persistent-server name
`%group%`	Group name
`%numerical-id%`	Numerical ID
`%persistent-server%`	Persistent-server name

Troubleshooting

The add or remove command cannot find the sign

Look directly at the sign and stand within eight blocks of it before running the command.

The sign stays offline

Confirm that its target exists. A group sign also needs an eligible running server; a persistent-server sign needs that server to be active and registered on the proxy.

A layout change does not appear

Restart the server after editing a layout. The plugin reads layout files during startup.

Introduction

Setup

Configuration

Plugins

Supported software

Install the plugin

Commands

Permissions

Layouts

Placeholders

Server name patterns

Troubleshooting

​Supported software

​Install the plugin

​Commands

​Permissions

​Layouts

​Placeholders

​Server name patterns

​Troubleshooting

Supported software

Install the plugin

Commands

Permissions

Layouts

Placeholders

Server name patterns

Troubleshooting