> 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/getting-started/updating.md).

# Updating

How to install a new ClickEm version safely, what is kept, what is not, and how to pull in new settings.

### The short version

1. **Announce** and stop the server.
2. **Back up** the whole `plugins/` folder and the worlds.
3. Replace the ClickEm jar in `plugins/`. Delete the old one.
4. Start the server and read the console.

### What an update keeps and what it changes

A new jar **never overwrites** files you already have:

| Kept as is                               | Replaced        |
| ---------------------------------------- | --------------- |
| `config.yml`                             | The plugin code |
| `modules/*.yml` and `modules/pets/*.yml` |                 |
| `lang/en_us.yml`                         |                 |
| `data/`, the player database             |                 |

New files (a new module, a new pet) are created when missing. This protects your edits, but **new settings are not added to your old files**.

* The plugin has built-in defaults for every new setting, so **nothing breaks**.
* A lang key missing from your `lang/en_us.yml` falls back to the text inside the jar.
* Changes made to **default values** in the new version **do not apply** to you, because your file still has the old value.

### Bringing in the new defaults

If the release notes mention a new setting, a rebalance, or new text you want:

1. Rename your current file, for example `modules/boosts.yml` to `modules/boosts.yml.old`.
2. Start the server so a **fresh default** `boosts.yml` is created. Stop it again.
3. Copy your own changed values (prices, rewards) from the `.old` file into the new one.
4. Start. Delete the `.old` file when you are happy.

Do this for one file at a time. For `lang/en_us.yml`, copy across only the lines you changed yourself (names, colours, currency names), then run `/clickem reload`.

{% hint style="warning" %}
Do not replace `data/` or the `.db` file. Those are your players.
{% endhint %}

### Code versus configuration

| You changed         | Needs                                              |
| ------------------- | -------------------------------------------------- |
| A new jar           | A **full restart**                                 |
| Configuration files | `/clickem reload` or `/clickem module reload <id>` |
| MythicMobs files    | `/mm reload`                                       |
| The resource pack   | `/iazip` and players re-download                   |

### Updating other plugins

Update one at a time and start the server between them. Watch the big ones:

| Plugin                                                      | Care                                                         |
| ----------------------------------------------------------- | ------------------------------------------------------------ |
| **MythicMobs**                                              | Re-run `/mm reload`. Check the boss skills.                  |
| **ItemsAdder**, **BetterModel**, **BetterHud**              | Rebuild the pack with `/iazip`.                              |
| **ExcellentCrates**, **nightcore**                          | Update both. Back up `crates/` first.                        |
| **ViaVersion**, **ViaBackwards**, **Geyser**, **floodgate** | Update together when Minecraft updates.                      |
| **Purpur**                                                  | Match the Minecraft version supported by every plugin first. |

### Downgrading

Stop the server, restore the backup of `plugins/` (configuration and data together), put the old jar back. Do not mix a new `data/` with an old jar.

### Checking the version

`/version ClickEmCore` shows the installed version. The jar name also contains it.


---

# 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/getting-started/updating.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.