> 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/commands/permissions.md). # Permissions Every ClickEm permission node, who has it by default, and how to give it with LuckPerms. Permissions decide who can use a command or a perk. ClickEm works with **any permissions plugin**. This setup uses **LuckPerms**: see [LuckPerms](/lethium-docs/server-setup/luckperms.md) for the ranks. ### The nodes | Node | Default | What it does | | -------------------------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `clickem.command` | everyone | Use every ClickEm command. Without it, a player cannot type `/clickem` or any shortcut. | | `clickem.admin` | operators | **Everything staff.** `/ceadmin`, `/clickem reload`, `/clickem module ...`, `/setspawn`, `/bosskit`, `/tutorial build`, `/language reload`, `/coins `, the Admin Panel button in the hub, and the admin part of every module command. | | `clickem.zones.bypass` | operators | Walk through zone borders freely, teleport anywhere, and own every `clickem.zone.*` node. For staff who build or test. | | `clickem.vip.` | nobody | Gives a VIP tier without LuckPerms groups. `` is any tier id in `vip-perks.yml`: `vip`, `mvp`, `elite`, `supreme`, `legend`, `ultimate`, `clicker`. | | `clickem.fly` | nobody | Allows `/fly` without a VIP tier (`essentials.fly` also works). | | `clickem.autoattack.targets.` | nobody | Raises a player's auto-attack target cap to `n`. The **highest** number the player has wins. | | `clickem.autoattack.targets.unlimited` | operators | No auto-attack target cap. | | `clickem.anti-afk.bypass` | nobody | Never gets the anti-AFK human check. | | `clickem.zone.` | automatic | ClickEm gives this **by itself** for every zone a player owns, so other plugins (crates) can check zone ownership. Do not give it by hand unless you use it as a zone sale, see below. | {% hint style="info" %} `plugin.yml` also declares `clickem.vip.vip-plus`, a leftover from an older tier list. The current tiers are the seven listed above. `clickem.vip.vip-plus` has no effect unless you add a tier with that id. {% endhint %} ### Giving permissions ``` /lp group default permission set clickem.command true /lp user permission set clickem.admin true /lp group vip permission set clickem.autoattack.targets.3 true /lp user permission settemp clickem.vip.mvp true 30d accumulate ``` Operators (`/op`) automatically have every `op` default above. **For real staff, use LuckPerms groups with only the nodes they need**, and do not give out op. ### Zone permissions as a sale A zone can require a permission (`required-permission` in `zones.yml`). That is a way to sell or reward a zone outside the normal gates: ```yaml requirements: required-permission: "clickem.zone.bonus" ``` ``` /lp user permission set clickem.zone.bonus true ``` ### Permissions for other plugins in this setup | Plugin | Nodes | Notes | | ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | | **LuckPerms** | `luckperms.*` | Only for trusted staff. | | **EssentialsX** | `essentials.msg`, `essentials.reply`, `essentials.r`, `essentials.msgtoggle`, `essentials.fly`, `essentials.` | The default group has only the first four. See [EssentialsX](/lethium-docs/server-setup/essentialsx.md). | | **WorldGuard** | `worldguard.region.bypass.*`, `worldguard.*` | Builders need bypass. | | **LPC (chat)** | `lpc.colorcodes`, `lpc.rgbcodes`, `lpc.clearchat`, `lpc.reload`, `lpc.cooldown.chat.bypass`, `lpc.cooldown.command.bypass`, `chat.hover.supporter` | Colour in chat is operator-only by default. | | **LethiumBans** | `donutban.*` (the nodes keep the plugin's original name) | See [Staff moderation](/lethium-docs/server-setup/staff-moderation.md). | | **EasyCommandBlocker** | `ecb.tab.` | Which tab-complete list a player sees. | | **LethiumMessages** | `lethiummessages.admin`, `.receive`, `.toggle` | | | **DeathControl** | `deathcontrol.admin` | | | **AdvancedPortals** | `advancedportals.*` | Creating portals. | | **FancyNpcs / FancyHolograms** | `fancynpcs.*`, `fancyholograms.*` | Editing NPCs and holograms. | | **MythicMobs** | `mythicmobs.*` | Spawning and reloading. | ### A sensible starting setup | Group | Give | | -------------------- | --------------------------------------------------------------------------------------------------------------------------- | | `default` | `clickem.command`, `essentials.msg`, `essentials.reply`, `essentials.msgtoggle`, `ecb.tab.default` (already set) | | `vip` to `clicker` | Their `clickem.vip.` (most are matched by LuckPerms group automatically), optionally `clickem.autoattack.targets.` | | `helper`, `mod` | `donutban.staff` and the moderation nodes they need. **Not** `clickem.admin`. | | `admin` | `clickem.admin`, `clickem.zones.bypass`, `worldguard.region.bypass.*` | | `owner`, `developer` | Everything | --- # 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/commands/permissions.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.