config.yml Reference
plugins/AstralChat/config.yml controls which servers are in scope, the global broadcast and private-message formats, the social-spy display, and the channel registry.
Default file
Top-level fields
Field | Type | Description |
|---|---|---|
|
| Server group names where AstralChat is active. Servers in other groups load the plugin but do not handle chat. The check uses the |
| Object | Global MiniMessage formats — see below. |
| Object | Social-spy configuration — see below. |
|
| Channel registry. The map key is internal; the channel's runtime identifier is the |
formats
Field | Type | Description |
|---|---|---|
| MiniMessage | Output of |
| MiniMessage | Output of |
The private-message format is rendered for both sender and recipient — the same component is sent to each side. Use MiniMessage <hover> and <click> to expose actions (the shipped format suggests /m <sender> on click).
social-spy
Field | Type | Description |
|---|---|---|
| MiniMessage | Output for spy receivers. Variables: |
| String | Permission node required to toggle |
| String | Players with this node are never spied on, regardless of their conversations. |
channels
See Channels for the full schema and per-field behaviour.
Reloading
/channel reload and /chat reload both re-read every YAML in the data folder. Running channels are recreated; pause state survives because it is held in ModerationService, not in the YAML.