# Configuration

CobbleQOL generates its config under `config/CobbleQOL/`.

### Files

* `config/CobbleQOL/config.json` — feature toggles + limits
* `config/CobbleQOL/messages.json` — all player-facing messages

Both files auto-merge on load:

* Missing keys are added automatically.
* Existing values are preserved.

## Example Config:

```jsonc
// config/CobbleQOL/config.json
{
  "enhancements": {
    "maxRareCandiesPerPokemon": 25,
    "enableEnhancementBudget": true,
    "maxEnhancementBudget": 30
  },
  "failure": {
    "enable": true,
    "start": 21,
    "heavyStart": 26,
    "multiplier": 0.5,
    "heavyMultiplier": 0.25
  },
  "movechanges": {
    "enableCooldown": true,
    "cooldownSeconds": 5
  },
  "chat": {
    "prettifyMissingSpeciesNames": true
  }
}
```

#### `enhancements`

Controls shared budgets and caps for enhancement items.

Common options:

* `maxRareCandiesPerPokemon` — per-Pokémon Rare Candy limit.
* `enableEnhancementBudget` — enable/disable shared enhancement budget.
* `maxEnhancementBudget` — maximum enhancements allowed per Pokémon.

#### `failure`

Chance-based failures for enhancements after a threshold.

* `enable` — enable/disable failure chance.
* `start` — budget point where failures begin.
* `heavyStart` — point where failures become harsher.
* `multiplier` — success chance after `start` (e.g., `0.5` = 50%).
* `heavyMultiplier` — success chance after `heavyStart`.

Notes:

* Items are still consumed on failure.
* On failure, the success message is suppressed and the failure message is used.

#### `movechanges`

Move change cooldown (anti-move-spam).

* `enableCooldown` — enable/disable cooldown.
* `cooldownSeconds` — time in seconds.

#### `chat`

Chat-related features.

* `prettifyMissingSpeciesNames` — converts missing species translation keys like `cobblemon.species.ectomancer.name` into `Ectomancer` in server messages.

### Reloading

After changing config/messages:

* `/cobbleqol reload`


---

# 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://dawnshade.gitbook.io/dawnshade-docs/docs/cobble-q.o.l/summary/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.