> 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/daily-rewards.md).

# Daily rewards

Daily login rewards, the reward cycle, streaks and streak insurance.

File: `plugins/ClickEmCore/modules/daily-rewards.yml`. Module id: `daily-rewards`. Commands: `/dailyrewards`, `/daily`, `/dailyreward`, `/dailyrewards claim`.

Players claim one reward per real day. A streak tracks consecutive days.

### The streak

* Claim every day to keep the streak.
* If a player **skips 2 or more real days in a row**, the streak goes back to day 1 on their next claim.
* **Streak insurance** forgives one missed day. Give it to everyone with `streak-insurance.enabled-for-everyone: true`, or keep it a VIP perk (`streak-insurance: true` under a tier's `perks`; MVP and above have it).

### The reward table

```yaml
cycle-length-days: 0
rewards:
  1:
    currency: 100
    currencies:
      gems: 5
      artifact_essence: 3
  7:
    currency: 1020
    currencies:
      gems: 11
      artifact_essence: 9
    items:
      GOLDEN_APPLE: 1
    bonus:
      currency-mult: 6.0
```

| Key                        | Meaning                                                                                                                                                 |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `cycle-length-days`        | The table repeats after this many days. `0` = the number of days listed (day 8 repeats day 1). Higher leaves empty days, lower only uses the first N.   |
| `rewards.<day>.currency`   | Coins (units scaled by progress).                                                                                                                       |
| `rewards.<day>.currencies` | Other currencies: `gems`, `artifact_essence`.                                                                                                           |
| `rewards.<day>.items`      | `MATERIAL: amount`.                                                                                                                                     |
| `rewards.<day>.bonus`      | A temporary [stat](/lethium-docs/configuration/stats-and-limits.md) buff that lasts until the next day starts, so players re-earn it by claiming again. |

Each day's tooltip frame (Common up to Ancient) follows its place in the list.

### How to

* **Make a week-long cycle:** list days 1 to 7 and leave `cycle-length-days: 0`.
* **Stronger day 7:** edit `rewards.7`.
* **Reward gems only:** remove `currency` and keep `currencies`.

### Staff commands

`/ceadmin dailyrewards set <player> <streak>`, `force-claim <player>`, `reset <player>`.


---

# 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/daily-rewards.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.