> For the complete documentation index, see [llms.txt](https://mode-development.gitbook.io/atomcombat/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mode-development.gitbook.io/atomcombat/integrations/luckperms.md). # LuckPerms AtomCombat doesn't call LuckPerms' API directly — instead, [Rank Abilities](/atomcombat/modules/rank-abilities.md) are gated by ordinary Bukkit permission nodes (`atomcombat.ability.dash`, `atomcombat.ability.charged-strike`, `atomcombat.ability.ground-slam`), which is exactly how LuckPerms is meant to integrate with third-party plugins. To gate an ability behind a rank, grant its permission to that rank's LuckPerms group: ``` /lp group vip permission set atomcombat.ability.dash true /lp group mvp permission set atomcombat.ability.charged-strike true /lp group elite permission set atomcombat.ability.ground-slam true ``` This works identically with any permissions plugin, not just LuckPerms — LuckPerms is listed as a soft-dependency purely so it loads before AtomCombat if both are present, ensuring permissions are resolved correctly on join. --- # 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://mode-development.gitbook.io/atomcombat/integrations/luckperms.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.