To set up LuckPerms, download the build for your server platform, put the single jar in the correct plugins or mods directory, fully restart the server, and grant your account initial access from the console with lp user <your username> permission set luckperms.* true. Then choose storage, create least-privilege groups, and assign users through commands or the web editor.
Playing with friends? Godlike.Host runs hosted Minecraft Java servers from 10 data-center locations, with free DDoS protection.
LuckPerms is a permissions plugin for Minecraft servers. The exact installation path depends on whether you run a Bukkit-compatible server, a modded server, a Bedrock server, or a proxy network.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
What LuckPerms controls
LuckPerms answers the question “which users may perform which actions?” A permission node is a text identifier supplied by another plugin, such as a command or feature. LuckPerms stores the rules, combines them through groups and inheritance, and evaluates them when a plugin asks whether a player has a node.
It is not a replacement for the server software itself. You still need a working Minecraft server and the correct LuckPerms build for that server. The official LuckPerms site describes the project and links to current downloads. Version numbers change; the site displayed version 5.5.87 in the supplied material, so check the live download before installing rather than treating that number as permanent.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Check your platform before downloading
LuckPerms publishes platform-specific jars. A jar built for one platform should not be copied to another merely because both use Java. Identify the software that starts your server, then select its matching LuckPerms download.
| Server arrangement | Where the LuckPerms jar goes | Installation qualification |
|---|---|---|
| Paper, Spigot, or another Bukkit-compatible Java server | plugins |
Use the Bukkit-compatible LuckPerms build. The installation guide recommends Paper for a non-modded Java server. |
| Sponge or a Forge-based modded server using the supported Sponge route | mods |
Use the build intended for that modded platform; the guide identifies SpongeForge for Forge modded servers. |
| NukkitX or another supported Nukkit server | plugins |
Use the Nukkit build. Nukkit serves Bedrock clients, so do not use a Bukkit jar. |
| Velocity or Waterfall proxy | The proxy’s plugin directory | Use the proxy build. A proxy installation is separate from installations on backend servers. |
| Fabric, NeoForge, or another listed platform | The directory required by that platform, normally its mods directory |
Download the matching platform file and follow the current platform notes on the official installation guide. |
The installation guide also names other supported platforms. If your software is not listed by the download page, do not guess which jar to use; verify compatibility on the current official page first.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Install LuckPerms on one server
- Stop or prepare the server safely. Make a backup of the server directory, especially if it already contains permissions data. A running server can overwrite files while you are copying them.
- Download the platform-specific jar. Use the project download linked from luckperms.net. Do not keep several LuckPerms versions in the same directory.
- Remove an older LuckPerms jar. Leave only the version you intend to load. Two LuckPerms jars can cause duplicate loading, startup errors, or ambiguous behavior.
- Copy the jar to the correct directory. Put Bukkit-compatible and Nukkit files in
plugins. Put Sponge and modded-platform files inmods. A proxy jar belongs in the proxy’s own plugin directory. - Start the server completely. A full stop followed by a start is preferable to copying files into a live process. Watch the console for LuckPerms’ enable message and any platform or dependency errors.
- Check that files were generated. After the first successful start, open the LuckPerms folder beneath the server’s plugin or configuration area. The installation documentation identifies
config.ymlas the main configuration file andluckperms-h2.mv.dbas the H2 data file.
If the console never reports a successful enable, stop and fix that problem before attempting permission commands. The most common causes are a mismatched platform jar, a second LuckPerms jar, or an incomplete restart.
Choose storage and protect the generated data
LuckPerms asks you to choose a storage type in its configuration. The usage documentation recommends making that decision near the beginning: changing storage later is possible, but it is easier to plan before you create users and groups. The right choice depends on whether you have one server or several servers that must share permissions.
Single-server considerations
For one server, the default local data arrangement may be sufficient if it meets your backup and reliability needs. Treat the generated database file as live application data. Do not delete luckperms-h2.mv.db to “reset” a problem unless you deliberately intend to lose the stored permissions and have a verified backup.
Network considerations
For multiple servers, choose a storage design that all relevant LuckPerms instances can use consistently, and configure it before building a large permission hierarchy. Back up the configuration and data using your normal server-maintenance process. Keep credentials and database connection details private; a permissions database can grant administrative control over every connected server.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Configuration changes
Edit config.yml only while you understand which setting you are changing. Make a copy first, preserve valid YAML indentation, and restart the server after a significant configuration change. The official configuration guide explains the available settings and their expected values.
Give yourself the first administrator access
On a fresh installation, nobody has access to LuckPerms commands by default. The official usage documentation states this explicitly. From the server console, run the command below, replacing the placeholder with the exact Minecraft username that should administer permissions:
lp user <your username> permission set luckperms.* true
For example, a console command for a player named Alex would be lp user Alex permission set luckperms.* true. Enter it without a leading slash in most server consoles; use a leading slash only where your hosting panel specifically expects one.
This grants that named account LuckPerms’ own command permissions so setup can continue from the console, in-game, or the web editor. Use it for a trusted administrator during setup, not as the default permission set for ordinary players. If you mistype the username, the permission is attached to a different account and your intended account will still be unable to run commands.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Integrated servers normally provide the local user with the access needed to manage the installation automatically. Dedicated servers should use the console command above because it does not depend on an already-working in-game permission path.
Create groups and assign permissions
Build groups around the actions each role actually needs. A typical hierarchy might contain a default group for every player, a moderator group for limited staff actions, and an administrator group for trusted operators. The names are yours; the permission nodes belong to the plugins whose features you are exposing.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Create a group
From the console or an account with LuckPerms command access, create a group with:
lp creategroup <group>
Replace <group> with a simple name such as moderator. Group names are labels used by your permission design, so choose names that remain understandable to other administrators.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteAdd a permission node
Give a group one specific node with:
lp group <group> permission set <node> true
Replace <node> with the exact node documented by the plugin that owns the command or feature. LuckPerms cannot invent a node for another plugin. If the plugin calls its permission example.command, granting a similarly spelled but different node will have no effect.
Assign a user to the group
Make a user inherit the group’s permissions with:
lp user <username> parent set <group>
Use the player’s exact account name. If the user should retain an existing parent relationship, choose the appropriate parent operation instead of replacing the current one; review the command result before making a destructive change.
Use inheritance instead of copying
Put shared permissions in a lower group and let a higher group inherit them. This avoids maintaining the same node list in several places. A staff group can inherit common moderation permissions from a base staff group, while an administrator group adds only the extra nodes it needs. Inheritance is easier to audit than repeatedly copying a long list.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Prefer least privilege
Grant only the nodes required for a role. The wildcard luckperms.* covers LuckPerms’ administrative permissions and should be reserved for trusted setup administrators. Do not give ordinary players broad wildcards simply to make a command work; identify the owning plugin’s exact node instead.
Use the LuckPerms web editor
The web editor is useful when a hierarchy contains many groups, inherited nodes, or contexts. After initial administrator access is working, open it with the LuckPerms editor command from an authorized console or in-game account. The editor presents users, groups, permission nodes, inheritance, and contexts in a form that is easier to review than a long sequence of commands.
- Run the editor command supplied by the current LuckPerms command documentation from an account with administrative access.
- Open the generated editor link and select the user or group you intend to change.
- Add only the documented permission nodes, configure parent groups, and add any required server or world context.
- Review the resulting changes before applying them. Check for accidental wildcard nodes and unintended inherited groups.
- Apply or save the export as instructed by the editor, then verify the server’s response. The general command documentation covers importing a web export; an intentional full replacement can use the optional
--replaceflag.
Use commands when you need a single, explicit change or are working entirely from a console. Use the editor when visual review reduces the chance of missing an inherited permission. Whichever method you choose, keep a backup of the working data before a large import.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Set global, world, and server contexts deliberately
A permission can be global or limited to a context. Global rules apply wherever that LuckPerms instance evaluates them. A contextual rule can apply only in a particular world or backend server, allowing the same player to have different abilities in different parts of a network.
Free tools Windows power users keep installed
One-click scans. No signup required.
World scope
Use a world context when a node should work in one world but not another—for example, a build permission in a creative world. Confirm the exact world identifier used by your server and plugin; a context that does not match the runtime name will look like a missing permission.
Backend-server scope
On a network, set the server context for a permission or group that should apply only to one backend. The name must match the server identifier configured for your network. Keep genuinely shared permissions global so you do not have to duplicate them for every backend.
Context debugging
When a node appears in a group but fails in-game, check whether a more specific context, an inherited rule, or a false assignment is taking precedence. LuckPerms’ Verbose mode is the quickest way to observe the actual check and the value returned for the user.
Install LuckPerms across a proxy network
A proxy and its backend servers perform different permission checks. Install LuckPerms on every backend where a plugin asks for permissions, and install the proxy build where proxy-side commands or features need LuckPerms. Installing it only on the proxy does not make backend plugin checks use LuckPerms.
- Install the matching proxy build in the proxy’s plugin directory.
- Install the matching backend build on each Paper, Spigot, Sponge, or other supported backend that performs permission checks.
- Configure a shared or otherwise coordinated storage arrangement when the network needs common groups and users.
- Set each backend’s
servervalue consistently before creating server-specific contexts. - Restart the proxy and every backend fully, then test a permission on each layer. A command handled by the proxy and a command handled by a backend may require separate nodes and separate LuckPerms instances.
The official network installation guide explains the division between proxy and backend installations. Design the network so a permission is installed where its check actually occurs, rather than assuming that one central jar intercepts every request.
Diagnose permissions that do not work
| Symptom | Checks and corrective action |
|---|---|
| LuckPerms does not appear in the startup log | Confirm that the jar matches the server platform, is in the correct plugins or mods directory, and is the only LuckPerms jar. Stop and start the server again rather than relying on a partial reload. |
| The LuckPerms folder or files were not generated | Look for an enable failure or dependency error in the console. Fix the platform or startup error first; configuration files are generated after a successful load. |
Your account cannot run lp commands |
From the console, run lp user <your username> permission set luckperms.* true with the exact account name. A fresh installation intentionally gives nobody LuckPerms command access automatically. |
| A plugin command remains unavailable | Find the exact permission node required by the plugin that owns the command. Grant that node to the appropriate group, check inheritance, and verify that the user is actually a member of the group. |
| The node exists but works only on some servers or worlds | Inspect the rule’s server and world contexts. Remove an accidental restriction or configure the context to match the runtime identifier used by that backend or world. |
| A permission appears to be allowed but the plugin denies it | Enable LuckPerms Verbose mode and reproduce the action. Observe the permission check and the value returned for the user, then correct the node, context, group, or explicit false assignment shown by the trace. |
| A large web import produced unexpected results | Review the export before applying it. Use the optional --replace flag only when you intentionally want a full replacement, and keep a backup so you can restore the previous data. |
The general command documentation covers information and debugging output, imports, and other command syntax. The official FAQ is useful when a platform-specific error is not explained by the checks above.
Safe maintenance after setup
- Back up before edits. Copy the LuckPerms configuration and data using the same backup schedule as the rest of your server.
- Keep one active jar. When upgrading, remove the old jar, copy the new platform-matched jar, and perform a full restart.
- Review privileged accounts. Periodically inspect who has
luckperms.*or equivalent administrative access and remove it from accounts that no longer need it. - Document contexts. Record which permissions are global and which are tied to a world or backend server. This prevents a future administrator from “fixing” a deliberate restriction.
- Test after changes. Verify a representative player from each group, including a player who should be denied the feature. Use Verbose mode for disputed checks, then disable or exit the diagnostic view when finished.
Keep the generated luckperms-h2.mv.db file with the rest of the permissions data, and never delete it as a routine troubleshooting step. If you need to start over, export or back up what you may need first and make the reset an explicit administrative decision.
Quick Recap
Official documentation
- LuckPerms project site and current downloads
- Installation guide
- Usage guide
- Configuration guide
- Network installation guide
- General commands
- FAQ
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
