> 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/first-start.md).

# First start

What you should see in the console, how to test with a fresh account, and the commands that prove each part works.

### 1. Read the console

A healthy start shows, in order:

| Message contains                                         | Means                                                                                             |
| -------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
| `ClickEm Core enabled.`                                  | ClickEm finished loading.                                                                         |
| Lines per module                                         | Each module enabled. A line such as `reload-module-failed` points to a module with a broken file. |
| `Reloading MythicMobs so ClickEm's custom mechanics ...` | Normal. ClickEm runs one `/mm reload` on the first tick.                                          |
| `Forced /warp to ClickEm's /navigation` and similar      | ClickEm took over command names that other plugins also use. See Troubleshooting.                 |
| A list of pet mob types **missing a texture**            | Informational. They show a spawn egg instead of a head.                                           |
| `Could not start the Redis bus`                          | Only if you enabled Redis.                                                                        |

Warnings to fix: a **licence** message, `Unknown mechanic`, a YAML error with a file name and line number, or `NoClassDefFoundError`.

### 2. Check the modules

In the console:

```
clickem module list
```

Every module in [Modules](/lethium-docs/configuration/modules.md) should be `enabled`.

### 3. Check MythicMobs

```
mm reload
mm mobs list
```

You should see `W1Z1f1` and the other 360 zone mobs plus the five bosses. See [MythicMobs](/lethium-docs/server-setup/mythicmobs.md).

### 4. Test with a player

Join the server with a normal (non-op) account, then:

| Step                                | Expected                                     |
| ----------------------------------- | -------------------------------------------- |
| Accept the **resource pack**        | Menus and icons look right.                  |
| The **tutorial** flight plays       | Then 750 Coins and 10 Essence are paid once. |
| You spawn in the **hub** of World 1 | NPCs and floating signs are around.          |
| `/clickem`                          | The hub menu opens.                          |
| Left-click a mob in **Zone 1**      | Damage numbers, a kill, Coins.               |
| `/coins`                            | Shows your Coins.                            |
| `/upgrades`                         | Buy a first Upgrade.                         |
| `/zones` and `/bestzone`            | Work.                                        |
| Tab list and chat                   | Show your rank badge and clan tag.           |

### 5. Test staff tools with an operator

```
/ceadmin
/ceadmin modules
/ceadmin economy give <you> 100000
/ceadmin zones grant <you> all
/bosskit grant <you> boss1
```

### 6. Check the integrations

```
/papi parse me %clickem_profile_level%
/papi parse me %clickem_balance_coins_formatted%
/lp user <you> info
```

### Common first-start problems

| Problem                                     | Fix                                                                                                       |
| ------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| Server stops with a licence message         | Check `license.key` and the internet connection.                                                          |
| Everything is a `BARRIER` block or a square | The resource pack did not load. See [ItemsAdder](/lethium-docs/server-setup/itemsadder.md).               |
| No mobs in the arena                        | MythicMobs did not load the mob files, or the worlds are not named `World1` to `World5`. Run `/spawners`. |
| `/clickem` says it is starting up           | Wait a few seconds. ClickEm is still loading.                                                             |
| Players cannot walk into Zone 2             | Expected until they unlock it.                                                                            |
| Placeholders show as text                   | PlaceholderAPI missing, or ClickEm's `integrations.placeholderapi` is off.                                |

More in Troubleshooting.


---

# 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/first-start.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.