# Configuration Chest generates a `config.yml` file in its plugin data folder on first startup. The configuration is minimal by design — most loot table management happens through the in-game GUI or the API. --- ## config.yml ```yaml version: 1 # DO NOT TOUCH!!! ``` | Key | Type | Default | Description | |---|---|---|---| | `version` | Integer | `1` | Internal config version tracker. Do not modify this value. It is used by the plugin to handle config migrations between updates. | Chest stores loot table data as individual `.yml` files in the `plugins/Chest/loot_tables/` directory. You should not edit these files manually — use the in-game GUI (`/chest`) or the [[Lead/Developers/API Reference|API]] to manage loot tables. --- ## Data Storage Each loot table is persisted as its own file in `plugins/Chest/loot_tables/` (e.g., `my_table.yml`). A loot table file contains: - **Name** — A display name shown in the GUI - **Icon** — The material used as the table's icon in menus - **Items** — A list of weighted items, where each item has a serialized `ItemStack` and an integer weight An example loot table (`example.yml`) is bundled with the plugin and generated on first startup. Loot table data is loaded on startup and saved automatically after each edit. Tables can also be reloaded from disk at runtime using `/chest reload`. --- ## Related Pages - [[Chest/Server Owners/Overview]] — Plugin overview and installation - [[Chest/Server Owners/Commands]] — Full command and permission listing