# config.yml

```
#Store method: SQLITE / MYSQL
#Restart server after change the option
Store: SQLite
bStats: true
#语言 Chinese / English
Language: English
locale: false
Mysql:
  address: localhost
  port: 3306
  database: test
  user: root
  password: 123456
#MySQLySQL connect pool setting
HikariCP:
  connectionTimeout: 30000
  minimumIdle: 10
  maximumPoolSize: 50
settings:
  #How far away from the cooking pot will force the cancellation of cooking
  cancel-cooking-distance: 15
  #How many cooking pots can each player place by default,
  #and the maximum number of pots can be set by permissions for players: legendarycook.put.limit.AMOUNT
  per-player-put-limit: 5
  #How many cooking pots can each player use simultaneously by default,
  #and the maximum number of cooking pots that players can use simultaneously can be set through permissions:
  #legendarycook.cooking.limit.AMOUNT
  per-player-cooking-limit: 3
  #Can only the person who places the cooking pot destroy it
  only-owner-can-break: true
  #Prompt for the order of dispensing formula materials, lore. When the details in the recipe are enabled, lore will display this description to prompt players on the order of material placement and the heat.
  recipe-details:
    head: '&6Order Of Ingredient Placement:'
    line: ' &f&l· &3Add &a%item% &a×%amount% &3in hot &a%hot%'
    
  #the maximum amount of cook pot per chunk
  chunk-max-pots: 5
  #cook level settings
  level:
    #Max level
    max: 5
    #Experience points required for each level upgrade
    exp:
      #Corresponding to the experience points required for each level upgrade (always maintain the maximum level-1)
      0: 100
      1: 1000
      2: 5000
      3: 10000
      4: 30000

  #When the fail message of the recipe is enabled, players will send a statistical message when cooking fails, which is used to prompt the player which step has the problem
  failed-information:
    format:
      - ' '
      - ' '
      - ' '
      - '&c&lCooking failure information statistics&f(&e%recipe%&f)'
      - '%failed-details%'
      - ' '
      - ' '
      - ' '
    detail: ' &f&l· &7At a heat of &a%hot%&f(%state-hot%&f)&7, ingredients such as %item%&f×%amount%&f(%state-item%&f) &7were added'
    
    state:
      right: '&a&l✔'
      wrong: '&c&l✘'
sounds:
  start-cook:
    name: ENTITY_PLAYER_LEVELUP
    volume: 1.0
    pitch: 1.0
  fail-cook:
    name: ENTITY_VILLAGER_NO
    volume: 1.0
    pitch: 1.0
  success-cook:
    name: ENTITY_FIREWORK_LAUNCH
    volume: 1.0
    pitch: 1.0
  cancel-cook:
    name: BLOCK_GLASS_BREAK
    volume: 1.0
    pitch: 1.0
  hot-down:
    name: BLOCK_LAVA_EXTINGUISH
    volume: 1.0
    pitch: 1.0
  material-input:
    name: ITEM_BOTTLE_FILL
    volume: 1.0
    pitch: 1.0

```


---

# Agent Instructions: 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://gyzer.gitbook.io/legendarycook/product-guides/configurations/config.yml.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.