Global Commands
Global commands let you define commands — like /lobby, /hub, or /spectate — that work across your entire network. You create them once in OrbisManager and they are pushed to all connected servers automatically.
No need to configure the same command on every server individually.
Creating a command
Click + Add Command and fill in:
| Field | What it does |
|---|---|
| Command name | The command players type (e.g. lobby, without the /) |
| Permission | Permission node required to use this command |
| Description | Optional — shown in /help listings |
| Action | What happens when a player runs the command |
| Scope | Which servers the command is available on |
Actions
Transfer
Moves the player to a server or pool. The most common action for commands like /lobby or /hub.
Example: /lobby → Transfer to Lobby Pool
Send Message
Displays a chat message to the player. Useful for info commands.
Example: /discord → Send message Join our Discord at discord.gg/example
Send Message supports TinyMessage tags for colors and formatting. See the TinyMessage guide for available tags.
<gradient:gold:yellow>Join our Discord!</gradient> <color:gray>discord.gg/example</color>
Disconnect
Silently disconnects the player from the network.
Disconnect with Message
Disconnects the player and shows them a reason.
Example: A /kick-self type command for testing, or a /afk-kick system.
Disconnect messages support TinyMessage tags. See the TinyMessage guide for available tags.
Scope
Scope controls where the command is available:
| Scope | Where it works |
|---|---|
| Global | On every server in your network |
| Specific pool | Only on servers in a chosen pool |
| Specific server | Only on one specific server |
Use Global scope for common navigation commands like /lobby and /hub. Use Specific pool or Specific server for commands that only make sense in a certain context, like /spectate in a game server pool.
Permissions
Every command requires a permission node. Players without that permission will see the command as unavailable or not see it at all.
Use orbis.default (or any permission your server grants to everyone) to make a command available to all players.
Real-time updates
Changes to commands are applied instantly. As soon as you save a command in OrbisManager, all connected servers receive the update — no restart required.