# Configuration Lectern operates with minimal required configuration. The plugin registers its network channels automatically on startup and communicates with Lectern-compatible clients over custom payload channels. --- ## config.yml ```yaml version: 1 debug: false ``` | Key | Type | Default | Description | |---|---|---|---| | `version` | Integer | `1` | Internal config version. Do not modify. | | `debug` | Boolean | `false` | Enables debug logging for troubleshooting. | --- ## Network Lectern uses the following custom payload channels: | Channel | Direction | Purpose | |---|---|---| | `lectern:receive_event` | Server → Client (S2C) | Sends effect events to the client. | | `lectern:send_event` | Client → Server (C2S) | Receives client events (keybind presses, button clicks, etc.) from the client. | | `lectern:handshake_c2s` | Client → Server | Client handshake initiation. | | `lectern:handshake_s2c` | Server → Client | Server handshake response. | All effect data is encoded as Base64 payloads over these channels. The channels are registered automatically when the plugin is loaded. No manual configuration is needed. --- ## Reloading The Lectern server plugin supports `/lectern reload` to reload server configuration from disk. See [[Lectern/Server Owners/Commands]] for details. --- ## Related Pages - [[Lectern/Server Owners/Overview]] — Plugin overview and installation - [[Lectern/Server Owners/Commands]] — Full command and permission listing