> 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/rebirth.md). # Rebirth The prestige loop: requirements, what resets, milestone bonuses, and world tiers. File: `plugins/ClickEmCore/modules/rebirth.yml`. Module id: `rebirth`. Commands: `/rebirth`, `/rb`, `/rebirth confirm`. {% hint style="success" %} **Quick start** * Make rebirth easier: lower `chain-multiplier` and `currency-multiplier`. * Drop the boss requirement: delete the world's `boss-requirements` entry. * Reward a rebirth: add a command to `commands-on-rebirth`. * Test: `/ceadmin rebirth force `. {% endhint %} Rebirth is the classic prestige loop. A player resets their progress for a **permanent bonus** that stacks with every rebirth. ### What resets Always reset: **Coins, Zones, Upgrades, Artifacts and Profile Level.** The player is teleported to spawn. Gear is only removed if `reset-gear: true`. Pets, Echoes, Skills, cosmetics, VIP and achievements are kept. ### What a rebirth needs The requirement is **worked out from `zones.yml`**, not typed in here. | Requirement | Where it comes from | | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Coins | At a world-tier milestone: the price of the last zone of the current world x `currency-multiplier` (5). Otherwise the previous requirement x `chain-multiplier` (1.5). | | Kills | The `rebirth.kills` value on the last zone of the world (and the zone before it). Grows by `essence-kills-chain-multiplier` (1.2) between milestones. | | Boss | The world boss must be defeated `kills` times (see `boss-requirements`). | | Right zone | The player must be in the right place. | After the final world tier (15 rebirths, World 5), every further rebirth multiplies the requirements by `late-chain-multiplier` (1.07) so the climb to `max-rebirths` stays reachable. ```yaml world-tiers: 1: World2 3: World3 7: World4 15: World5 ``` Reaching that rebirth count unlocks that world's first zone (through the zone's `min-rebirth`). The counts (plus 0) are also where the requirement formula starts fresh. ### Settings | Key | Default | Meaning | | ---------------------------------------- | --------------------- | ---------------------------------------------------------------------------------- | | `max-rebirths` | 10000 | `0` = unlimited. | | `world-tiers` | 1, 3, 7, 15 | Rebirth count to world unlock. | | `currency-multiplier` | 5 | At a milestone. | | `chain-multiplier` | 1.5 | Non-milestone rebirths. | | `essence-kills-chain-multiplier` | 1.2 | Kill requirement growth. | | `late-chain-multiplier` | 1.07 | After the last tier. | | `cleared-zone-currency-multiplier` | 5 | Zones in worlds already rebirthed out of pay 5x Coins when re-climbed. | | `boss-requirements..mob`, `kills` | `W1Boss`..`W5Boss`, 3 | Boss kills needed to leave that world. Delete an entry to drop the requirement. | | `boss-kills-reset-on-rebirth` | true | The required kills are used up. Extra kills carry over. | | `zone-kills-reset-on-rebirth` | true | Kill counters restart. | | `reset-gear` | false | Strip ClickEm gear on rebirth. | | `commands-on-rebirth` | `[]` | Console commands after each rebirth. `` is replaced. | | `gems.each`, `gems.milestones` | 40, 150 at 1/3/7/15 | Gems paid per rebirth and at milestones. | | `slot-milestones` | pet at 9, echo at 13 | Extra loadout slots earned at a rebirth count. | | `bonus-per-rebirth` | +10 Coins, +2 Luck | Stats applied once per rebirth and stacking. | | `milestones` | see below | One-off permanent bonuses at a rebirth count. All reached milestones add together. | ```yaml commands-on-rebirth: - "give minecraft:diamond 1" - "broadcast reached a new rebirth!" milestones: 5: damage-mult: 50.0 10: damage-mult: 100.0 ``` ### How to * **Make rebirth easier:** lower `chain-multiplier`, `currency-multiplier`, or the `rebirth.kills` of the last zone in `zones.yml`. * **Drop the boss requirement:** delete the world's entry under `boss-requirements`. * **Give a reward at each rebirth:** add a console command to `commands-on-rebirth`. * **Add a milestone:** add a number under `milestones:` with stat keys from [Stats](/lethium-docs/configuration/stats-and-limits.md). * **Change the menu:** `gui.rows`, `gui.slots.confirm`, `gui.confirm-ready-material`, `gui.confirm-not-ready-material`. ### Staff commands `/ceadmin rebirth set `, `/ceadmin rebirth force ` (rebirth ignoring requirements), `/ceadmin rebirth reset `. ### Placeholders `%clickem_rebirth_count%`, `_required_currency`, `_required_kills`, `_kill_progress`, `_boss_name`, `_boss_kills`, `_required_boss_kills`, `_progress_percent`, `_blocked_by`. See [Progress placeholders](/lethium-docs/placeholders/progress.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/rebirth.md?ask=&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.