> For the complete documentation index, see [llms.txt](https://lethium.gitbook.io/lethium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lethium.gitbook.io/lethium-docs/gameplay/settings.md).

# Player settings

The /settings menu: every personal toggle, its default, and how to reorganise the pages.

File: `plugins/ClickEmCore/modules/settings.yml`. Command: `/settings`, `/prefs`, `/setting`, `/preferences`.

`/settings` lets each player turn off things they find annoying. It is **always available** and cannot be disabled like other modules. The file sets the default state of each toggle for new players, and how the menu pages are organised.

### The toggles

| Toggle                                               | Default | What it controls                                                                                            |
| ---------------------------------------------------- | ------- | ----------------------------------------------------------------------------------------------------------- |
| `earn-messages`                                      | on      | The chat line on each reward.                                                                               |
| `achievement-messages`                               | on      | Messages for your own achievements.                                                                         |
| `other-achievement-messages`                         | off     | Other players' achievement announcements.                                                                   |
| `zone-messages`                                      | on      | Entered and left zone messages.                                                                             |
| `server-announcements`                               | on      | Server broadcast messages (LethiumMessages and ClickEm).                                                    |
| `reaction-titles`                                    | on      | The Very Strong / Weak titles.                                                                              |
| `fury-alerts`                                        | on      | The Fury milestone chat lines.                                                                              |
| `sounds`                                             | on      | Sound effects.                                                                                              |
| `particles`                                          | on      | Particle effects (Fury bursts, cosmetics, zone curtains).                                                   |
| `combat-floating-text`                               | on      | Damage numbers and income text.                                                                             |
| `own-pet-visuals`                                    | on      | See your own floating pets.                                                                                 |
| `other-pet-visuals`                                  | on      | See other players' pets.                                                                                    |
| `pet-glow`                                           | on      | The rarity glow and sparkle on floating pet heads.                                                          |
| `auto-attack`                                        | on      | Auto-attack on your hits.                                                                                   |
| `skip-egg-animation`                                 | off     | Skip the single-hatch animation.                                                                            |
| `hud-pets`, `hud-echoes`, `hud-location`, `hud-main` | on      | The matching HUD panels (BetterHud reads these via [placeholders](/lethium-docs/placeholders/progress.md)). |
| `ability-hud`                                        | on      | The ability action-bar HUD (and its `%clickem_hud_abilities%` value).                                       |
| `profile-visible`                                    | on      | Whether others can open your `/profile`.                                                                    |
| `gifts-allowed`                                      | on      | Receive gift offers.                                                                                        |
| `trades-allowed`                                     | on      | Receive trade invites.                                                                                      |

Each one is stored per player. Change the default under `setting-field:`. **It only affects players who have never changed that toggle.**

### Menu layout

```yaml
gui:
  toggle-slots: [10, 11, 12, 13, 14, 15, 16]
  pages:
    messages: [earn-messages, achievement-messages, ...]
    effects: [sounds, particles, ...]
    display: [auto-attack, skip-egg-animation, hud-pets, ...]
    social: [profile-visible, gifts-allowed, trades-allowed]
```

The menu has one row of toggles per page. `pages` lists which toggles sit on which page in order. Every page id needs a `clickem.settings.category.<id>` name in `lang/en_us.yml`. Any toggle left out is added to the last page so it never disappears.

### HUD panels

The four `hud-*` toggles only **report** the player's choice. The HUD config (BetterHud) must use the placeholder as a condition to actually hide the panel. See [BetterHud](/lethium-docs/server-setup/betterhud.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://lethium.gitbook.io/lethium-docs/gameplay/settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.