Party
Play with other players so that only one needs to go on the server and everyone else follows.
Party
config.yml
Prefix
The prefix is used by default for each 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 replaced by the system with the prefix entered in config.yml
.
switchServerMessage
If this setting is set to true
, the message that the party has changed the server will be displayed when the server is changed.
Whitelist
If you are using CloudNet v3, the 1st step is to enable the CloudNet v3 module under modules in config.yml
.
Then enter the task name here.
If CloudNet v3 is not enabled, you enter the individual names of the servers as they are entered in the config of the BungeeCord server.
defaultMembers
Here you enter the default size of the party's each player may have.
The minimum number of the party has to be 2!
With a value of -1
, there is no limit to the maximum number of players in a party.
maxMembers
Here you can define how many players can be in a party using bungeecord permissions.
The structure is as follows: permission;number of players
Aliases
You can also define so-called aliases that you can enter instead of /party. For this you simply add further points under the point aliases
.
Default Configuration
Commands
Syntax
Partychat
Party chat is for sending messages to the party. Players can see these when they are in the party.
config.yml
Prefix
The prefix is used by default for each 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 replaced by the system with the prefix entered in config.yml
.
Aliases
You can also define so-called aliases that you can enter instead of /partychat. For this you simply add further points under the point aliases
.
Default configuration
Command
Syntax
Last updated