> 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/customization/item-format.md).

# Cost & Item Format

Two formats appear all over the config files: the **item** format (used by every GUI item, tool item and pickaxe) and the **action** format (used by reward/command lists). They work the same everywhere.

## Item format

```yaml
item:
  material: DIAMOND_PICKAXE
  name: '&b&lPrison Pickaxe'
  amount: 1
  glow: true
  lore:
    - '&7Line one'
    - '&7Line two'
```

| Key        | Description                                                                                                                                                        |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `material` | The item material. Special forms: `head-<name>` (a player's head), `texture-<base64>` (a custom head from a base64 textures value), and `{placeholder}` materials. |
| `name`     | Display name (colours + placeholders).                                                                                                                             |
| `amount`   | Stack size.                                                                                                                                                        |
| `glow`     | `true` to add an enchant glow with no visible enchant.                                                                                                             |
| `lore`     | A list of lore lines (colours + placeholders).                                                                                                                     |

### Custom heads

To use a custom head, set `material` to `texture-` followed by the base64 **textures** value:

```yaml
material: 'texture-eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQ…'
```

`head-<player>` or `head-{player}` renders that player's own skin as a head.

### Colours

* `&` colour/format codes (`&a`, `&l`, …).
* Hex: `&#RRGGBB`.
* Per-character hex for gradients.
* PlaceholderAPI `%...%` and local `{curly}` placeholders.

## Cost format

Anywhere a price is configured it uses a currency id + amount:

```yaml
cost:
  currency: 'money'
  amount: 1000000
```

| Key        | Description                              |
| ---------- | ---------------------------------------- |
| `currency` | A currency id (a file in `currencies/`). |
| `amount`   | The price.                               |

Some systems use flat keys instead (`cost-currency` + `cost-amount`, or `cost.starting-cost` + `cost.increase-cost-by` for scaling costs) — these are documented on each feature's page.

## Actions

Action lines power every command/reward list in the plugin (`commands-on-explode`, `rewards`, `level-up-actions`, NPC click commands, etc.). Each line is `type arguments`:

| Action                         | Description                        | Example                                   |
| ------------------------------ | ---------------------------------- | ----------------------------------------- |
| `message <text>`               | Send a chat message to the player. | `message &aWell done!`                    |
| `console <command>`            | Run a command from the console.    | `console crate givekey {player} common 1` |
| `player <command>`             | Run a command **as the player**.   | `player autominers`                       |
| `give-eco <currency> <amount>` | Give the player a currency.        | `give-eco tokens {blocks}`                |

`{player}` is always replaced with the player's name. Context-specific placeholders (like `{blocks}`, `{layers}`, `{level}`) are listed on each feature's page.

```yaml
rewards:
  - 'give-eco money 250000'
  - 'message &a&l+ &fYou opened a lucky block!'
  - 'console broadcast {player} hit the jackpot'
```


---

# 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/customization/item-format.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.