--- title: "LuckPerms vs PermissionsEx: Why LuckPerms Won | ZCS" description: "Compare LuckPerms and PermissionsEx on maintenance, features, web editor and migration to see why almost every server now uses LuckPerms." url: "https://www.zcraftstudios.com/blog/luckperms-vs-permissionsex-comparison" updated: "2026-10-20T07:16:50.972429+00:00" source: "ZCraft Studios" --- > Site index for AI agents: https://www.zcraftstudios.com/llms.txt (full reference: https://www.zcraftstudios.com/llms-full.txt). Every page is available as Markdown by adding `.md` to its URL or sending `Accept: text/markdown`. 1. [Home](https://www.zcraftstudios.com/) 2. [Blog](https://www.zcraftstudios.com/blog) 3. LuckPerms vs PermissionsEx: Why LuckPerms Won [ All posts](https://www.zcraftstudios.com/blog) # LuckPerms vs PermissionsEx: Why LuckPerms Won ZCraft StudiosOct 3, 2026Updated Oct 20, 2026 Compare LuckPerms and PermissionsEx on maintenance, features, web editor and migration to see why almost every server now uses LuckPerms. ## In this guide - [Development Status](#development-status) - [Inheritance and Group Structure](#inheritance-and-group-structure) - [The Web Editor](#the-web-editor) - [Network Support](#network-support) - [Vault Integration](#vault-integration) - [Is There Any Reason to Still Use PEX?](#is-there-any-reason-to-still-use-pex) - [Migrating From PEX to LuckPerms](#migrating-from-pex-to-luckperms) - [Migration checklist for an existing network](#migration-checklist-for-an-existing-network) - [Use a role matrix to verify the migration](#use-a-role-matrix-to-verify-the-migration) - [Official documentation and links](#official-documentation-and-links) - [Official projects used in this guide](#official-projects-used-in-this-guide) - [A practical verification exercise](#a-practical-verification-exercise) ## LuckPerms vs. PermissionsEx: Why Almost Everyone Picks LuckPerms Now _PermissionsEx (PEX) was the default permissions plugin for years. It's worth understanding why most new setups don't reach for it anymore._ ## Development Status This is the biggest factor by far: **LuckPerms is actively maintained**, with regular updates tracking new Minecraft versions. **PermissionsEx has seen minimal active development** in recent years by comparison. That's a meaningful risk for a plugin as foundational as permissions, where compatibility breaking on a new Minecraft version is a serious problem. ## Inheritance and Group Structure Both support group inheritance, but LuckPerms' implementation is generally considered more flexible, with multiple inheritance paths, per-context overrides (a permission that only applies in a specific world, for instance), and weighted groups for resolving conflicts. ## The Web Editor LuckPerms' `/lp editor` command generates a temporary link to a full web-based permission editor. It's a meaningful usability advantage over typing individual commands for complex setups, and something PEX doesn't have an equivalent to. ## Network Support Both support MySQL for syncing permissions across a proxied network, but LuckPerms' documentation and community support around multi-server setups is considerably more current, which matters more than it might seem when something doesn't sync correctly and troubleshooting help is needed. ## Vault Integration Both integrate with Vault for other plugins to check permissions through, so compatibility with permission-dependent plugins (which is most of them) isn't really a differentiator between the two. ## Is There Any Reason to Still Use PEX? Mainly legacy. A server with years of existing PEX configuration and no pressing need to migrate might reasonably stay on it rather than take on a migration project. For any new setup, though, LuckPerms' active development alone is a strong enough reason to default to it. ## Migrating From PEX to LuckPerms LuckPerms includes a built-in migration command for importing an existing PermissionsEx configuration, converting groups and permissions rather than requiring every rank to be rebuilt from scratch. It's worth checking LuckPerms' own documentation for the exact migration command, since the process can vary slightly by version. ## Migration checklist for an existing network Before changing permission systems, export all existing ranks, user memberships, and permission rules. Keep the old data somewhere you can restore it, and decide whether the new permissions will be stored locally or shared across servers. Do not simply copy permission nodes without checking their meaning. A node may belong to a plugin version you no longer use, and a broad wildcard may grant dangerous administrative capabilities. Test at least four accounts: a new player, a normal member, a moderator, and an administrator. For each account, confirm which commands work, which are denied, and whether prefixes display correctly. | Question | Why it matters | | --- | --- | | Does the plugin support your server version? | Prevents unsupported startup failures | | Can staff edit permissions safely? | Reduces accidental access changes | | Are inheritance rules easy to debug? | Helps explain unexpected command access | | Is cross-server synchronization needed? | Determines storage and network design | For a new setup, prefer a maintained permission system with current documentation. See the [LuckPerms wiki](https://luckperms.net/wiki/Home) before planning a migration. [LuckPermsA permissions plugin/mod for Minecraft servers.On Modrinth ](https://modrinth.com/plugin/luckperms) _Official LuckPerms logo. [Official source](https://github.com/LuckPerms/branding). Illustrative publisher image._ ## Use a role matrix to verify the migration List representative roles across the top of a small permission matrix and important actions down the side. Include actions that should be denied, not only the popular player commands. Test the matrix on a staging copy before and after migration. If an outcome changes, inspect inheritance and context rather than granting a wildcard to make the symptom disappear. Keep the matrix with the migration notes so later updates can use the same acceptance checks. Preserve the original data and export before changing the live setup. Review the supported migration process for the installed versions and confirm which metadata, prefixes or contextual rules it carries over. Compare several real role patterns on the copy without exposing players' personal details. Plan a short rollback decision window and explain the disruption to staff. A clean startup is a useful first check, but it does not prove that player access and moderator boundaries remain correct. ### Troubleshooting paths - Unexpected grant: inspect inherited permissions and context. - Prefix is missing: compare migrated metadata separately from command access. - Backend differs: review world and server-specific rules in the matrix. ## Official documentation and links - [LuckPerms documentation](https://luckperms.net/wiki/Home) - [LuckPerms Setup Guide: Ranks, Prefixes, Tracks and Debugging](https://www.zcraftstudios.com/blog/luckperms-ranks-setup-guide) [LuckPermsA permissions plugin/mod for Minecraft servers.On Modrinth ](https://modrinth.com/plugin/luckperms) ## Official projects used in this guide Open the relevant project for its downloads, supported versions and installation instructions. Install only the plugins needed for the workflow you choose. [LuckPermsA permissions plugin/mod for Minecraft servers.On Modrinth ](https://modrinth.com/plugin/luckperms) ## A practical verification exercise If migrating permissions, export the old group structure and translate each inherited permission deliberately. Test default players, donors and moderators after import. Watch for wildcard nodes and conflicting contexts; a successful data import does not prove safe effective permissions. ## Continue reading - [LuckPerms Config, Placeholders and Verbose Guide](https://www.zcraftstudios.com/blog/luckperms-config-placeholders-verbose-guide) - [LuckPerms Setup Guide: Ranks, Prefixes, Tracks and Debugging](https://www.zcraftstudios.com/blog/luckperms-ranks-setup-guide) [ Previous guide WorldGuard vs GriefPrevention: Land Protection Compared](https://www.zcraftstudios.com/blog/worldguard-vs-griefprevention-comparison)[ Next guide Best Minecraft Anti-Cheat Plugins: Grim, Vulcan, Matrix](https://www.zcraftstudios.com/blog/minecraft-anticheat-plugins-compared)