> For the complete documentation index, see [llms.txt](https://edseries-plugins.gitbook.io/p/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://edseries-plugins.gitbook.io/p/pinnaprison/getting-started/main-configuration.md).

# Main Configuration

The core settings live in `config.yml`.

## Data storage

```yaml
data:
  method: h2
  save-interval: 120 # in seconds
```

* **`method`** — the storage backend used for all player data. `h2` is a fast embedded file database and needs no setup.
* **`save-interval`** — how often (in **seconds**) player data is flushed to storage. `120` = every 2 minutes. Data is also saved when a player quits and on server shutdown.

## Shared enchant settings

The `enchants:` section holds settings shared by **all** enchants. The per-enchant files live in `enchants/<id>.yml` (see [Enchants](/p/pinnaprison/core/enchants.md)).

```yaml
enchants:
  gui:
    requirement-not-met: '&c&lLOCKED &7(Requires &fPickaxe Level %pinnaprison_notation_{amount}%&7)'
    available: '{prim-color}&lCLICK HERE'
    maxed-out: '{prim-color}&lMAXED OUT'
    requirement-not-met-sound: 'ENTITY_VILLAGER_NO'
    requirement-not-met-item:
      material: BARRIER
      name: '&c&lNot High Enough Level'
      lore:
        - '&7Your pickaxe must be level %pinnaprison_notation_{amount}%&7 to'
        - '&7purchase this enchant.'
  prestige:
    star-icon: '&e⭐'
    stars-format: '&7[%stars%&7]'
    requirement-currency-format: ' &b* &7Cost: &c%amount% %currency%'
    requirement-level-format: ' &b* &7%level%: &f%amount%'
```

### `enchants.gui`

Controls how enchant entries render inside the enchant upgrade menus.

| Key                         | Description                                                                            |
| --------------------------- | -------------------------------------------------------------------------------------- |
| `requirement-not-met`       | Status line shown on an enchant the player can't buy yet. `{amount}` = required level. |
| `available`                 | Status line on a buyable enchant. `{prim-color}` = the enchant's primary colour.       |
| `maxed-out`                 | Status line on a fully-levelled enchant.                                               |
| `requirement-not-met-sound` | Sound played when clicking a locked enchant (`''` disables it).                        |
| `requirement-not-met-item`  | The item shown in place of a locked enchant.                                           |

### `enchants.prestige`

Shared formats for the prestige display used by every enchant.

| Key                           | Description                                                          |
| ----------------------------- | -------------------------------------------------------------------- |
| `star-icon`                   | The single star used to build the prestige stars string.             |
| `stars-format`                | Wrapper around the stars (`%stars%` = the filled/empty star string). |
| `requirement-currency-format` | One line per currency requirement (`%amount%`, `%currency%`).        |
| `requirement-level-format`    | One line per leveling requirement (`%level%`, `%amount%`).           |

## Logging

```yaml
logging:
  debug: false
```

* **`debug`** — set to `true` to print extra debug information to the console. Leave `false` in production.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://edseries-plugins.gitbook.io/p/pinnaprison/getting-started/main-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.