> For the complete documentation index, see [llms.txt](https://ae.advancedplugins.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ae.advancedplugins.net/configuration/per-level-descriptions.md).

# Per-Level Descriptions

Starting 9.5.0, it is possible to add per-level descriptions for enchantments. It's very simple to do:

Here is an example with `hasten` enchantment, where you can describle per-level descriptions better:

{% code title="enchantments.yml" overflow="wrap" fullWidth="true" %}

```yaml
hasten:
  display: '%group-color%Hasten'
  applies-to: Tools
  type: MINING
  group: SIMPLE
  applies:
    - ALL_PICKAXE
    - ALL_SPADE
    - ALL_AXE
  levels:
    '1':
      chance: 15
      cooldown: 3
      description: Chance to gain Haste 1 after breaking blocks.
      effects:
        - POTION:FAST_DIGGING:0:40
    '2':
      chance: 25
      cooldown: 3
      description: Chance to gain Haste 2 after breaking blocks.
      effects:
        - POTION:FAST_DIGGING:1:60
```

{% endcode %}

It's as simple as adding a `description` value under each level, just like `chance` or `cooldown` would be added for enchantments! 

In config.yml, you must also change for items and books to utilize %level-description% instead of %description%. This will be located at the bottom of config.yml file, under `settings` (full path: `settings.lore-descriptions.enabled`)

<pre class="language-yaml" data-title="config.yml" data-overflow="wrap" data-line-numbers data-full-width="true"><code class="lang-yaml"><strong># Should enchantment descriptions be added under enchant names in lores?
</strong>#   for per level descriptions use %level-description%. (will default to %description% if level description is not setup)
#   if level description is set, but here it's still still to %description%, the placeholder won't parse!
lore-descriptions:
  enabled: false
  display: "%group-color%* &#x26;8%description%"
</code></pre>

and under `enchantment-book` (full path: `enchantment-book.lore`)&#x20;

<pre class="language-yaml" data-title="config.yml" data-overflow="wrap" data-line-numbers data-full-width="true"><code class="lang-yaml"><strong>enchantment-book:
</strong>  lore:
  - '&#x26;a%success%% Success Rate'
  - '&#x26;c%destroy%% Destroy Rate'
  - '&#x26;e%description%'
  - '&#x26;7%applies-to% Enchantment'
  - '&#x26;7Drag n'' drop onto item to enchant'
</code></pre>


---

# 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, and the optional `goal` query parameter:

```
GET https://ae.advancedplugins.net/configuration/per-level-descriptions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.