> 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/launch-checklist.md). # Launch checklist Everything you must replace or decide before opening the server to players: links, keys, names, prices and safety. The Clicker package is configured for a working demo. A handful of values are **placeholders** that must be replaced before real players join. Work through this list once. ### 1. Keys and licences | Where | What to set | | -------------------------------------------- | --------------------------------------------------------------------------- | | `plugins/ClickEmCore/config.yml` | `license.key`: your ClickEm licence. | | `plugins/DonutBans/config.yml` (LethiumBans) | `license.key`, `server_name`, `appeal_url` (created after the first start). | | `plugins/ItemsAdder/` | Your ItemsAdder licence. | Never post these files publicly. ### 2. Links and names players will see | Where | Placeholder to replace | | ------------------------------------------ | ------------------------------------------------------------------------------------------------ | | `plugins/LethiumMessages/placeholders.yml` | `https://discord.gg/yourserver`, `https://store.yourserver.com`, `https://tiktok.yourserver.com` | | `plugins/LethiumMessages/commands.yml` | The same three links, written as `(url:...)` inside the lines | | `plugins/TAB/animations.yml` | `play.yourserver.net` in the `ip` animation (every line) | | `plugins/TAB/config.yml` | `&fWebsite: &bwww.domain.com` (only shows if you turn the bossbar on) | | `plugins/EasyCommandBlocker/config.yml` | The `[CLICKEM]` name in `blocked_command_default_actions` if you rebrand | | `plugins/MiniMOTD/main.conf` | The two MOTD lines, the icon and the displayed `max-players` (69) | | `server.properties` | `motd` (overridden by MiniMOTD), `server-name` | The store and Discord **NPCs** in the hub run `/store` and `/discord`, which come from LethiumMessages, so fixing the links fixes the NPCs too. ### 3. Prices and the store | Where | What to decide | | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `modules/vip-perks.yml` | `price-tag` of each tier (shown as text in the menu, for example `€4.99`). Match your real webstore prices. | | Your webstore | Sell the LuckPerms **group** (`vip`, `mvp`, `elite`, `supreme`, `legend`, `ultimate`, `clicker`). ClickEm takes no real money. | | `modules/gemsshop.yml` | Gem prices. You need a way to sell or give out Gems (webstore command `ceadmin economy give gems`). | | `modules/codes.yml` | The sample codes. `LAUNCH2026` runs `lp user %player% parent add launch2026`, which needs a LuckPerms group called `launch2026`. Create it or delete the code. | ### 4. Permissions * Confirm `default` has only what players need. See [Permissions](/lethium-docs/commands/permissions.md). * Give staff **groups**, not `op`. * Put `clickem.admin` only on trusted staff. * Make sure new commands you add appear in EasyCommandBlocker's `tab.default.commands`. Add `/language`, `/lang`, `/verify`, `/captcha` (they are missing from the shipped list). ### 5. Fix the small issues found in the shipped files | File | Fix | | ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | | `plugins/LPC/config.yml` | `chat-tags.gems.display` uses `%playerpoints_points%` (PlayerPoints is not installed). Use `%clickem_balance_gems%`. | | `plugins/DeathControl/config.yml` | `wither` reads `withe#ff1d54 away` and another entry reads `discove#ff1d54`. Fix the typos. | | `plugins/ExcellentCrates/milestones.yml` | `haven''t` should read `haven't` if it shows doubled quotes. | | `plugins/TAB/users.yml` | Remove the example UUID entry. | | `plugins/MobDisabler/config.yml` | Add any world you create. | ### 6. Decide your economy rules * Is the **Vault economy** ClickEm's Coins or Essentials' money? See [EssentialsX](/lethium-docs/server-setup/essentialsx.md). * Turn off modules you will not support: `/clickem module disable ` or `modules..enabled: false`. * Turn on **offline earnings** if you want it (`idle-earnings.yml`). * Decide if **gems** can be traded (`trade.yml`, `gifting.yml`, `auctionhouse.yml` `currencies`). * Review the AFK limits: `combat.auto-attack.max-targets`, `idle-timeout-seconds`, and [Anti-AFK](/lethium-docs/gameplay/anti-afk.md). ### 7. Storage * Pick `sqlite` for one server or `mysql` for a network. Do it **before** players join. See [Storage](/lethium-docs/configuration/storage.md). * Set up **backups** of `plugins/ClickEmCore/data/`, LuckPerms, `plugins/Essentials/userdata/`, the worlds, and `plugins/*/` configuration. ### 8. The resource pack * Rebuild with `/iazip`, check the URL, and join with a fresh client to see the download. * Test on a Bedrock device if you allow Bedrock. ### 9. Network and safety * Firewall: only the Java TCP port and the Bedrock UDP port are public. Keep the database port private. * `enforce-secure-profile`, `online-mode` and the whitelist as you want. * Restart once after all changes and read the console. ### 10. Dress rehearsal With a fresh non-op account, play for 10 minutes: tutorial, first kills, first Upgrade, first zone, first egg, `/quests`, `/dailyrewards`, open the crates. Fix anything that feels wrong before launch. --- # 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/launch-checklist.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.