# Lobby

### Prefix

The prefix is used by default with every message. It can be set in the message files at the beginning of each message. To set it, simply write `%prefix%` (placeholder). This will then be exchanged by the system with the prefix entered in `config.yml`.

```yaml
prefix: "&7[&6System&7]&r"
```

### switchServerMessage

If this setting is set to `true`, when jumping to a player, the message that he has changed the server is displayed.

```yaml
switchMessage: true
```

### Aliases

You can also define so-called aliases that you can enter instead of /lobby. To do this, simply add more points under the item `aliases`.

```yaml
aliases:
  - "hub"
  - "leave"
  - "l"
```

### Default configuration

```yaml
lobby:
  prefix: "&7[&6System&7]&r"
  switchMessage: false
  aliases:
    - "hub"
    - "leave"
    - "l"
```

## lobby.yml

You can define your fallback servers in the lobby.yml under `plugins/BungeeSystem/modules/`.

### normal

If you are using CloudNet v3, enter your LobbyTask under server.

```yaml
server: "Lobby"
```

However, if you only use BungeeCord, list all lobby servers as in the example here:

```yaml
server:
- "ServerName-1"
- "ServerName-2"
```

### silent

If you have silent lobbies, you must first set `enabled: false` to `true`. Then set the `server` item as [normal](#normal). So that your players can now be automatically connected to the silent server, you must enter the permission that the player requires.\
`priority` means which server should be prioritized.

### premium

If you have premium lobbies, set them up in exactly the same way as the [silent](#silent) lobby.

{% hint style="info" %}
The priority is essentially about which server/servertask the player is sent to if silent and premium lobby is activated and the player has both permissions.
{% endhint %}

### Default lobby.yml

```yaml
fallbacks:
  normal:
    # if using CloudNet v3 please insert task name
    # if using only BungeeCord please insert server names
    # server:
    # - "ServerName-1"
    # - "ServerName-2"
    # etc
    server: "Lobby"
  silent:
    enabled: false
    server: "SilentLobby"
    # for no permission please leave empty
    permission: "bungeesystem.lobby.silent"
    # lowest = 1
    # The lower the number, the higher the priority
    priority: 1
  premium:
    enabled: false
    server: "PremiumLobby"
    permission: "bungeesystem.lobby.premium"
    priority: 2
```

## Command

### Syntax

```
/lobby
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki-en.herrtechniker.eu/bungeesystem/module/lobby.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.