# Configuration There's very little to set up. Lectern works out of the box and sorts out talking to clients by itself. `plugins/Lectern/config.yml`: ```yaml version: 1 debug: false ``` | Setting | Default | What it does | |---|---|---| | `version` | `1` | How Lectern updates your file when you upgrade. Leave it alone | | `debug` | `false` | Extra logging. Turn it on when something isn't working and you're trying to find out why | Changed something? `/lectern reload`. ## How it talks to clients You don't need to configure any of this, it's here so you know what you're looking at if you're watching network traffic or debugging a firewall. Lectern and the client mod talk over four channels: | Channel | Direction | What it carries | |---|---|---| | `lectern:receive_event` | server to client | Effects being sent out | | `lectern:send_event` | client to server | Things the player did, like pressing a keybind or clicking a button | | `lectern:handshake_c2s` | client to server | The client saying hello | | `lectern:handshake_s2c` | server to client | The server answering | These register themselves when the plugin loads. Nothing to do. One thing worth knowing: Recap can capture `lectern:receive_event`, which means a replay can show the cutscenes, camera work and screen shake exactly as they happened the first time. ## Related Pages - [[Lectern/Server Owners/Overview]], what Lectern does - [[Lectern/Server Owners/Commands]], the two commands