> For the complete documentation index, see [llms.txt](https://docs.xandtech.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xandtech.fr/home/xplayercurrencies/configuration/default-configuration-files/default-currency-gems.md).

# Default currency: gems.yml

The exact `currencies/gems.yml` shipped with the plugin - a second example currency showing several options the other way round from `coins.yml` (player-to-player trading off, a fully configured stackable cheque, a one-way exchange rate already enabled, a different menu look).

```yaml
# ============================================================
#                    XPlayerCurrencies
#              Currency definition - "gems"
# ============================================================
# A second example currency, shipped alongside coins.yml to show that XPlayerCurrencies
# supports as many independent currencies as you want, each with its own settings. See
# coins.yml for a detailed explanation of every option below.

enabled: true

name-display: "Gem"
name-display-plural: "Gems"

icon-display: "💎"

symbol: "Gems"
symbol-position: AFTER

decimals: 0
thousands-separator: true

default-balance: 0

min-balance: 0
max-balance: -1

priority: 1

gui-material: EMERALD

command: gems

# A premium-feeling currency, so player-to-player trading is disabled by default (see coins.yml
# for what this does) - flip to true if you do want gems tradeable between players.
allow-pay: false

leaderboard-enabled: true
leaderboard-size: 10

# A smaller, green-tinted leaderboard/logs menu, to show these can look different per currency.
menu-size: 27
menu-border-material: GREEN_STAINED_GLASS_PANE

# A configured, enabled cheque example (see coins.yml for what each option does) - gem cheques
# CAN stack past 1 here, to show the other side of that toggle.
cheque:
  enabled: true
  min-amount: 10
  max-amount: 5000
  stackable: true
  glow: true
  item: PAPER
  name: "&b&lGem Cheque &7- &f{amount_formatted} {icon_display}"
  lore:
    - "&7Redeemable for &f{amount_formatted} Gems&7."
    - ""
    - "&eRight-click to redeem."

plugin-integration: NONE

# Enabled here (unlike coins.yml, which ships this off) so a fresh install already has a working
# example: gems -> coins works out of the box, but coins -> gems doesn't (that pair is left
# disabled over in coins.yml) - showing exchange pairs really are one-way and opt-in each.
exchange:
  enabled: true
  rates:
    coins: 80
    #other: 0.02

restrictions:
  mode: NONE
  worlds: []
  regions: []

# Left off here (see coins.yml for what this does, and shops/coins/example.yml for a working
# demo shop) - flip to true and drop a shop file under shops/gems/ to give gems its own shop too.
shop:
  enabled: false
```

Next: [Default English messages](/home/xplayercurrencies/configuration/default-configuration-files/default-messages-en.md).


---

# 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://docs.xandtech.fr/home/xplayercurrencies/configuration/default-configuration-files/default-currency-gems.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.