-
Notifications
You must be signed in to change notification settings - Fork 1
Channels
Strings's most powerful system is the channel system. All channel configuration is done in channels.yml.
When a player first joins, their channel is set to default. While default is indeed a channel, it cannot process any messages, instead redirecting the message to another channel that the player has been determined as eligible to message in, despite not necessarily being a member. Similarly, players can be eligible to receive messages from channels they aren't members of, so long as they are within it's scope. Of course, this logic does not apply to all channels (see membership).
If a player is eligible to send a message to multiple channels, the channel the message will be sent to is determined by each channel's priority. The higher the number, the higher the priority.
Of course, players can select what channel they want their message to be sent to, using the /channel command.
A channel's membership strongly influences how channels behave. For the purposes of configuration, there are two to be used: "default" or "permission". Membership is set for channels individually, under each channel's "membership" option in channels.yml.
membership: default
Any player can be eligible to send messages in channels with default membership, but in the case of LocalChannels, they must be in scope.
Similarly, any player can be eligible to receive messages from channels with this membership, as long as they are in its scope.
More information about scope can be found in the description for each channel type.
Channels must have this membership to be considered in the DefaultChannel.
membership: permission
Channels with this membership are more protected, requiring players to be members of the channel to receive messages, and the channel must be sent as their active channel in order to send messages.