Yes, the DBs will be compatible
#issues
1 messages · Page 13 of 1
oof i blink and theres 4 new updates.. tried with the newest as of right now and does the same.

Can confirm this happens regardless of the storage system used.
Currently, the server context is a way of isolating permissions to a specific LP instance
That is correct and that is exactly the issue here.
Contexts are used to narrow then the when and where a permission applies. The LP instances themselves are utterly useless in operation. While it makes sense being able to differentiate them (ideally with a dedicated context) it's not something the majority of users care about. They care about the when and where a permission or group ap...
Recently decide to switch to MySQL due to i think it would be better than mysql. So i setup and enter everything in correctly and check and all of the info is the same i use for my currency plugin which works. However once i switch to MySQL i keep getting this issue in console --- >
`[01:08:01 ERROR] [LuckPerms]: Exception occurred whilst loading data for 3be4767d-a9a9-47f1-b104-327f68467865 - LonlyGamerX
java.util.concurrent.CompletionException: java.sql.SQLSyntaxErrorException: Table 'luc...
Assuming you still have your old data in an export, try deleting all luckperms tables.
Also make sure the user you configured in the LP config has permissions to create tables.
Assuming you still have your old data in an export, try deleting all luckperms tables.
Also make sure the user you configured in the LP config has permissions to create tables.
i have tried deleting all the luckperms tables even restart both the plugin and my MySQL but i get the same error and as far as user permission i have everything clicked on. So it has every permission i can give it
Can confirm this still happens with ver v5.2.60
We have about 200 effected users so if a way of also fixing what damage has been done also it would be much appreciated.
This should be resolved in v5.2.61 - nasty bug, sorry about that - didn't show up at all in testing :L
Unfortunately there's no easy way I can think of to fix existing promotions - might be something that you have to do by hand.. sorry.
Try stopping the server, then fully deleting all LP tables, then starting the server again.
Make sure there are no errors when LP enables for the first time - that's when the tables get created.
Description
Clearing all InheritanceNodes from a User adds the group.default right after, adding an extra step (removing group.default) when simulating the parent set command through the API.
Reproduction steps
Sample snippet
// onCommand
final User user = this.luckPerms.getPlayerAdapter(Player.class).getUser((Player) sender);
user.data().clear(NodeType.INHERITANCE::matches);
user.data().add(InheritanceNode.builder("first").build());
this.luck...
Yeaa I have a table added that I use for displaying my ranks on my website, do you think regenerating the table & then manually adding the custom table would work? * this database was a save I pasted in from another MySQL database
Description
I added a new mysql database for bedwarsrel stats then this error happened
Reproduction steps
- Download bedwarsrel and setup a game in a 1.8.8 server,
- when everything is setup and done make it bungeecord,
- then add a mysql database to bedwarsrel stats in its config.
- After that join it from another server,
- you will get many errors in the server log
Expected behaviour
The bedwarsrel plugin to work
Environment details
Sp...
Could you enable debug-logins in the LP config.yml then try again
Could you enable
debug-loginsin the LP config.yml then try again
And then what?
Description
<!-- The placeholder %luckperms_inherited_expiry_time_XXX% and %luckperms_expiry_time_% doesn't display the good amount of time of the permission. -->
Reproduction steps
<!-- Give to a player a permission for more than a month, then parse him the %luckperms_expiry_time_% or %luckperms_inherited_expiry_time_XXX%, it will display a bugged number with for example "15d 38h 10s" so it's fully bugged, it should be "1 month" for example -->
Expected behaviour
...
Same on 1.16.4 with latest version of PAPI and Luckperms 5.2.35.
It displays ">....=>.... [14:13:23 INFO]: 21d 59h 59m 34s" instead of
"Set jobs.boost.all.all.1 to true for warndangerous for a duration of 1 month 1 week 4 days 13 hours 30 minutes 50 seconds in context global."
Update PAPI to a dev build :) https://ci.extendedclip.com/job/PlaceholderAPI/
It seems to work on my test server,
I'll try tomorrow on my official server (after server restart) and let you know ! Thanks :D
[09:36:52] [Server thread/INFO]: [LuckPerms] Loading configuration...
[09:36:52] [Server thread/INFO]: [LuckPerms] Loading storage provider... [H2]
[09:36:53] [Server thread/ERROR]: Error occurred while enabling LuckPerms v5.2.35 (Is it up to date?)
java.lang.NoSuchMethodError: com.google.common.collect.Range.closed(Ljava/lang/Comparable;Ljava/lang/Comparable;)Lcom/google/common/collect/Range;
at me.lucko.luckperms.common.util.Predicates.notInRange(Predicates.java:72) ~[?:?]
at me.luck...
Hello,
We have since days several ArrayIndexOutOfBoundsException: 18 error messages in the console. we have also already installed an extension on it (extension-legacy-api-1.0.0.jar) also without success.
#Info
Plugin version: LuckPerms-Bukkit-5.2.61
Serverjar: Magma version 966e691 (Implementing API version 1.12.2-R0.1-SNAPSHOT, Forge version 14.23.5.2854)
Storage mode: Mysql
Plugins: Multiverse-Core-2.5.0, MysqlInventoryBridge-v2.4.1, Vault, worldedit-bukkit-6.1.9, worldgua...
Use the Bukkit-Legacy version: https://luckperms.net/download
I use bungeecord on my server i use MySQL storage method, but i wanna seprate permissions on servers, on editor i made that /fly can be only done in survival on donor rank, but i dosen't allow to that in survival, i also changed config like this:
The name of the server, used for server specific permissions.
- When set to "global" this setting is effectively ignored.
- In all other cases, the value here is added to all players in a "server" context.
- See: https://github.com/l...
This is really an issue with your Bukkit/Forge hack, but I've added a workaround in LP anyway.
That's not an LP error, so seems like it's working ok?
Please don't disregard the issue template - it's there for a reason...
If you have an actual bug report, then please open another issue and fill it out correctly. Otherwise, the best place to aim any questions is our Discord server.
Feel free to re-open if there's still a problem, I'm going to close this for now.
Description
When a group is set to a user, the user's meta gets set to the previous group's.
Reproduction steps
- Run the command /lp bulkupdate users delete permissions (to clear permissions and groups)
- The user now has the default group set, with a clear user meta
- Set the user's parent to another group
- The user now has the default group meta set as user meta and in order to show the new group info, /lp user meta clear is required.
Expected behavior
W...
Description
Players are able to see a full list of plugins by typing "/" in the chat window. There are other plugins out there that hide this feature, but I believe the LuckPerms resource by itself has the capacity to do this down to the permissions level.
Proposed behaviour
Players ought not to be able to see command help for plugins and features they don't have access to. This could potentially present security risks to the server since hackers could find out what plugins w...
https://prnt.sc/w6s52e
Here's an example of the present issue. With default rank, players can see the commands for worldedit tasks, without the permissions to run them.
LuckPerms doesn't control which commands are sent to clients; if the other plugin registers its commands and permissions properly, just denying the permission will suffice, if not you should seek that plugin's support.
LuckPerms doesn't control which commands are sent to clients; if the other plugin registers its commands and permissions properly, just denying the permission will suffice, if not you should seek that plugin's support.
In most scenarios, denying the permission doesn't suffice for the security of production servers. Why? Because players can still see your plugin commands despite the permission being revoked, providing a way for current vulnerabilities or exploits to be exposed. There are ...
Please re-read the very first sentence of my comment:
LuckPerms doesn't control which commands are sent to clients;
That is completely controlled by the server implementation and again, if the plugin in question registers its commands properly it should not pop up. LuckPerms is a permissions manager and a tree calculator, not a command and suggestions blocker. There are plugins that are made for that purpose but LuckPerms is not one of them.
Please re-read the very first sentence of my comment:
LuckPerms doesn't control which commands are sent to clients;
I understood what you said the first couple times. This is a feature suggestion to to have luckperms control PlayerChatTabCompleteEvent for individual users which is also something I'm fully aware luckperms doesn't control.
That is completely controlled by the server implementation
Not quite. You have the option in spigot/bukkit to disable it entirely which def...
One thing you seem to not get is that permissions and commands are entirely unrelated, LuckPerms controls permissions, not commands. Is that so hard to comprehend?
If my plugin has 2 commands and one permission for only one of them, no matter how many permissions you set to false the other command will still show. This is the case of those specific WorldEdit commands that always show up.
Not only that but there can be permissions that are not attached to any commands too, but rath...
One thing you seem to not get is that permissions and commands are entirely unrelated, LuckPerms controls permissions, not commands. Is that so hard to comprehend?
If my plugin has 2 commands and one permission for only one of them, no matter how many permissions you set to false the other command will still show. This is the case of those specific WorldEdit commands that always show up.
Not only that but there can be permissions that are not attached to any commands too...
This is already handled at the platform level, Luckperms has no reason to involve itself except to further complicate things. Plugins are responsible for declaring things in such a way that the platform can properly handle tab completes.
Description
LuckPerms is showing 3 different permission sets:
Yaml file

Editor

Command

I've run /lp sync but nothing chan...
if you could provide a pastebin of the yaml file and an editor link instead of screenshots, we will be able to place the relation each has in context with the others. Thanks!
Thanks, could you please send a screenshot of the output of /lp info as well as the rest of the information originally requested in the issue template? The reason it is requested is because it allows us to help you quickly, and so we do not have to ask again. If you cannot remember what was originally asked,
is a screenshot of the prompts.
Thank you!
I'm not really clear what the issue is? From your screenshots, it looks like everything is working properly.
The template is not optional, please don't ignore it. It makes it so much more painful for us to help you. If you'd still like our help, please open a new issue and fill out the template properly.
Spigot:

BungeeCord:

Issue:
When I update the group on the bungeecord, the event is not triggered. but when I run it on the spigot it is triggered properly.
Description
When comparing permissions in 3 different ways, the results are inconsistent.
Yaml file

Full file: https://paste.bnn.gg/operator.yml
Editor

Link: https://luckperms.net/editor/fcHndu47IJ
Command
. For the editor screenshot you didn't show the value section so it's impossible for us to tell.
To add on, if are talking about health.set, it is present in all 3 screenshot as well. If you mean the order of the nodes, it's probably not possible/practical to be exact same order due to difference in the way the sort/display nodes and how code map works.
Parent groups are not stored as group.<group> permissions in (text based) storage, they are stored as <group> under parents, that's why they don't (and shouldn't) show on .. permission info when you properly add a parent group, but rather in .. parent info.
Additionally, setting a parent group "permission" to false doesn't "remove" the parent group as many people think.
Does LuckPerms create the permission group.<group> internally?
When I go into the editor and put in permissions it won't work I tried in-game but the same thing other players don't have the permissions I give them.
Please follow the issue template! It makes everything way, way easier to work with and hunt down issues.
And please provide a screenshot of your editor.
Yes and no, they are stored in a special, separate "map"/collection they are put into alongside the regular permissions collection, that's why they are not like other regular permissions and are not shown when you run the permission info command if you add the parent group properly (either with the parent set/add command or from the web editor).
This may be where we are confused about each other's answers. I created the group.x permissions when I was on PEX, it is not intended to have anything to do with LuckPerm's groups.
I do have my parents set up correctly, that is not an issue, I guarantee. But if LuckPerms is automatically adding group.x permissions based on its own internal group structure, that answers my question about where the perms were coming from, considering I don't have group.seniorstaff defined anywhere in the yaml file structure.
Understanding this, I can understand that the yaml file can be different than the editor and the ingame viewer, but I don't understand why the editor and the ...
You can see in your own YAML that parent groups have their own section and are not treated as regular permissions:
parents:
- architect
- moderator
- seniorstaff
To be honest I don't know where that group.builder set to false came from as a permission in storage. Maybe if you set the node to false in the editor it does that (especially since it's the only one)? That's something subject to test and, kind of another issue if that's the case.
I don't understand ...
I'm not sure you're following, as I mentioned, my group.x permissions were created back in PEX, and imported into LuckPerms. Until today I had no idea LuckPerms calculated the group.x permissions itself, I thought parents simply controlled the inheritance, not created a new permission. That is why I have group.builder: false in my config, I manually created it when creating my own group permissions years ago. Accidental name conflict.
I would love if I could disable the feature that calculates these permissions so I can define them myself.
I'm still confused about the differences between the command and the editor; why doesn't group.moderator or group.architect show up in the command? what makes it different from group.seniorstaff? group.builder makes sense, I have it explicitly defined as false, but the other 3 are not defined anywhere in the yaml structure, yet one behaves differently.
I would love if I could disable the feature that calculates these permissions so I can define them myself
Absolutely impossible. That would break so incredibly much. Especially with plugins interfacing with LP.
I'd recommend you scope your own permissions.
Now even if we ignore the practical issues with implementing this as setting, it means support hell. There are already so incredibly many obscure config setting for edge cases that can really mess up an instance if changed carele...
sorry my native language is not english
I have problems connecting luckperms to my database
I have the base in my vps so everything is by default
luckperms works fine being without database but when trying to connect this appears, my session data is correct
`[luckperms-hikari housekeeper] DEBUG me.lucko.luckperms.lib.hikari.pool.HikariPool - luckperms-hikari - Pool stats (total=0, active=0, idle=0, waiting=0)
815548 [luckperms-hikari housekeeper] DEBUG me.lucko.luckperms.lib.hik...
Does this happen when LuckPerms is the only plugin installed?
Screenshot /lp info and two /lp editor links from before and after running the bulk update command please.
Everyone ignores my issue on discord.
So keep posting it.
But also doing what Luck said and creating an issue with the proper template will be very useful.
Everyone ignores my issue on discord.
People both on the Discord server and in here are not paid for support nor are there 24/7 to help; volunteers help because they want to help, but are not obligated to do so. You are completely free to re-post your issue; if you do it in here, please follow the issue template; if you do it in the Discord server maybe ask in #general-2 which is usually less crowded and wait patiently for a response.
Open a new ticket and provide your full log. Be sure to follow the template.
Description
Until a few versions ago when I received a bug report from a LuckPerms user, this is how I have been defining a certain "anti-permission" to basically allow a server owner to declare a select group "newbies" and restrict usage of my plugin:
This has been working well for years - maybe only with other permissions plugins - or without even - and it see...
I can't seem to reproduce the issue, I defined in my test plugin's plugin.yml:
permissions:
some.permission:
default: false

The only thing that comes to my mind is the apply-bukkit-default-permissions setting. Make sure it is set to true in your LP config: https://github.com/lucko/LuckPerms/blob/5c443338927104da858beca9d1306628671bdcac/bukkit/s...
Thank you for your time!
I tried addressing this by reintroducing the permission setting, defaulting to false in my plugin.yml.
This works out of the box, as you pointed out, but then what happens is that admins give themselves the "*" permission to test out all the features, assuming that they have "all permissions", in turn giving themselves a permission that is restrictive in my logic.
Is there a way that I can set up a permission in a way that it will not be granted if a server a...
You just set the specific permission to false. * perm node is not recommended as well. See: https://v2.nucleuspowered.org/docs/nowildcard.html
I know that it is not recommended. No need to convince me :)
But what can I do when server owners do use them when setting everything up and then expect my plugin to work the way they think it should?
If there is no way to prevent this while defining or checking permissions on my end, I will just stick to my current setup that checks for undefined permissions :)
An upcoming version will display warnings about this and maybe explain this behavior to affected server owners.
You just ask them to set the permission node to false, bcu that how permission works, its just true or false, no special whitelist/blacklist to over complicate things.
... and then expect my plugin to work the way they think it should?
And that's the issue and why we are against wildcards, admins and owners not knowing any better blindly sticking * here and there.
Bukkit defaults are used as an ultimate fallback if the permission ends up undefined by any other means (specific permission, Regex, shorthand, wildcard, sponge wildcard, Bukkit child permissions); the wildcard (like any of the other kinds of permissions mentioned) is doing its job, this is ...
Hopefully the above change will solve this issue for you. :)
You'll need to insert the new option into your config, as it defaults to being disabled if the section is missing.
# If the plugin should apply negated Bukkit default permissions before it considers wildcard
# assignments.
#
# - Plugin authors can define permissions which explicitly should not be given automatically to OPs.
# This is usually used for so called "anti-permissions" - permissions which, when granted, ...
Yes, this is very helpful and validating because it is in agreement with how I understand how permissions were defined to work.
I hope that this does not break functionality with plugins that might rely on the asterisk flipping their false to true - however I think we are in agreement that the absolute wildcard should not be used, and specific (parent) wildcards can and should be defined and then used to flip groups of permissions, and also, perms should be set and used as verbose as rea...
Erm, yeah, sorry, I don't think there's much I can do about this at this stage. The group.x has been used by LP since the start, it's not easy for me to move to something else now. Sorry.
Connection refused
Your database server is refusing the connection.
Description
Luckperms contexts are checked in the main thread, making the performance poor when used a lot by plugins
Proposed behaviour
Probably make it async? :/
Do you have any profiling data to back this up?

After asking to one of DiscordSRV dev:
HaeivenAujourd’hui à 19:35
mh... i don't rly understand why the mysql request isn't done in async?
VankkaAujourd’hui à 19:36
because luckperms is calculating contexts for the user on the main thread
And this is not the only one plugin to have this problem, as I see :/
Ah I see - well, ideally DiscordSRV should be caching this value, so the MySQL lookup isn't necessary.
I feel partially responsible, since I initially PRed contexts into DiscordSRV - however, I don't think the MySQL storage was there at the time.. I think that might've been added since.
Anyway, unfortunately there's not much LP can do about this - contexts have to be calculated whenever permissions are checked, which of course is going to happen sometimes on the main thread.
If you'r...
In all fairness, the very first thing that the ContextCalculator interface "specification" mentions is that they ought to be fast and should resolve time-consuming queries and cache their results beforehand:
https://github.com/lucko/LuckPerms/blob/8167fbf73f99debb0cd8c1a46412a0176afb88af/api/src/main/java/net/luckperms/api/context/ContextCalculator.java#L33-L43
Ah I see - well, ideally DiscordSRV should be caching this value, so the MySQL lookup isn't necessary.
While this would solve the problem, it causes another; another server might change the data in the database, which would lead to the cache being out of date, and adding redis/plugin message for this would be quite the hurdle (this is just one value that's in the database)
however, I don't think the MySQL storage was there at the time.. I think that might've been added since.
...
The one big question that remains is how to you link player accounts to LDAP accounts?
You can add some extra Infos/fields to LDAP users.
So you can set the UUID of the player.
Hey, im having a big issue with luckperms. other plugins don't get the group of player, if i "lp user (name) parent clear" and then use "/lp user (name) parent set VIP" plugins get the group of player. but when player logs out and logs in back same thing again plugins don't get the group of player. But on players first join it gets the group nicely (and then when player logs out and logs in same thing blabla). i tried other plugins to understand if problem is cuz of luckperms and it looks lik...
ok i solved it is because of other plugin named vipzero (i used to use it with groupmanager forgot to remove).
love your job btw gl :)))
Description
If a plugin subscribing to certain events calls a blocking LuckPerms API call, commands that update an online player, such as promoting on a track, will appear to succeed (and even send a message using Redis) while not writing changes to the database (or writing them extremely delayed), making it seem as if the database has suddenly gone read-only.
Reproduction steps
- Have near-zero (real) programming talent and think running a server is a good idea
- Inst...
Description
Sometimes when joining a Server, you get kicked with the message "An unexpected error occurred whilst setting up your permissions data. Please try again later." Also affects Server-Switching with waterdog. Then you'll be stuck in a world of acazia buttons.
It doesn't happens always. But very often.
Reproduction steps
- Join the server
- Read the error in the console (https://bytebin.lucko.me/4IzER2kfGX)
Expected behaviour
Dont get kicked,
Getting no...
[16:59:13] [Server thread/INFO]: [LuckPerms] Loading LuckPerms v5.2.35
[43,552s][warning][os,thread] Failed to start thread - pthread_create failed (EAGAIN) for attributes: stacksize: 1024k, guardsize: 0k, detached.
[43,553s][warning][os,thread] Failed to start thread - pthread_create failed (EAGAIN) for attributes: stacksize: 1024k, guardsize: 0k, detached.
[43,554s][warning][os,thread] Failed to start thread - pthread_create failed (EAGAIN) for attributes: stacksize: 1024k, guardsize: 0...
Looks like your server hardware just doesn't have enough thread to work with. But in any case, follow the issue template.
Description
I have never had any bad issues with luckperms, I love luckperms and I expect to be using it for a long time.
I do have one suggestion which would really help clean up my console, I believe it is the only error I keep seeing returning frequently because my players level up pretty quickly.
When someone levels up we give them a suffix with a few symbols in them declaring the level of the player (pvp related).
Giving these suffixes with symbols causes an error to be put i...
Wouldn't this be more of a bug report rather than a suggestion? I don't think your LP should be spitting errors like that.
You need to run this MySQL command in your LuckPerms database:
ALTER TABLE luckperms_messenger CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;
Assuming your table prefix is the default luckperms_ (if you didn't change it, that's what it still is)
Hey @i509VCB
I've recently been working on my own small fabric server, so now have a personal incentive to get this across the line! 😄
I've taken your branch and replicated it in the official repository, I didn't want to push any changes to your fork without asking (but I can do if you'd prefer that)
So far, I have:
- Switched over to the new Fabric networking API
- Reverted/tidied up some of the context changes. I've also made some small style changes to bring the fabric module m...
Description
When you use the promote or demote command on someone that has a group on a specific track, the expiry time (in case it is a temporary group) won't conserve and it will turn permanent.
Reproduction steps
1- Create a track including 2 groups (group "A" and group "B")
2- Apply yourself one of those groups temporarily.
3- Promote or demote yourself on that track, and the expiry time won't be conserved, turning into a permanent group.
Expected behaviour
...
Hey @lucko, I don't mind you pushing to my branch, I trust you there
Some things of interest may be this PR: https://github.com/FabricMC/fabric/pull/957 which will let you drop the mixins for player respawn (you have marked that one) and a player changing worlds for context tracking.
On changes, I believe you should also listen to ServerLoginConnectionEvents#DISCONNECT so you can expunge a player from the cache if another mod kicks the player during login.
On an official permission...
Hi,
I was trying to conect Luckperms with my MySQL db but the only thin i get ios a big fat error in my Consloe that says. Cant conect to MySQL.
I Penta Checkt the login data in my Config and oter Plugins works Perfect only Luckpers makes me Probelms.
"java.sql.SQLTransientConnectionException: luckperms-hikari - Connection is not available, request timed out after 5000ms."
i´m sorry i´m dump i solved my problem and i dont know how to close this post here :D
Web Editor
- add editing of group settings (menu is same, as when we are creating new group)
- add users search by UUID
Please open this on lucko/LuckPermsWeb
Proposed behaviour
If a parent have a specific permission which is set to false and the child wildcard where the specific permission is is set to true, the command will not work. It would be nice to add a boolean in the configuration file so this behavior could be activiated.
When there are a few commands I want to disable, I set the wildcard to true and then get rid of the specific permissions, then I add the wildcard to true in the stronger group (for example admin > moderator).
[lucko/LuckPerms] New comment on issue #2797: Boolean to let specific permissions override wildcards
Just set the specific to true/false in the child. That overrides the parent.
[lucko/LuckPerms] New comment on issue #2797: Boolean to let specific permissions override wildcards
All the rest will inherit the right way?
[lucko/LuckPerms] New comment on issue #2797: Boolean to let specific permissions override wildcards
What?
No idea what you mean.
Description
When using the command /lp group parent settrack the game (client, not server) crashes. I have tried with several different groups and the problem still exits, I'm using YMAL for the persmission files.
Reproduction steps
Run the command described above, and use tab for atleast the group. When press tab on the prefferd group, the game crashes.
Expected behaviour
I'm expecting the command to not crash when it's ran.
Environment details
- Server ...
Do you happen to edit the yaml files directly?
No i'm using the command in game, and the first time i tried the command i created the group in-game so the YAML file was never touched. The second time i tried using a file I have modified the YAML file on but it had the same result.
Can you reproduce this with just LuckPerms on the server?
Yes i get the same error when using a server with only LuckPerms installed. I have also tried to do a fresh install where i removed all LuckPerms files and i still receive the same error.
Can you run export your permission data and upload it here? Also provide the exact command you’re using.
Sure! I did an export on the server with only LuckPerms installed and all settings default. I ran the command /lp export <filename>, i hope that is what you meant!
{
"metadata": {
"generatedBy": "SwedishMonkey",
"generatedAt": "2020-12-29 16:05:20 CET"
},
"groups": {
"default": {
"nodes": []
},
"test": {
"nodes": []
}
},
"tracks": {
"mod": {
"groups": []
}
},
"users": {}
}
The game crashes when i try to r...
Interesting. I mean you don’t have any groups in the track. So that looks like an issue. But frankly that shouldn’t crash the client. I believe that is actually a bug.
Description
When joining through a proxy to a lobby, I get an error which crashes my client, this doesnt happen everytime but it happens a fair amount to be annoying. I have LuckPerms installed on both my proxy (WaterDog) and my lobby (nukkit).
Expected behaviour
Player should join with no issues.
Environment details
The client either crashes or gets stuck in a locating server glitch screen of which the player cannot get out of and has to restart the client.
- Serv...
Description
Due to the recent commit https://github.com/lucko/LuckPerms/commit/8167fbf73f99debb0cd8c1a46412a0176afb88af and the addition of the setting https://github.com/lucko/LuckPerms/blob/8167fbf73f99debb0cd8c1a46412a0176afb88af/bukkit/src/main/resources/config.yml#L473-L482 which is true by default (although it fallbacks to false if not found) and LP's nature of defaulting its own permissions to false prevent it from being used (by default) without being server operator, r...
The important part of the mapped exception is as follows:
java.lang.StringIndexOutOfBoundsException: String index out of range: -5
at java.lang.String.substring(String.java:1955)
at net.minecraft.client.gui.components.CommandSuggestions.formatText(SourceFile:315) (Yarn: net.minecraft.client.gui.screen.CommandSuggestor.highlight)
at net.minecraft.client.gui.components.CommandSuggestions.formatChat(SourceFile:280) (Yarn: net.minecraft.client.gui.screen.CommandSuggestor.pr...
Description
with any of my ranks on my server, i give them permissions, and i give myself the rank, i deop my self, and i cant do any commands
Reproduction steps
- Open the config.yml file and set example to true.
- Restart the server
- Run /lp user example permission set x from the console
- See error
Expected behaviour
Environment details
- Server type/version:
ExampleSpigotrunning version1.12.2build??? - LuckPerms version: `...
Follow the issue template...
Description
My plugin PromotionEssentials works with every other permissions plugin for removing and adding ranks via Vault's API. However, LuckPerms seems to ignore Vaults API for removing the parent rank / other ranks and then applying a new one.
For example, this would remove all other groups and then add a new group for a plugin such as GroupManager or Pex when using Vaults Permission service:
`
// Get permissions provider
Permission permissions = p...
Description
Using auto-generated worlds (Worlds get UUID-alike names) I cannot give perms using world=(world name) because the name is too long.
Reproduction steps
- Have a world with long name (Such as mine being sland_ad9e0a4c-897c-4d13-b224-1edf2dca8d16_normal)
- Try adding a specific permission using world=world=island_ad9e0a4c-897c-4d13-b224-1edf2dca8d16_normal
Expected behaviour
A permission to apply no matter the world name length
Environment ...
Description
Whilst using UserLoadEvent does not trigger on Player Join or when the Plugin gets Reloaded.
Main Class:
public void onEnable(){
new LuckPermsListener(this, LuckPermsProvider.get());
}
Listener Class:
public class LuckPermsListener {
private final Main main;
public LuckPermsListener(Main main, LuckPerms api){
this.main = main;
Bukkit.broadcastMessage("1");
EventBus bus = api.getEventBus();
bus....
I cannot reproduce, it's working fine for me.
I've added a simple demo to the cookbook plugin to confirm too: https://github.com/LuckPerms/api-cookbook/commit/b1804a934371776fe6720253976a0e2021deb1a0
[18:52:16 INFO]: Done (4.211s)! For help, type "help"
[18:52:16 INFO]: Timings Reset
[18:52:33 INFO]: [LuckPermsCookbook] UserLoadEvent fired! - c1d60c50-70b5-4722-8057-87767557e50d
[18:52:33 INFO]: UUID of player Luck is c1d60c50-70b5-4722-8057-87767557e50d
[18:52:33 INFO]: Luck j...
Interesting bug! Thanks @Proximyst for the detailed analysis, you saved me a lot of time attempting to do the same 😅
The issue seems to be that arguments in the same parse tree need to have unique names - hence the reason why the crash happens with /lp group .... and not /lp user ...
The slimmed down tree looks like this:
luckperms {
user {
user brigadier:string single_word {
parent {
settrack {
track brigadier:string single_word {
...
commands-allow-op defaults to true, so it should still work fine?
I've just tested & confirmed it does indeed still work.
Of course, if the user chooses to set commands-allow-op to false it won't - but that's the nature of that option.
Yeah, it should work fine if one is op (which may be the case when first setting everything up), but the wildcard itself no longer "works". Besides, not all platforms allow for a server operator, e.g. Sponge disables it or BungeeCord in which there is no server operator.
Thanks for reporting :)
Btw, it seems like for some reason either the join event is being called twice, or Player instances are being reused. That would suggest to me there is some sort of bug in either Nukkit, Waterdog or another plugin integration - might be worth looking into.
No, I'm saying it does still just work.
On a completely fresh server, you can grant luckperms.* in the console without opping to give access to all LP commands.
The potential issue doesn't apply to Sponge or BungeeCord because LP doesn't mark the permissions as explicitly false by default on those platforms.
Thanks for the detailed report.
Yes - it's not a good idea to make calls to loadUser within a NodeMutateEvent, because loadUser indirectly causes more NodeMutateEvents... so you end up effectively with a stack overflow that will never end (because the result gets spawned on new threads).
The same would happen (more obviously) for example if you made a call to loadGroup in a GroupLoadEvent listener.
Thing is though, there's really no reason to make a call to loadUser within th...
It varies, but usually at least 1000 are available - likelihood is that something is using lots of them up.
However, that error is unrelated to the LP error message. That is fixed by updating to a newer version: https://luckperms.net/download
[lucko/LuckPerms] New comment on issue #2797: Boolean to let specific permissions override wildcards
This is supported already, see the link above :)
I'm not sure a flag is necessary - but I've switched it so the expiry time is preserved :)
LuckPerms aims to support Vault fully - the notion that I would purposely implement it badly in order to to encourage usage of the native LP API is pretty crazy...
Anyway, I suspect the issue is being caused by an internal requirement in LP that all users must have at least one group. If a user is left in a state where they have no groups, they are automatically added back to the default group.
Since each Vault method call is treated as a distinct operation, when you clear all groups, L...
That's a pretty long world name! But, it should still be ok - the max length is 64 characters.
(or it might be shorter if you started using / created your LP database a while ago)
You might need to manually increase the column limit in your MySQL database, should be relatively easy to do with phpmyadmin or something like that.
Failing that, might just be worth trying to generate shorter world names? :/
Good evening, I have been experiencing the underlying problem for some time now where the server crashes completely without even restarting with the loop.
Reading some online guides and from the same error message I tried to lower the MaxLifeTime over and over again the connection-timeout but nothing, how can I do to solve?
Pastebin with log here:
https://pastebin.com/kUPXkHpp
Can you try switching to mysql storage instead of mariadb to see if that resolves the issue.
Pretty sure that wouldn't work as if you still remove all groups with that it still adds them back to the default group.
I'd propose adding the group first and then removing all others.
Yes, I try to let you know by tomorrow because it usually crashes after a few hours
Thanks 👍
Uuh.. I must have missed something when testing? It works fine :thinking: well, closing the issue then.
Thanks. I didn't mean purposefully add it badly. Just didn't know if you implemented only the parts needed to hook with Vault and then expected people to use the API due to a change in how you do permissions or something.
Thank you lucko
Have a hppy new year!
Description
Having the elements that let you define a track or a group on plural instead of singular, would make the meta formatting much more manipulable and comfortable to edit at your liking.
Example:
highest_on_track_ would turn into highest_on_tracks_
So instead of only being able to put 1 track, you would be able to set more than 1.
highest_on_tracks_staff,donors
Same with elements that include ``. So for example highest_from_group_ would turn into `highest_from_gro...
Goodmorning how are you?
Unfortunately apparently the problem was not that, now it gives me this error:
Thanks so much for your help
PS: but this time the server hasn't crashed and if I run in game / lp it seems to work ... mhh
receivedMessages will keep on growing, even it's only a UUID.
On high production proxies with uptimes of a few weeks, this will all count up to 100+ MB's.
Thanks for bringing this to my attention :)
I want to try to keep the system from becoming any more complex.. so unlikely to implement this as-is. I do have a suggestion for you though:
highest_from_groups_... can be replicated by just creating a throwaway track (i.e. one you're not going to use for promotion) with the groups you want.
Likewise with highest_on_tracks_..., just create another track which contains a union of the tracks you want to query for.
Thanks for the idea, but probably not something that is in-scope fo...
Okay I think I understand the problem but I don't know how to solve it, that is after 8 hours of inactivity I think that mysql disconnects some connections like that of LuckPerms and also LiteBans, in fact from the logs putting the connection in MySQL instead of MariaDB now this "The last packet successfully received from the server was 54,318,428 milliseconds ago. The last packet sent successfully to the server was 54,318,448 milliseconds ago. is longer than the server configured value of 'w...
Description
This report is in follow up to Issues #2764 & #2751
Reproduction steps
Assign "temporary" permission to user
Wait indefinite amount of time
Assign permanent permissions/groups to that user
Wait indefinite amount of time
"Temporary" permission expires (or is removed via command) and any perms added after that "temporary" node are removed
NOTE: This does NOT occur all the time, and is very rare
Expected behaviour
User does not lose permanent gro...
There's no need to bump, I work on suggestions as and when I have time.
This is a complex problem with a potentially large impact on users setups if implemented incorrectly. It is also not something I consider to be urgent, the current system (whilst I admit is not perfect) is at least functional at the moment (and has been for the past 3/4 years...)
As well as the complexity of the code change, it also has knock-on effects on documentation and other behaviours (e.g. the include-global ...
The limit has been increased and the way it applies has been altered.
This should no longer be an issue 👍
https://github.com/lucko/LuckPerms/commit/d83559b94946138c52268c3c4c4d990499e10186
I'm happy that this branch is now in a workable / maintainable state. I think it therefore makes sense to merge it into master so Jenkins can start creating jars for people to download and test with.
Thank you so much for your work on this so far @i509VCB!
I look forward to being able to implement further improvements as & when fabric-api additions land. 😃
Would this change not make the storage incompatible with any existing data saved in a different format?
Thank you for the PR!
A question though:
Would this change not make the storage incompatible with any existing data saved in a different format?
Yes, this will break existing ids. It is not possible to transform a uuidv3 to a uuidv4 but an id saved in v3 is unusable since it does not correspond to mojang user's id.
It would be necessary to ensure that version 4 is used only if no data has yet been recorded. Another alternative would be to add an option in the configuration f...
I'm not sure about that - I'm pretty sure the current serialization is working ok - perhaps it would be possible to automatically migrate them to a new format
There is the stored _id with uuid saved as v3

and there is the stored _id with uuid saved as v4

There is my real uuid from mojang:

As you can see, th...
Description
LuckPerms fabric null pointers in offline mode upon login
[ForkJoinPool-4-worker-53/ERROR] (luckperms) Exception occurred whilst loading data for null - [My Player's Username]
java.lang.NullPointerException: null
at java.util.Objects.requireNonNull(Objects.java:221) ~[?:?]
at me.lucko.luckperms.lib.caffeine.cache.BoundedLocalCache.put(BoundedLocalCache.java:1981) ~[?:?]
at me.lucko.luckperms.lib.caffeine.cache.BoundedLocalCache.put(Bounded...
Investigation:
Issue occurs here:
https://github.com/lucko/LuckPerms/blob/master/fabric/src/main/java/me/lucko/luckperms/fabric/listeners/FabricConnectionListener.java#L92
My educated guess is the game profile on ServerLoginNetworkHandler is null for some reason?
However I don't see a typical way this would end up as null.
The limit has been increased and the way it applies has been altered.
This should no longer be an issue 👍
d83559b
Thank you very much!
Awesome, this will make it so much easier to add permissions to Fabric servers :)
Ah, ok, yeah I think I've ran into this before.
The GameProfile isn't null but their UUID is
Description
People with access to the web editor should be able to remove users from there like you can with groups
Proposed behavior
an X next to a players username that when you click it it will remove all data with that player
its already there, ensure you are on the latest version of lp. https://luckperms.net/download

I thought I was updated. ._. sorry about wasting your time
Description
I give someone the persimmon node minecraft.command.seed
However it does not work and says unknown command, (works with op)
Aswell as on the web editor and in game the default Minecraft commands do not auto fill.
Reproduction steps
- do
/lp editororlp editorfrom console - select a user / group
- start typing in minecraft
- see it does not auto fill
- give someone a perm like
minecraft.command.seed - make sure you do not have op or...
<img width="644" alt="Screen Shot 2021-01-05 at 10 58 28 PM" src="https://user-images.githubusercontent.com/64851720/103727557-87b84580-4fa9-11eb-845b-2005bcde9766.png">
Note it is only showing up here due to me typing it in before
I am not certain that Fabric has inbuilt permissions for vanilla actions at this point - the examples you give, like minecraft.command.seed are built into Bukkit as permission nodes to control those actions specifically and you can find them
at https://bukkit.gamepedia.com/CraftBukkit_Commands
As LP does indeed work on fabric for things that have permissions, this is likely something that should be raised with the Fabric team. LP cannot control what perms are called or what they do - ...
I can in fact confirm that fabric does not have permissions for those actions at all - it only recently got a permissions API and nothing has, as of yet, been added in terms of permissions for vanilla actions
Description
When luckperms loaded it throws a NoSuchMethodError for com.google.common.cache.CacheBuilder.build
Reproduction steps
- idk why
Expected behaviour
Idk it not error on start
Environment details
- Server type/version:
Spigotrunning version1.7.10git-Spigot-1.7.9-R0.2-208-ge0f2e95??? - LuckPerms version:
v5.2.76 (Legacy)
https://gist.github.com/Moose1301/095098e7ec0d5b93a455a287233f0918
Any other relevant details
...
LuckPerms legacy will only work on 1.7.10, you'll need to upgrade from 1.7.9 to 1.7.10
it is a 1.7.10 server it even tho it says "git-Spigot-1.7.9-R0.2-208-ge0f2e95"
How do you know, sing all evidence you send is pointing to a 1.7.9 server version. Can you send your full startup log?
Can you download this version then restart your server?
Try deleting the LuckPerms/libs/ folder then restarting your server.
Try deleting the
LuckPerms/libs/folder then restarting your server.
That fixed it ty
Description
Causes watchdog crashes with blocklogger on fabric
Reproduction steps
Start a fabric server with luckperms, fabric API and blocklogger.
Currently unsure of what exactly causes the crash, but I have so far had 4 of these crashes reported since users added luckperms to their servers
Expected behaviour
Blocklogger does not behave in a way that a watchdog could occur, even if there is a storage slowdown. I believe this is a conflict with luckperms
...
Since I have removed luckperms from my server I have not had any crashes anymore
I am aware luckperms uses some form of database. As the stacktrace says, there is an issue executing SQLite
PreparedStatements.
The stacktrace says specifically that the issue is from executing tech.dttp.block.logger PreparedStatements.
java.lang.Error: Watchdog
at org.sqlite.core.NativeDB.step(Native Method)
at org.sqlite.core.DB.execute(DB.java:849)
at org.sqlite.jdbc3.JDBC3PreparedStatement.execute(JDBC3PreparedStatement.java:54)
at tech.dttp.block.logger.save.sq...
[lucko/LuckPerms] New comment on issue #2797: Boolean to let specific permissions override wildcards
On Discord, I was told that if there is a specific right that is forbidden for a group, it won't be authorized in the child group, even if allow the wildcard in the child group.
The way I use permission is to add the whole wildcare and set to false the couple permissions i don't want in the group. Maybe it's the wrong way to do it?
Description
Spent last 3 days setting perms on a server. Needed to make it so lower staff cannot demote higher staff
Support in discord told me to set require-sender-group-membership-to-modify to true
set this. Restarted server did /lp editor. It worked fine
Noticed i had no permission to do anything with luckperms even though i was OP and had the Permission* set in my username
also had basically no perms for anything.
Did /lp editor. Only 2 of the Groups out of 10 were there...
Description
Fabric server on bungeecord network won't work w/ luckperms...
Reproduction steps
- Create a new fabric server w/ luckyperms & fabricproxy
- Connect the server to a bungeecord network
- Try to join
- See error
Expected behaviour
I want to login : )
Environment details
- Server type/version:
Fabricrunning version1.16.4buildv0.6.1.51 - LuckPerms version:
v5.2.77 - Fabric API version:
v0.28.3 - FabricProxy version...
This is an issue with FabricProxy overriding the Fabric networking API which LP uses.
It seems like FabricProxy v1.4.5 has been released which may resolve the issue :)
I connected to the mysql database and it crashes errors.
luckperms bukkit
server version: 1.16.4
lp bulkupdate users delete ?
Description
I honestly have no idea why it does this.
Reproduction steps
/killyourself (with or without op)- Type
/perms - Check Console
Expected behaviour
Log spam.
Environment details
Minecraft Environment: Floader 0.10.8 + Fabric + Jellysuite
Operating System: Ubuntu 18.04 x64
https://gist.github.com/TehcJS/bbd1375e911b80e12db1e267d263f1c0
Any other relevant details
It also happens when it tries to give you sugge...
Description
Console is being spammed with an error about "An exception was thrown by me.lucko.extracontexts.calculators.WorldGuardFlagCalculator whilst calculating the context of subject CraftPlayer{name=srnyx}"
Reproduction steps
- Enable MySQL for LuckPerms
- Add WorldGuard and WorldGuardExtraFlags
- Join the server
- See error
Expected behaviour
No error
Environment details
- Server type/version:
Paper-Spigot-400running version `1.16...
This seems like the same issue as ExtraContexts issues 29, 32, and 34. Are you using the WorldGuardExtraFlags command-on-entry or command-on-exit flags? I know they can cause issues, but don't know why.
This seems like the same issue as ExtraContexts issues 29, 32, and 34. Are you using the WorldGuardExtraFlags
command-on-entryorcommand-on-exitflags? I know they can cause issues, but don't know why.EDIT: I haven't tested every flag comprehensively, so other flags may cause the same error.
Not as far as I'm aware
Description
Upon executing the /stop command, the server does not shut down 100%. LuckPerms seems to cause it to hang?
Reproduction steps
Install LuckPerms and use /stop command /shrug
Expected behaviour
For the server to stop completely and restart
Environment details
- Server type/version:
Tuinityrunning version1.16.4build8954b61 - LuckPerms version:
v5.2.76
Shutdown log: https://gist.github.com/vx888/91dbae6d951a0a17db9541de9...
It breaks if a player has an expiration time of over 3 weeks. once it hits 25 days and above it will start over from 60 hours for some reason.
Meaning at 24 days it says for example: 23d 12h 34m 13s
But as soon as it hits 25 days and over it starts at 60h.
its really odd.
Description
ViaVersion seems to be incompatible with LuckPerms on Sponge. The error is here.
I've narrowed this down to this line in ViaFacet of the LuckPerms adventure platform. The issue appears to stem from LuckPerms loading the class before ViaVersion. The class loaded has a static declaration, [and one of the ...
Thanks for the report - as you noted, this issue is actually coming from one of the libraries LP uses, adventure-platform.
Would you mind copying your report to the issue tracker here: https://github.com/KyoriPowered/adventure-platform/issues :)
I'm confused.. you say it hangs but the timestamps seem to show that it wasn't waiting at all?
[23:06:30] [Server thread/INFO]: [LuckPerms] Disabling LuckPerms v5.2.76
[23:06:30] [Server thread/INFO]: [LuckPerms] Starting shutdown process...
[23:06:30] [Server thread/INFO]: [LuckPerms] Closing storage...
HANGS HERE ^
[23:06:30] [Server thread/INFO]: [LuckPerms] Goodbye! <-- CTRL + C
Ideally, I need a thread stack dump taken while it is hanging. You can use the jps ...
Interesting that the previous change has made this worse... I'm not sure what conclusion to draw from that.
Suggested Fix
Don't ever write back deletion to MySQL table. The database must always be the ultimate source of known good data.
If a plugin / api call or command requests the removal of a permission then remove that permission, There should never be a situation when the databases version should be considered invalid as all permissions are written out accurately whe...
You can find details about how to fix this issue on our wiki :)
Thanks for the extra info, I also did a bit of reading about the various UUID types Mongo uses.
A seamless transition is really important here: ideally, we assume that users might not even update all of their servers at the same time, so older versions of LP should be able to continue to function correctly.
So yes, a seamless migration from "current" to "recommended" UUID encoding is important. Otherwise, I'm inclined to just leave things as they are - it does seem to work somewhat ok a...
I will set up enhanced logging and advise shortly what queries are causing this. Please give us a few days.
Hope it's going well. Any updates?
Add possibility to modify/remove meta through bulkupdate?
Example: /lp bulkupdate users delete "meta == 14_12"
Add possibility to modify/remove
metathrough bulkupdate?
Example:/lp bulkupdate users delete "meta == 14_12"
That is possible with the current setup, meta nodes are structured like so meta.<key>.<value>
I can't seem to find documentation for whether or not this is an option, but I'm using LP to create a guild system. I have a track called "guild" with groups "Guild_member," "Guild_builder," and "Guild_leader." I want to give the group "Guild_leader" the permission to promote users only along the "guild" track. I have argument based command permissions enabled, but I can't seem to get the perm to show up for my test subject unless he has permission to promote along every track.
@Fernthedev no updates, and the Floodgate rewrite has been making progress but alas it is not here quite yet.
Hello. Help with an error on the site, after entering / lp editor, I go through the site and write
"LuckPerms
Web Permissions Editor
There was an error loading the data. Either the URL was copied wrong or the session has expired.
Please generate another editor session with / lp editor. "
Screenshot - https://imgur.com/a/k9NtILb
This could be due to a variety of reasons:
- your browser has an extension blocking the connection to bytebin (where the data is stored and read from). Try using another browser or private browsing mode
- your computer could have an anti-virus preventing the connection to bytebin. Disable your antivirus or try and use another device (another PC or mobile) to load the page
- your internet connection (ISP) could be blocking the connection to bytebin. Try using another wifi network if possi...
@kolia22871 we just made a change to the website that may improve the issue, can you please try again and see if it works?
https://luckperms.net/wiki/Argument-based-command-permissions
You explained too much in your reply. Try being less helpful next time. Still no documentation on whether Luckperms.user.promote.track is a permission node, or what argument based permissions have to do with that. Good try though.
Everyone loves a snarky reply.
Enable the option in the config, then use verbose mode to figure out the rest.
Everyone loves a snarky reply.
Enable the option in the config, then use verbose mode to figure out the rest.
If somebody is going to post a link with no explanation, they might as well not post at all. Why do developers always reply with as little explanation as possible? Are you actually trying to help? I'll try your suggestion, but my response to BrainStone is justified.
tbf, the contents in the link does explain.


And the if you are unsure if the exact permission, you can also use verbose to check. https://luckperms.net/wiki/Verbose
That’s the thing about documentation. It requires no further explanation. As it contains all the info you need.
But it’ll be my pleasure no longer helping you out ☺️
Ben where did you find that section in the documentation? Brain, posting a link to a wiki requires explanation on where in the massive article to look. Also you never helped to begin with.
The wiki is very well detailed, that article as a whole explains argument based permissions and if you were to take your time and read in detail you would know that section is towards the bottom
Ben where did you find that section in the documentation?
In the link brainstone sent.
Also you never helped to begin with.
Not sure why you are so closed-minded to ppl helping you, but we are all just chipping in to help. Hope you understand. 😄
Well if around two pages of text is too much to read then you shouldn’t be running a server. Reading documentation is an essential skill for successfully running a server on your own. And it’s quite impressive that you never bothered even scrolling down. Else you would’ve seen it.
Now if you’ve read the documentation and it you don’t understand something that is fine. Ask for clarification on those parts. But don’t demand for people to regurgitate perfectly fine documentation into bite si...
My apologies on being so hasty and not scrolling down. I don't mean to be rude. It is possible, however, to help without being vague at first, and then scornful. Moreover, the article states that it pertains only to spigot and sponge, which I am not using. The issue is still unresolved. For instance, the node luckperms.user.promote.<track>.* doesnt seem to exist. I cannot use the wildcard to invoke all groups on a track.
That’s the thing. There’s nothing meaningful for me to add to the link. As it contains all the info you need.
And I’m not sure where you get the idea from that it only works on Spigot and Sponge. This works for all LP types.
And lastly make sure you enable the setting that’s mentioned in the very first sentence.
he article states that it pertains only to spigot and sponge, which I am not using.
You didn't fill in the issue template so we can only assume you use the common server types. Tho luckperms permission nodes don't differ between server types so I don't see an issue there.
For instance, the node luckperms.user.promote..* doesnt seem to exist.
How do you know it "Doesnt exist", also the permission node its luckperms.user.promote.* not 2 .. Then also note that there is 5 permi...
Well if you read my original post, you'll see that that setting is in fact enabled. Also, the article SAYS "for sponge and spigot." Also, it would more appropriate to ask "is that setting correct?" or "did you try this command." That is what beig a helpful person looks like. The double dot was a typo on the post. The node is in red text when I type it.
The node is in red text when I type it.
That is purely client side and has no functional implications, you can wrap your permission in double quotations "like.so.*" and it will be yellow fancy.
If you want people to provide help without having to assume things you should follow the issue template.
There were no details to assume, as I cleared up those missing details, however I was unaware of the issue template. I'll look at that next time.
The node is in red text when I type it.
Red doesn't mean its invalid, have you actually tried setting all the relevant permission node.
the article SAYS "for sponge and spigot."
At least say what server type you are using then
Well if you read my original post, you'll see that that setting is in fact enabled.
Im just asking you to check, didn't say you definitely didn't enable it yet.
Also, it would more appropriate to ask "is that setting correct?" or ...
Thank you Ben. You have been very patient and understanding. I'll come back to this problem when there are players to test it out. With the knowledge of the autofill suggestion status not being relevant, I should be able to get it taken care of.
@Turbotailz Doesn't work anyway
Did you try any of the options I mentioned before?
@Turbotailz I'll try another internet right now
@Turbotailz I tried from my phone and from another internet
Could you send an editor link?
What version of LP are you running?
Description
when you do /lp import, and it tells you what the command does and how to use it, it states that --replace "replace existing data instead of merging", which (at least to me) implies that it will replace all permissions data
Proposed behaviour
there are a few options here
- make the description more clear on what it is
- rename the current option and add a new one that matches the current description
- (better for compatibility) keep the current option as is (...
This is what I did which solves the problem without having to repeat yourself with different groups.
/lp bulkupdate users update permission group.default "permission ~~ group.%"
This will reset everyone no matter the group back to the default group.
Alright, so I've used verbose mode to see what nodes are being checked when the command "/lp user name promote track" is run. I have the perms luckperms.uers.promote.modify.others, luckperms.user.promote.track.* set to true, which is all that the wiki says is needed. However, the output of the verbose command shows about 30 perms being checked, all of which seem unrelated to the command I'm trying to run, ones about viewing, clearing users, parents, and permissions. My subject does now get au...
Can you set the actual screenshot/links of permissions you set and verbose output? Also is your track named track?
The names in the commands and nodes that I send here are placeholders. I don't see an option to attach an image to my post.

Try add luckperms.user.promote.usecontext.global perm node as well. Also for verbose you can do a web upload with lp verbose record, then after doing the command lp verbose upload
Ben, it looks like that one node worked.
Hey!
Just testing this out and noticed a minor detail - it seems that the editor option doesn't display when trying to auto-tab the command. If I manually type the command the link still generates though!
Currently running version 5.2.84
Thanks for reporting, this should be fixed :)
I suspect this is probably the issue you were experiencing: 2a44572fb2dc7a74307a1b90c48958978245b4c7
Should now be fixed in the latest dev version.
Description
Ability to Change the permission before checking it
Proposed behaviour
It would be useful for some developers to be able to change the permission before checking it. This way a permit containing for example quantities would be easier to develop:
token.
A plugin can request to check the number of tokens needed for a certain action and with this method, it would be super simple to go and change the permission in order to check the number of tokens in this ca...
Use transitive permissions.
Those are non persistent permissions that take precedence over normal permissions. Intended for exactly that. A permission check event would completely kill performance.
A token storage system doesn't really fit well with permission checks. Permission checks return a boolean (true/false) value - not ints, strings or anything else.
If anything, using MetaNodes would be better, however, for that to work well, LuckPerms would need to be the source of truth for token balances. It wouldn't make sense to have another plugin be able to alter the lookup results, based on some other stored value.
If another system needs to be the source of truth on token balan...
I am aware that it sucks to use permissions to manage this but it is the only way to integrate it with another plugin (not made by me and therefore I cannot change in a short time)
Fair enough, but I'm afraid it's not something we want to encourage or accommodate in LuckPerms itself.
Description
When using any of the log history commands, an error will occur in console but will also complete it's expected task
Reproduction steps
I feel this might be specific to me only but:
- Do any of these 3 commands - /lp log userhistory/trackhistory/grouphistory [user/track/group]
Expected behaviour
The log to appear without generating an error in console
Environment details
Server version: git-Tuinity-"4743c34" (MC: 1.16.4)
LuckPerms version: 5.2...
Description
My /lp editor is very slow & I often get warnings related to the database in my console.
Reproduction steps
Actually, I am not sure why it happens, so I'll show the console log instead.
Expected behaviour
It gives me editor link faster & doesnt throw warnings in console.
Environment details
- Server type/version:
Waterfall / paperspigot (bungee network with 1 waterfall server & 2 paperspigot servers all running luckpermsrunning version...
I have connected LuckPerms to a MySql, and at first it connected fine, but when I reboot in the vps, it gives me an error.
MySql is started, i can login and manage it.
Error: https://pastebin.com/ERiUeFR9
Config: https://pastebin.com/SThjjNen
Database: https://gyazo.com/43adf9dbf233d02463171ee117ad1a30
Btw, I've added a workaround in LP for until this can be fixed in adventure. Try again using the latest version
Hi, this is in fact breaking to other plugins yes.
After the fifth or so user came into the Citizens channel to ask why they couldn't use Citizens anymore, I looked into it and found this breaking change was at fault.
While I do think it fair to change Citizens permissions to default: op and don't find the commit inherently unreasonably, I must very strongly protest the issue post here...
"Anti-permissions" do NOT EVER EVER EVER SUPER NO NOT EVER belong in the permissions sy...
I only just noticed that the default for this "fix for anti permissions" is true by default. maybe that needs to be changed? everyone setting this setting to "false" will experience the old behaviour and I think it is fair to say that the anti-permission logic is deviating from the norm :)
Hello, it's normal.
It removes the connection to DB when you are restarting your server.
You have to connect it with apache2/nginx (depending what you have).
Permissions are PERMISSIONS
NEVER mix permissions and user settings
I agree with you on this, and think that it should just be easy to just grant * to give users access to everything permission related.
However, the reality of the situation is that plugin authors are using the system for "anti-permissions", and that's something that LuckPerms should therefore aim to support in my opinion.
The idea behind this change was exactly that - to allow plugin authors to mark in t...
i get this error when i try to connect it to mysq
l[10:54:45 INFO]: [LuckPerms] Enabling LuckPerms v5.2.90
[10:54:45 INFO]: __
[10:54:45 INFO]: | |) LuckPerms v5.2.90
[10:54:45 INFO]: |_ | Running on Bukkit - CraftBukkit
[10:54:45 INFO]:
[10:54:45 INFO]: [LuckPerms] Loading configuration...
[10:54:45 INFO]: [LuckPerms] Loading storage provider... [MYSQL]
[10:54:45 WARN]: [Server thread] INFO me.lucko.luckperms.lib.hikari.HikariDataSource - luckperms-hika...
I fixed that with setting weight to all
donationgroups to1.
how did you fix the problem. plz help me.
Hello, your MySQL server is active?
Yes
You didn't defined password in config:
password: 'passwordhere'
Description
When joining a fabric server on a Bungeecord network user data doesn't load but also doesn't have any errors
Reproduction steps
- Have a bungeecord network with at least 1 fabric server
- have everything configured to run on a MySQL database.
- log into server and connect to the fabric world
Environment details
- Server type/version:
Spigotrunning version1.8.8 - LuckPerms version:
v5.2.9
[17:46:52 WARN]: [NametagEdit] Loaded class net.luckperms.api.LuckPermsProvider from LuckPerms v5.2.76 which is not a depend, softdepend or loadbefore of this plugin.
- Follow the issue template, it's there for a reason.
- NTE issue, not LP.
My users can do /godmode which is part of my plugin and I can not disable it with luckperms. Please help and thank you.
Description
Verbose logging on fabric stops working completely all of a sudden after some arbitrary amount of time, in the order of seconds to minutes.
Reproduction steps
- Install LP on fabric and enable verbose.
- Wait for some arbitrary amount of time and do things that require permissions, no results yield.
Expected behaviour
Well it should keep reporting :full_moon_with_face:
Environment details
- Server type/version:
fabric@0.29.4+1.16...
I think the core issue of that whole ordeal is that what permissions default to true or false are not visible to the user at all!
Mean they are tapping around in the dark with no chance of figuring out why that specific set of permissions is false even though they believe they should have those permissions. If there was a way to visualize the default permissions this whole issue should become a non-issue as then people can actually find the root cause.
I have enabled bungee on all my sponge and spigot servers and enabled IP forwarding
`WARNING A permission check was made for player UploadKingYT - 56855605-4a13-4fc6-9bfb-07f777ef08a6, but LuckPerms does not have any permissions data loaded for them. Perhaps their UUID has been altered since login?
20.01 09:07:20 [Server] INFO java.lang.Exception
20.01 09:07:20 [Server] INFO at me.lucko.luckperms.bungee.listeners.BungeePermissionCheckListener.onPlayerPermissionCheck(BungeePermissionCheck...
Description
I am trying to insert "meta.rankintab.&c[[color=#FF4400]&lL[color=#FF5F01]&lE[color=#FF7A02]&lA[color=#FF9603]&lD[color=#FFB104]&l-[color=#FFCD05]&lA[color=#FFB104]&lD[color=#FF9603]&lM[color=#FF7A02]&lI[color=#FF5F01]&lN&c]&f &r" as a permission but am hit with a Data too long for column 'permission' at row 1 error in the logs.
Reproduction steps
Command `/perm group staff4 permission set "meta.rankintab.&c[[color=#FF4400]&lL[color=#FF5F01]&lE[color=#FF7A02]&...
The default length limit for permissions is 200 characters.
If you want to insert anything longer than that, then you'll need to go into your DB and increase the length of the column. :)
Seems to be an incompatibility somewhere, the pre-login event listener doesn't seem to be being triggered.
Please make sure you are using an up-to-date version of Fabric API and FabricProxy.
In the future, please create issues using one of the available templates: https://github.com/lucko/LuckPerms/issues/new/choose
It makes things much easier, and ensures we have all the information needed.
I suspect the issue is being caused by one of your other plugins altering player UUIDs on login, but since you only included a partial log I can't say for sure.
There's something wrong with your MySQL server, or you've configured it incorrectly.
https://luckperms.net/wiki/Storage-system-errors
That's all I can tell you, sorry.
"Connection refused" error
Could be wrong password, bad firewall config, bad MySQL server config....
https://luckperms.net/wiki/Storage-system-errors
but nothing to do with LuckPerms. :)
You have some malformed data in your actions.txt file.
Easiest way to solve it is probably to just delete it and allow LP to regenerate it.
This issue belongs on the ExtraContexts repo
I think it's already pretty clear - when the flag is provided it does replace all data for the groups/users/etc being imported.
If you want to have a completely clean slate then you need to delete the storage first then import after. :)
Thanks for reporting :)
Description
Only getting back version information When trying to execute any luckperms command in the console (Fabric)
Reproduction steps
- Install the Fabric Loader, API and Luckperms.
- Start the Server
- Try to give a User
luckperms.*by executinglp user Paul_42812 permission set luckperms.* truein the Console. - Get
[LP] Running LuckPerms v5.2.91.back.
Expected behaviour
Permissions are not updated and [LP] Running LuckPerms v5.2.91. is ret...
After further testing with Latest release on all proxies, and backend servers we have seen no reoccurrence in 7 days.
Sweet, glad to hear that! Thanks for getting back to me :)
Description
When I start my server I get this error:
java.util.concurrent.CompletionException: java.sql.SQLSyntaxErrorException: Table 'permscv.luckperms_groups' doesn't exist
I have the latest version of LP and I have tried making new of everything but it doesn't work. I have figured out that its not actually creating the table in the DataBase so it isn't finding it.
Reproduction steps
- Put your database credits in config.yml
- Restart the server
- See error
...
Description
All in game log notifications are showing up as blank lines, and when a permission edit is made the line will start with either a plus or a minus depending on if a permission was added or removed but the rest of the line is completely blank. The notifcations do however show up in the console normally
Reproduction steps
- Use /lp applyedits or any /lp command that edits permissions or groups or have anyone else use a command that you should be notified about...
What client are you using?
What client are you using?
Well that solves it, I feel quite stupid now. Thanks for the help!
Try stopping your server, then dropping all LP tables, then starting it again.
If that doesn't fix it, then it's most likely an issue with your database server. The first thing I would check is that the MySQL user has the right privileges assigned to create tables, etc.
When I attempt to upload a json abckup i did of my previous luckperms config, it says it is unable to fidn the file. The minecraft output seems to shorten the location fo the directory it is searching against, but I have made sure that this file is available in /server/luckperms and /server/config/luckperms
The command I am using is
lp import file.json
lp import file.json [--upload]
lp import
lp import [--upload]
The issue it seems is that it cannot fidn the file itself. I am using S...
I believe the output should be a json.gz file, that can then be imported with /lp import filename (providing it's in the LuckPerms plugin folder, plugins/LuckPerms)
It was - Fefo on discord ended up helping me. I was using the gz extension as well, but it turned out, the import method was case sensitive, and I had an intial capped letter. Fefo resolved this for me. Thank you very much for your insanely fast response, and thank you for having such an amazing community.
Description
I have recently set up my server with bungee cord and now when i do the command /lp then a space in my main server it kicks me to my hub
Expected behaviour
I expected to do /lp editor but i am not able to do a space after the command due to the server kicking me to the hub
Environment details
- Server type/version:
PaperMcrunning version1.16.4 + with viaversionbuild??? - LuckPerms version:
Bukkit
Any other relevant details
...
There was such a problem. After death-the player loses all the roles, he can not write to the chat, etc. After the relog - it returns all the rights. What to do? Server version 1.16.4, Mohist core, LuckPerms version 5.2.92
This doesn't seem like a LuckPerms issue, especially if it's happening with other plugins' commands.
I also met this issue, do others have a way to solve it? Thanks a lot
This is an issue with Mohist not copying permissions when a player respawns - nothing to do with LuckPerms.
I would agree that this likely isn't a luckperms issue, however I would suggest looking at the console of the server you get kicked from to see if its kicking you for spam. That can happen on pre-1.13 servers when using viaversion or protocolsupport as those plugins translate chat tab events to an event that counts as spam, although i am not sure why it would be happening on 1.16.4. I would also suggest updating to 1.16.5 (1.16.4 and 1.16.5 use the same protocol version btw, and are 100% comp...
Hi, thanks for the PR - I appreciate it!
However, I'm not entirely sure how this is an improvement? The 'mutability' wasn't causing a problem before, and this change makes the class more complex by skipping out on the automatic error handling provided by the static method used previously.
Furthermore, when reloading, we kinda want to discard the existing YamlConfiguration & create a new one instead of merging into the existing!
Impossible for anyone to know.
Did you read the error?
It tells you to check console for errors.
So, check the console for errors and upload the whole logs/latest.log to pastebin
If you are a server admin, please check the console for any errors
You should really learn to read console logs
Description
When I do lp editor (in game or in console) it says "[LP] Preparing a new editor session, please wait...
[08:15:05 INFO]: [LP] Click the link below to open the editor:" and no link shows up.
Reproduction steps
- Open the config.yml file and set example to true.
- Restart the server
- Run /lp user example permission set x from the console
- See error
Expected behaviour
Please help me solve it this problem, I want to use LP Web Editor.
#...
Can you check that the computer running your mc server can access https://bytebin.lucko.me/
I have hosting, how can I check that?
Description
Recently came across a warning/error when a player logged in with the username "Imperial", if you don't know this IGN is actually tied to two different UUID's/Mojang accounts. This causes LuckPerms to throw a warning in console when they both login or when one logs in after the other. I'm unsure of what consequences this may have on luckperms
Reproduction steps
- Get an account with the same IGN as another player.
- Login both accounts to the server.
...
I have server on hosting, how can I check that?
Contact your server host to ask...?
GIT - https://github.com/MinecraftForge/MinecraftForge.
Permission API - https://github.com/MinecraftForge/MinecraftForge/blob/1.16.x/src/main/java/net/minecraftforge/server/permission/PermissionAPI.java
Example permissions hook for command (with mixin) -
`@Mixin(CommandSource.class)
public class MixinCommandSource {
private static final String PERMISSION_LEVEL_NODE = "minecraft.op.level.";
@Final
@Shadow
private ICommandSource source;
@Inject(method = "hasPerm...
Hey, my suggestion for people wanting to use permissions on Forge servers is to install Sponge. :)
Hey, my suggestion for people wanting to use permissions on Forge servers is to install Sponge. :)
At the moment, it does not support versions higher than 1.13, and in addition to advantages it has disadvantages. For example, in real tests, forge will withstand more online than spongeforge
That old version is no longer supported.
So unless you can recreate that issue on a modern LP version it’s pretty much mute.
invalid plugin exception
Log paste: https://bytebin.lucko.me/RnZpFdicbT (modified to remove unsafe stuff)
Reproduced on both paper and yaptopia (bukkit).
luckerms is the only plugin that doesn't work on java 16
There are plenty of reasons to use java 16
java 16 gets 36cps, java 15 just 27 (on my server)
its way faster and it fixes garbage colection bugs from previous versions.
That old version is no longer supported.
So unless you can recreate that issue on a modern LP version it’s pretty much mute.
I get same warning on 5.1.86 on one of our backend servers. I assume this would hold true for even the current version of LuckPerms as well. I see no commits which would of done anything about this?
I'd have to agree , The latest builds are not right . If a player logs off while in the air , they get kicked when logging back on , contrary to setting allow flight in survival . I just became aware of this . I think it started with last weeks builds . When I have time I can look into it some more.
[16:45:35] [Server thread/WARN]: maelnelson was kicked for floating too long!
[16:45:35] [Server thread/INFO]: maelnelson lost connection: Flying is not enabled
@Tsoccerguy3 How is that a LuckPerms issue?
Description
In the web editor (https://luckperms.net/editor), you are not able to edit group non-permission based properties such as Display name, Parent, Weight, Prefix, Suffix. You should be able to.
Description
I know I submitted this before but I'm very confident it's either luckperms or fabric poxy being broken here
Reproduction steps
- Have a bungeecord and fabric server
- Using MYSQL as storage type join the fabric server
- be sad
Expected behaviour
Environment details
Fabric Running Latest Build, Fabric Api Latest Build, Fabric Proxy latest buildLuckPerms version: v5.2.92
You absolutely can! Just not in a "regular" way; they are sort of like permissions and they are explained and shown here https://luckperms.net/wiki/Web-Editor under "LuckPerms Nodes"
(also this would be more suitable for the lucko/LuckPermsWeb repo :p)
You absolutely can! Just not in a "regular" way; they are sort of like permissions and they are explained and shown here https://luckperms.net/wiki/Web-Editor under "LuckPerms Nodes"
I didn't know that. Thanks.
Hi,
I've just switched over from group manager to Luck since groupmanager breaks all the time, and I wanted to add all permissions to the Owner rank, since in its default state with op, it blocks a bunch of permissions. In groupmanager I used to be able to put the '*' permissions, but there doesnt seem to be something like that in Luck, is there any solution for this?
You can use the same *, it's a global wildcard.
Description
The NodeMutateEvent , NodeAddEvent and the NodeRemoveEvent are only fired when the Nodes are changed using in-game commands. All editor changes are ignored.
Reproduction steps
- Register listeners for
NodeMutateEvent,NodeAddEventand theNodeRemoveEvent. - Make them print a debug message.
- Compile plugin and put it on the server.
- Run
/lp user permission set-> See debug message - Do the same thing from the editor
- Save editor ...
Thanks for the detailed report! This should be fixed by the above commit :)
You can either:
- ignore the warnings
- prevent those players from joining your server
I'm reluctant to remove the warnings - because well, they are warning you about a valid issue lol
Plugins simply are not going to behave correctly when two players are able to join the server using the same username. LuckPerms should be mostly ok, but bear in mind if you use their usernames to make changes using commands, it's probably going to actually apply the change to whichever user logged ...
Thanks for reporting, I'll look into this and get back to you :)
Well.. I already told you what the problem is:
https://github.com/lucko/LuckPerms/issues/2835#issuecomment-764615885
This isn't a LuckPerms issue - the event simply is not being called.
Would it be possible for the editor to show offline players using the usercache.json (or an option to show these players in the editor)?
According to the new Java 9 module system, this shouldn't even work with Java 9, due to the much more strict encapsulation that was introduced that also applies to reflection
It works fine up until J16 because we're able to open the package to the 'unnamed module' at runtime.
Seems this is no longer possible, so will need a new solution.
Description
The issue presents itself with GriefDefender that uses LuckPerms as data storage.
Basically, every time I run a /gdreload or re-start the server - the amount of flags stored in one of the groups - griefdefender_definition - changes drastically. It should contain around 100 flags, but the amount jumps from single- to double-digits. It looks like GD clears that group and adds flags to it one-by-one asynchronously, which LP doesn't like and sometimes even breaks the...
This looks phenomenal! fixing #1365 has been impossible for a while, but I think that it needs a config option (people hate synchronous operations that they're unaware of) so that people who enable it are aware and willing to use a sync operation regardless of potential downsides
(sender instanceof RemoteConsoleCommandSender) limits synchronous operations to just RCON. User commands and console commands will operate asynchronously. There is also WARNING before each response for RCON users that this command could block the game thread. I feel like a feature flag for a bug fix with no breaking changes is an anti pattern.
The warning imo is less preferred than a toggle - if you want to use it, having a potential flood of warnings would not be preferable, while if you don't want to use it, rcon commands should be blocked entirely. This isn't exactly a bugfix as it does not correct the source problem, it rather works around the problem by forcing RCON commands to run synchronously. As this is, as I see it, closer to a feature, it may be something users want to entirely disable, and if they want to use it then
1...
Shud i use pidgeon upstream? Its in english? No breaking changes? @karlatemp
是英文吗?没有不兼容的更改?
https://github.com/Karlatemp/LuckPerms-Mirai/commit/45ea8dab5bc37acf4f515d6b13dc70bfe1b7fd57
bump, upstream might contain valuable code
You convinced me that the warning is noise and should be removed. Done.
I'm not convinced this is a feature. The problem is lp commands over RCON do not output a response. A response is the only indication of successful or failure on RCON: https://developer.valvesoftware.com/wiki/Source_RCON_Protocol
I'm also not convinced RCON commands should run asynchronously. I couldn't find an RFC to confirm this, but RCON protocol seems to be serial in nature with one (or more) response packets fo...
this is the error
[23:43:45 INFO]: [LuckPerms] Enabling LuckPerms v5.2.94
[23:43:45 INFO]: __
[23:43:45 INFO]: | |) LuckPerms v5.2.94
[23:43:45 INFO]: |_ | Running on Bukkit - CraftBukkit
[23:43:45 INFO]:
[23:43:45 INFO]: [LuckPerms] Loading configuration...
[23:43:46 INFO]: [LuckPerms] Loading storage provider... [MYSQL]
[23:43:46 INFO]: luckperms-hikari - Starting...
[23:43:46 INFO]: luckperms-hikari - Start completed.
[23:43:47 INFO]: [LuckPerms] Loading ...
I reckon there should be a setting (something like rcon-sync-operations or whatever, false by default) that if false it blocks the operation and warns the sender instead but if true it just doesn't do that and runs the command unsafely; this would be more like vault-unsafe-lookups when making operations for offline players on the main server thread.
I'm not clear how synchronous execution of a RCON command is unsafe.
The issue isn't the RCON command, the issue is that the operation will effectively run on the main server thread and, if the operation takes long time to complete (e.g. load user data, run a heavy database query, bulk operations on text-based storage methods, etc), it will cause lag; that is <i>the</i> reason why vault-unsafe-lookups is false by default and throws a runtime exception.
We have the following requirements:
- RCON should run synchronously for consistency/adhere to the protocol
onCommandmust complete quickly to avoid blocking the main game thread
Proposed changes:
- Add support for integerKey
- Include rcon-timeout-seconds defaulted to 5
Commits updated.
Including a timeout is a great option, but does not solve the main problem - primarily that rcon commands run sync and sync operations are toggleable in LuckPerms. As Fefo brought up, there are even other examples - vault-unsafe-lookups des not have a timeout, but rather a toggle. I believe it is better design to allow a toggle because having a default, limited, timeout will not match some users' specifications, while a toggle allows them the freedom to choose entirely.
I'm thinking her...
The timeout supports that behavior. Set the timeout to Integer.MAX_VALUE. The pedantic among you will argue that is only a 68 year timeout but I'm willing to wait and see if anyone hits it :trollface:
Description
/lp setting|settinginfo|configinfo
Proposed behaviour
It would make and report various checks regarding the config setting specified:
- Is it present / not null?
- Current value (fallback value if not present / null, letting the user know of its invalid state)
- Is reloadable?
- Setting type (list of x, storage type, string, integer, etc)? (If it isn't the one expected, maybe let the user know of the invalid state)
Maybe suggest/check for settings listed...
LuckPerms does not format prefixes/suffixes nor does it display them in chat/tab/tags/scoreboard, it's totally up to the chat/tab/tags/scoreboard plugin you use on your server to format the prefix/suffix accordingly, so you have to use the RGB format they specify on their documentation.
a JSON dump of all config data uploaded to bytebin could be useful, too
thread {
# The number of threads to use for GD's executor. (Default: 1)
executor-threads=2
}
This value in GD's global.conf has to be more than 1, otherwise GD does everything in a non-parallel way, which obviously results in single-threaded processing without any race conditions.
the following are excerpts from a chat on discord:
make lp debug which dumps all data (except users) into a json and ships it to a web viewer
and then lp debug --full which includes users
by everything I mean editor data, but also config and server startup and other plugins involved
@Turbotailz could make a web viewer for that
it will send everything so we can cross reference and check startup logs while also checking lp info and group names and literally everything at once
we ...
Ahhhh amazing - thank you!
Should be fixed by the above commit, thanks for reporting :)
Try deleting and re-downloading the jar file. Seems like it has been corrupted somehow.
Description
Reproduction steps
- Run /papi ecloud download LuckPerms
- Run /papi reload
- Run /lp user example parent addtemp groupname 91d
- Run /lp parse example %luckperms_group_expiry_time_%
Expected behaviour
Correct the same time as /lp user example parent info
Environment details
- Server type/version:
Paperrunning version1.13.2buildgit-Paper-655 - LuckPerms version:
v5.2.84
Any other relevant details
...
Hi, I made a post here a while back asking about adding the * perm to my server. It doesn't seem to work and I've tried all of the main options, I've tried * and then the following ones too: . '*'. and none of them seem to work. I'm running a 1.8.9 server which your plugin page says is supported, but me and the other owners are trying to do things after switching over from essentials, but we're constantly being blocked by LP saying we dont have permission, how do I fix this?
Hey, I think I'm going to try a more long term solution instead of more hacks - but thank you!
Hey, thanks for the PR!
However, I would prefer it if we took a slightly different approach: a boolean config option like rcon-run-commands-sync which defaults to false, but when true, uses the blocking behaviour.
LuckPerms commands are not suited to being ran on the main thread - most of them involve some sort of blocking i/o which will make the server (game) thread lag if executed sync.
The reason for defaulting false - rcon is still perfectly functional at the moment for LP comm...
If you'd be happy to make those changes, I will merge the PR. :)
If not, I don't mind making the changes myself, since I agree it would be a useful option to have.
The debug command was removed because nobody was really using it!
I'd be happy to add it back, although it would be nice if we could time it with some sort of viewer on luckperms.net.
Even if that just means a simple page that can render JSON as-is in a pretty way, kinda like the viewer on https://jsonformatter.curiousconcept.com/
https://myst729.github.io/vue-json-tree/ or https://github.com/chenfengjw163/vue-json-viewer#preview could work
Gracias, lo arreglé.
Pues yo no
What is your obsession with single line commits & PR's
Hey, someone had to do it :p
Description
I'm trying to make a plugin which gives a player a permission. In the docs, it says I should use PermissionNode.builder("my.permission").build() but when I try to build my plugin, gradle says:
Calls to static methods in Java interfaces are prohibited in JVM target 1.6. Recompile with '-jvm-target 1.8'
I don't want to change a version or something I'm using
Reproduction steps
- Make a plugin with Kotlin
- try to set a permission / build a PermissionNode with `...
LuckPerms only supports Java 8 and above - you're trying to compile using Java 6.
If you're using Gradle, you need to define
sourceCompatibility = 1.8
targetCompatibility = 1.8
in your buildscript, or for Maven:
<properties>
<maven.compiler.source>1.8</maven.compiler.source>
<maven.compiler.target>1.8</maven.compiler.target>
</properties>
I did that and it still doesn't work
Please use StackOverflow to ask "how-to" and "why-didn't-it-work" questions.
Or GoogleSearch
Description
All placeholders that return an amount of time are not parsed correctly - the amount of hours is often greater than or equal to 24. For example, when I run the /papi parse USER %luckperms_group_expiry_time_GROUP%, I get values like "5d 36h 1m 23s".
Reproduction steps
- Run
/lp user USER permission settemp test.test true 1d2h - Run
/papi parse USER %luckperms_expiry_time_test.test% - See the returned value - you should see something like `1d 25h 59...
Description
Changing the usergroup manually through the database, you expect to change the primary group in the players table
However, this is not the case you have to change the player record in permissions.permission from group.{old} to group.{new}
Changing the Primary Group will not change anything in the server when you obtain the info through /lp user {name} info
This will change whenever you update permissions.permission
Proposed behaviour
Either the usage so t...
What happens if you specifically include the permissions for essentials as: essentials.* as additional line?
I am running the latest MC server and it works fine for me setting: * with value: true
Ok I got it working, for kotlin, I have to do
compileKotlin {
kotlinOptions.jvmTarget = "1.8"
}
Description
Quite simply, once two servers are connected to the same database (for luckperms only), the console will spam the error: me.lucko.luckperms.lib.hikari.pool.PoolBase - luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@(No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
Reproduction steps
**1. Have a Bungeecord server and a Spigot server
2. Put Luckperms ...
Take a look at https://luckperms.net/wiki/Storage-system-errors#mysql-no-operations-allowed-after-connection-closed-error for a detailed look at your problem and potential solutions.
Also, make sure to update to latest LP at https://luckperms.net/
When I do it for specific plugins, it works, but the wildcard * doesnt work on 1.8.9 which is the version of one of our prominent servers. It seems to work on newer version but not on 1.8
Paste your LuckPerms config in https://bytebin.lucko.me/ and send the link over.
What LuckPerms version? ("latest" is not a version).
Any errors on console?
What server software are you running?
Basic debugging information 👏
Please consider using the issue template next time...
Hello, after the change of the database, the problem seems resolved ...
I hope at least. Thank you very much for your help, I had already watched this article, and it had not worked, and everything is up to date.
###optimalisation:
Also using the normalization form will optimise the plugin (application) as there is less data to be obtained.
An player contains a uuid (unique user id)
Which means we can hold this as primary key (the row identifier) | {additional info}
A group is now only consistent out of a name. Maybe add the data related to a group to this table instead?
Such as: title, weight etc.etc.
The group name is unique so we can index this one as well as prinary key.
Then we get to...
Description
When you try to join a Fabric server through BungeeCord/Waterfall using FabricProxy, LuckPerms does not allow that login because player's data couldn't be loaded during the pre-login stage.
Reproduction steps
- Create a Fabric and a BungeeCord/Velocity server
- Put FabricProxy (only on Fabric server) and LuckPerms as mods
- Try to log in to the server and you'll see the error in the console.
Expected behaviour
A successful login was expected...
Please try again using LP v5.2.100 or newer (https://luckperms.net/download) & ensure debug-logins is set to true in the LP config.
If the issue still occurs, please could you provide console/log output again :)
Hello!
I won't be able to test it until tonight, sorry for that. I'll answer you as soon as I can.
Thanks for your quick answer!
Description
Luckperms does not autofill the commands in the editor.
Reproduction steps
- Create a Fabric server
- Put luckperms in the mods folder(with Fabric API)
- Restart
- Do /lp editor and have a look.
Expected behaviour
I expected there to be a list of available commands.
Environment details
- Server type/version:
Fabricrunning version1.16.5latest. - LuckPerms version:
1.16.4
Any other relevant details
Here ...
This looks really great - thanks so much!
Hi again.
I have tested LP v5.2.101 on BungeeCord but the issue wasn't fixed. Here you have the console output.
[21:56:39] [Server thread/INFO]: Kikisito[/127.0.0.1:55490] logged in with entity id 217 at (253.5, 70.0, -156.5)
[21:56:39] [Server thread/INFO]: Processing login for 31c7be0d-89fc-401e-9d16-bafca8739984 - Kikisito
[21:56:39] [Server thread/WARN]: User 31c7be0d-89fc-401e-9d16-bafca8739984 - Kikisito doesn't currently have data pre-loaded - denying login.
[21:56:39] [S...
Description
Can you please add support for WaterdogPE (https://github.com/WaterdogPE)? It's an new version of waterdog with a new API.
You're free to do this yourself if you want, though I don't know if @lucko has any intention of maintaining support for this.
If you're not seeing a log message saying "Processing pre-login..." then Fabric's ServerLoginConnectionEvents.QUERY_START event is not being fired.
This not not an issue that can be caused by LuckPerms itself, and is either an issue with Fabric or another mod.
Sorry, not much more I can do to help.
The permissions list is populated as permission checks run - bear in mind also for Fabric that not all commands have permission checks implemented (in fact, the majority do not at the moment)
Doesn't seem like there's a permissions API that LuckPerms can hook into yet.
That aside, I'm also reluctant to add support for more platforms (officially) until they've proven to be stable / popular. Perhaps we can revisit this later once Waterdog has matured a bit :)
Description
When the tempgroup is >25 days the placeholders %luckperms_group_expiry_time_% doesn't work, I don't have 24d etc ... I have something like 59h etc ...
We have a big problem with the placeholders bcs if the tempgroup is 24days I have 23d 35H etc ...
- Server type/version:
ExampleSpigotrunning version1.12.2build??? - LuckPerms version:
v5.2.77
Hi again.
Thanks for your answer. I've been still trying to see what was happening for this and switched again to Velocity. I forgot to test the build using this proxy before (i'm really sorry for that), and the console output is different.
[18:48:07] [Server thread/INFO]: Processing pre-login (sync phase) for 859a0db5-6499-3552-96ea-c8543a67ff75 - Kikisito
[18:48:07] [ForkJoinPool-4-worker-59/INFO]: Processing pre-login (async phase) for 859a0db5-6499-3552-96ea-c8543a67ff75 - Kik...
Basically where you can tell the meta key that they are dealing with a placeholder so it can get parsed correctly and not into text.
example: lp prefix.
so something like meta.prefix.%luckperms_prefix%
That way you get a return of the actual prefix and not just pure text form.
I am aware that this would be stupid for this example. i simply used it as a simple explanation.
It would be useful if you are using custom placeholders and want to use multiple at the same time to where ...
@lucko we're seeing exactly the same thing with velocity+fabric
Description
Fabric server 1.16.5 don`t start with Chunky and LuckyPerms.
Environment details
- Server type/version:
Fabric 1.16.5 (loader 0.11.1) - LuckPerms version:
v5.2.104
Log
As you can see from the log, the pre-login event is being called with the UUID 859a0db5-6499-3552-96ea-c8543a67ff75 (looks like the offline mode UUID) and the login event with 31c7be0d-89fc-401e-9d16-bafca8739984 (looks like an online mode one!).
Both UUIDs should be the online one - this is most likely an issue with the mod which is providing Velocity support.
Thanks again for answering and for your help. I'll report this to the author of FabricProxy as it seems the issue comes from here. Have a nice day.
Description
After an update of LuckPerms from version 5.1.47 to 5.2.104, colours a no longer shown for the groups display name when running /lp listgroups
v5.1.47: https://i.imgur.com/oSfCPZw.png
v5.2.104: https://i.imgur.com/RvgKXCx.png
Reproduction steps
Upgrade from any version 5.1.x to any version above v5.2.76 (These are the 2 I was running at the time)
Expected behaviour
Expected displayname formatting to be shown
Environment details
- Server...
LuckPerms Fabric v5.2.104
PlayerRoles 1.3.0
Description
Crash with PlayerRoles
Log:
2021-02-08-5.log
For those who don't want to download random files: https://bytebin.lucko.me/fYAWUhS4gt
Niketats, it looks like you're using two different mods that have the same purpose and they're conflicting. I'm not 100% sure on this due to my lack of experience with Fabric, but I believe you can only have one mod interacting/assigning permissions via the Fabric permissions API. LuckPerms and PlayerRoles both seem to do this, so you'll need to pick one.
Description
Reproduction steps
- User registered/login at server
- User logout
- I can see the user at web luckperms console
- user missing for about a day
- user info lost from web luckperms console
Expected behaviour
Environment details
Any other relevant details
Note that there isn't any syncing of data between storage types. You need to export and then import the data. See: https://luckperms.net/wiki/Switching-storage-types#how-to
The data was exported and imported as the developer specified-with the appropriate /export and /import commands. The server reported a successful import of the database, and the data in the Mysql database was reflected, but not all.
Hello,
it's me again!
I have a problem that makes user get their group's meta (prefixes and such) when they get set to another group.
Since last time, the problem seemed to vanish by itself, however yesterday it returned.
When we ran the command /lp user USER parent set GROUP, we observed the user got the group meta set as their own.
We tried completely deleting everything from LuckPerms - groups, tracks, users, everything, but to no effect.
The new groups suffer from the sa...
This issue has been solved with the last version of FabricProxy-Lite (https://github.com/OKTW-Network/FabricProxy-Lite/issues/1). I leave the link here if somebody needs info about this.
Description
Maybe if there was a way to make a context work only when it is FALSE.
Proposed behaviour
Some might want a person to have a certain group on every world/server except one. I've needed this multiple times recently. Something like world=!worldname.
Hello,
I would like to report a problem that I almost always have with the plugin.
I start to get these types of warnings that are errors that are generated, they take out all my players and it is usually repetitive. Sometimes those messages that I show in the image keep coming out, and I already checked all the configuration and it's fine, besides that I went to its page to see the error wiki and everything is correct, but I still have the same problem , and this occurs between all con...
Description
Luckperms does not respond on latest version after executing more then 100 permission nodes (104)
and it does work find on older versions (76)
Reproduction steps
https://www.youtube.com/watch?v=ESCaD_0_fF0&feature=youtu.be (Version 104 Latest)
https://www.youtube.com/watch?v=2ULt-oH2PNg&feature=youtu.be (Version 76 Older)
Expected behaviour
Environment details
- Server type/version:
paperspigotrunning version1.12.2build??? - L...
Hello!
- You don't need to bump issues - they will be addressed when possible if the template requested is filled out correctly.
- Please fill out the template requested as asked in a new issue, with specific version number details as requested, and close this one.
Thanks for reporting, hopefully the above commit will help :)
The error here is originating from the driver, and is not being caused by LP.
The wiki page you referenced already (https://luckperms.net/wiki/Storage-system-errors) is my exhaustive advice on these issues - sorry but there's not much more I can do to help.
It's unlikely that there's a bug that is causing this issue, perhaps you made a mistake during the migration?
If you still have the import/export files to hand, I can take a look to see if the data is there? You could always run the import again and it'll merge the old data back in again.
Closing for now, but please feel free to re-open if you have any more info to give.
The issue is with FabricProxy - not LuckPerms.
User c8c1425f-75a9-3afb-a193-66d8112d1eee - NikitaCartes doesn't currently have data pre-loaded - denying login.
See #2873
Group display names (or think of them like aliases) are not meant to contain color codes.
The intention was to just allow nicer formatting (since LP forces the actual name to lowercase):
e.g. format owner --> Owner or sradmin --> SeniorAdmin.
Of course, there aren't any restrictions on what characters you can use - so you can put color codes in there if you want - but LP won't format them for you - at least in internal commands.
The reason for the change is because we phased...
I'm not sure why you think Chunky is the issue..?
Strange error though, to be honest I'm not sure why it's happening. Try updating to the latest Fabric/FabricAPI maybe?
Morgning My LuckPerms data was in Mysql type
I created the character "Test" and went into the game with it. After then relogin as an administrative character. In the webconsole, character was, i checked it. I applied the permission for the group (adding rtp for default), and then opened the lacperms console again - the "Test" character was no longer there - it just disappeared.
There were no storage migrations between it 2 action. LuckPerms was and remained on Mysql. After that, I moved th...
Description
When we ran the command /lp user USER parent set GROUP, we observed the user got the group meta set as their own.
We tried completely deleting everything from LuckPerms - groups, tracks, users, everything, but to no effect.
The new groups suffer from the same bug.
Reproduction steps
1.Create a group
2.Try setting it to a user
3.The user has now their previous group's meta set as their own.
Expected behaviour
The user meta remains untouched
#...
Tested with 3 mods
fabric-api-0.30.0-1.16
Chunky-1.2.29
LuckPerms-Fabric-5.2.104
Got it
latest.log
When i delete one of mod, LuckPerms or Chunky server start successfully.
At the moment I really have no idea how to do this without breaking the "one-class" structure.
Could you send some screenshots illustrating what you mean? I don't really follow what the problem is

The user "dedda" has a group set as primary that does have item meta, but has inherited her previous group's meta (default), which got applied to her as personal user meta.
On my Bungee server I get the error when loading the plugin.
Could not load class "org.slf4j.impl.StaticLoggerBinder"
As the image shows, it is not loading correctly the corresponding class of slf4j

What BungeeCord version? What plugins do you have on your proxy? Is there anything else to that error?
I have this version of bungee

These are the plugins that I have in the bungee and I don't think that any are interfering

And not, only does this error appear when loading luckperms, apparently the plugin is not loading the corresponding class as mentioned above...
Are you able to reproduce the issue with LuckPerms as the only plugin?
you mean remove all plugins and just run luckperms to see if the error continues?
Apparently you are right, a plugin is interfering with the connection of the class, previously I have not had problems and I did not get this error, maybe it is with some update of the plugin that is causing the class not to be executed, some way to fix it ? Or would you just have to report it to the plugin that is doing the interference so you can validate and fix it?
Another question, what does that class not work? Would it cause a fatal error in the plugin? or in the connections?
SLF4J is just the library used by Hikari (the library in charge of handling connections to the database) to log things in console. Everything will still work, the logger will just fallback to a NOP (no-operation) one, meaning it won't print anything, you just won't see things like errors or warnings printed by Hikari; is it ideal? Well no lol, the issue is one of those plugins is (most likely) being shipped with an ancient version of SLF4J.
Thank you very much for the report, maybe that is what is causing another error that I keep with luckperms, now that you tell me about hikari, although I will see if the problem is that, I will report right now about this inconvenience to the other plugin for see if you can do something about it, thank you very much again.
Personally suggest adding a function that can increase the limited time inheritance time. I believe this function will be very popular. The function means that it can increase the time from the original time.
The permission group is set with a prefix, and the player has the prefix of the permission group after entering, but it cannot be returned to the prefix of the default group after it expires.
You can already achieve this by adding accumulate after the duration in the addtemp command, see the [temporary modifier] argument in the parent addtemp command page :)
That one. . . . . Can you give me a specific example how to write.
Already understand, thank you for your confusion
Description
We should be able to use placeholders in prefixes and suffixes.
Proposed behaviour
When we are be able to use placeholders in prefixes and suffixes, placeholders will be shown in prefixes and suffixes.
Before starting, I want to say that I am reporting this for someone else who had this issue and doesn't know how to make a bug report. If the info provided is not sufficient or anything else is wrong, feel free to close. Just wanted to forward this.
Description
Running a command that called Chat#getPlayerSuffix threw an exception (https://paste.gg/p/anonymous/17155bf2a1b644339def4661edff27f2), line calling it is at https://github.com/NEZNAMY/TAB/blob/716466e444689e6e79b1e66349dd...
If the player is definitely online, then LP should have some data loaded for them - the full log may give some more insight into this.
Without it though, not much I can do to debug the problem further.
Yeah, so, logs are pretty clear - they weren't connected to the server when the LP warning message was printed. :wink:
[11:37:15] [User Authenticator #4/INFO]: UUID of player AleafL is 9a7b2995-03dd-38c2-b715-69673f57e3e5
[11:37:15] [Server thread/INFO]: AleafL[/xxxx] logged in with entity id 18188 at ([world]4019.815052779904, 69.0, -2911.5489495565566)
...
[11:46:52] [Server thread/INFO]: AleafL lost connection: Disconnected
...
[11:50:53] [Server thread/INFO]: [TAB v2....
Description
lp bulkupdate users delete "permission ~~ group.%"
doesn't work .-.
Reproduction steps
issue lp bulkupdate users delete "permission ~~ group.%"
% being a group.
on a 1.16.4 server with viaversion. viabackwards and viarewind (latest stable versions.)
Issue the command thru console and it won't work.
- Open the config.yml file and set example to true.
- Restart the server
- Run /lp user example permission set x from the console
- See error
not ev...
Description
Hello, i have a problem with LuckPerms and essentials. All essentials.PermissionExample doesn't work at all. I made a single rank, with "essentials.kit.daily" or "essentials.msg" (the kit was already created) and player doesn't have access to these command, even if i give them the permission. Tested everything, nothing works. All essenitals permission just doesn't work with Luckperms for some reasons.
Any help?
Sorry for the bad english :(
Reproduction steps
...
According to essentials documentation, lets use your kits example. You will need essentials.kit AND essentials.kits.[kitname]. I think you are just using the wrong permission nodes, contact essentials support on it and sending your editor link so we can see the perm nodes you set will be useful in this case.
According to essentials documentation, lets use your kits example. You will need
essentials.kitANDessentials.kits.[kitname]. I think you are just using the wrong permission nodes, contact essentials support on it and sending your editor link so we can see the perm nodes you set will be useful in this case.
The problem is, it's not that.
Because every permission doesn't work so,
essentials.msg
essentials.afk
etc, etc doesn't work at all.
Ok so here are some info youy should provide:
- screenshot output of
/ess version(run command from console) - send your editor link.
- Run
/lp verbose command <player> <command>replacing the placeholders appropriately
Make sure LuckPerms is your only permissions plugin installed, other perms plugins will take over if any is present making LP not function.
You can find a very small list of permissions plugins in the [migration page] (https://luckperms.net/wiki/Migration) (keep in mind that it's not an exhaustive list and other perms plugins exist).
If you are unsure whether or not one of your plugins is a permissions plugin you can upload a screenshot of /plugins.
Ok so here are some info youy should provide:
- screenshot output of
/ess version(run command from console)- send your editor link.
- Run
/lp verbose command <player> <command>replacing the placeholders appropriately
(edit: also ensure you test with a player that are in the correct permission groups.)
Version Server : 1.16.5-R0.1-SNAPSHOT git-Paper-468 (MC: 1.16.5)
.... [19:10:47 INFO]: Version EssentialsX : 2.19.0-dev+74-36422ab
.... [19:10:47 INFO]: Ver...
UPDATE :
I deleted the essentials folder (except the users data + warps)
and the permissions finally works!
Sorry about all of this, i should have deleted the essentials folder in the first place!
Description
I use Craftbukkitlogin, an authentication plugin, for security reason. If I deop myself, i can't login nor register.
Reproduction steps
- Register and login using Craftbukkitlogin.
- OP myself with LuckPerms.
- Exit the server.
- Deop myself.
- Enter the server.
Expected behaviour
I should be able to use the password i created, or at least make a new one.
Environment details
- Server type/version:
Spigotrunning version `1....
Okay, apparently i just needed to change manually the password from the plugin file. I have no idea about what happened, but there's no problem now
Description
- The players don't come into my own default group, but always into "default", but I want them to come into my group, because otherwise I have to rewrite most of the plugins
Environment details
- Server type/version:
Waterfall&PaperMC-Version: 1.16.5 - LuckPerms version:
Waterfall - v5.2.107|PaperMC - v5.2.104
The Error
- https://prnt.sc/zrixnr - this error is on my (proxy)waterfall-server
- on my (bukkit/spi...
Description
No matter how long gone,Loading configuration is always stuck during startup

Even though I tried this

It doesn't work
Reproduction steps
Expected behaviour
Environment details
- Server type/version: mohist-1.12.2...
➜ /Users/luck/Desktop/servers/tuinity /Library/Java/JavaVirtualMachines/zulu-16.0.83.jdk/bin/java -DPaper.IgnoreJavaVersion=true -jar server.jar nogui
Unsupported Java detected (60.0). Only up to Java 15 is supported.
System Info: Java 16 (OpenJDK 64-Bit Server VM 16-ea+33) Host: Mac OS X 11.1 (aarch64)
Loading libraries, please wait...
...
[18:23:13 INFO]: This server is running Tuinity version git-Tuinity-"d3ee222" (MC: 1.16.5) (Implementing API version 1.16.5-R0.1-SNAPSHOT)
......
Description
Querying user meta-data (using LuckPerms API) with the method User#getCachedData#getMetaData#getMetaValue(KEY) does not query with the key lowercase forced, even though meta does not support uppercase characters.
This is an issue because setting new meta through the API (or commands) converts the key input to all lowercase if provided capital letters. This creates an inconsistency with setting/querying.
Reproduction steps
- Use the method with an...
Description
Luckperms cannot connect to PostgreSQL database
Reproduction steps
- Open the config.yml file and set storage-method to PostgreSQL, enter address, database, username and password.
- Restart the server
- See error
[18:34:37 ERROR]: [LuckPerms] Failed to init storage implementation
java.sql.SQLTransientConnectionException: luckperms-hikari - Connection is not available, request timed out after 5001ms.
at me.lucko.luckperms.lib.hikari.pool....
Seems like a duplicate of #2749
Unfortunately I don't have time to look into this myself at the moment, but will gladly accept a PR for it! :)
That's strange.
I need some more details in order to look into this further - specifically a stack dump taken when the startup gets stuck.
See here for info about how to do that: https://gist.github.com/lucko/81033b72927eee0246dc8e8c284664c4
Please re-open the issue once you've got that :)
The default assignments extension requires that Nashorn is installed on your system - unfortunately this is no longer being installed by default with Java installs, so you will need to add it manually for the extension to work.
The extension is for legacy support, so naturally it's not being maintained really.
Sorry, not much more I can do to help.
It's working fine for me... could you provide some screenshots to show what you mean exactly?
This is something your chat formatting plugin should handle, not LuckPerms :)
This sounds like an issue with your chat plugin.
Please use the template next time, it's there for a reason.
Another question, what does that class not work? Would it cause a fatal error in the plugin? or in the connections?
It's not a fatal error :)
The info command will show inherited meta too - perhaps you want to use the meta info command instead?
Unfortunately, this sort of thing isn't possible to implement given the way the system works currently.
In the meantime, I suggest you define/use your own static contexts, or just set a false override in the world you don't want the permission to apply in.
e.g.
# apply 'some.thing' in all worlds except the nether
/lp group default permission set some.thing true
/lp group default permission set some.thing false world=nether
I think this sort of behaviour would be better handled by the placeholder plugin itself. ("recursive" placeholder resolution I suppose is what you'd call it)
Please feel free to re-open if/when you implement those changes. :)
Incidentally, I switched from Mohist to Magma, but the problem remains the same

Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.202-b08 mixed mode):
"Thread-17" #78 daemon prio=5 os_prio=0 tid=0x00000000358f0000 nid=0x75e0 waiting for monitor entry [0x000000002bacd000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.bukkit.plugin.SimplePluginManag...
The important part is:
"ForkJoinPool-1-worker-11" #68 daemon prio=5 os_prio=0 tid=0x000000002ab4f000 nid=0x5b70 waiting for monitor entry [0x0000000034e5c000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.bukkit.plugin.SimplePluginManager.getPlugins(SimplePluginManager.java:366)
- waiting to lock <0x00000006d9c8c898> (a org.bukkit.plugin.SimplePluginManager)
at pw.yumc.Yum.kit.PKit.collectPlugin(PKit.java:176)
at pw.yumc.Yum.kit.PKit.getOperatePlugin(PKit.java:57)
a...
No, no, I use the parse test function of papi, and the test is the variable %luckperms_prefix%. No matter how you adjust it, the return is the prefix when setting, not the fixed prefix of the group
I know the reason, because I inherited the relationship of the default group, and then my default group is also set, he will give priority to display the default group, you can see if you can let other groups inherit the default group or common inheritance Not inherit the prefix
I found a problem. If the player has both the default group and the VIP group, and both groups have default prefixes, he prefers the prefix of the default group. If you don’t want to display the prefix of the default group, the player must delete the default group. Inheritance.
Looks great, thanks!
Also fyi I updated the gradle wrapper which should fix the issues you had building :) 7579bbe5496ad0e2e1bfab8f468c708bc4b3e69b
Should be fixed in 435e039b38f5b0d676d700589e8fec38a2f6442c
You ignored the issue template - in future, please don't, it's there for a reason.
It sounds like your issue will be resolved by setting group weights.
Thank you very much. After my test, gradle can be built normally. I am very sorry to be so anxious to get your answer, but your discord group does not welcome me. Maybe I don’t understand your customs, but @somebody is not the most basic Notify? @lucko (This is a friendly @
Hey,
i have a plugin named harry potter economy for my chatformat and if i install luckperms the chatformat dissapear for no reason here are some screenshots
without luckperms

with luckperms:

Error in console:
https://pastebin.com/Ta6MML...
Note that LuckPerms isnt blocking the other plugin. From the errors you sent, it seems like harry potter economy plugin is not using the luckperms API correctly.
when you try and tab complete the command in an execute command: https://prnt.sc/1045sm6
it'll give you a few error messages in chat and it will basically flood your console with the error message down below
I'm not entirely sure if this is due to the plugin or Minecraft self that doesn't understand the integration of the plugin commands
`[21:41:05 ERROR]: Exception when crazy_chikken98 attempted to tab complete execute as @p run lp user
org.bukkit.command.CommandException: Unhandl...
Plugin commands don't really work with vanilla execute. You can enable resolve-command-selectors in LP config if you want to use @ selectors in LP commands (e.g. lp user @r promote staff) and you should use this instead of using the execute command.
https://github.com/lucko/LuckPerms/blob/40184932855d85d05189e8e705562d734ad660f2/bukkit/src/main/resources/config.yml#L663-L665
On another note, that error is due to LP registering commands in a way vanilla thinks they are van...
Description
Due to this commit 8167fbf and the way commands-allow-op works, having this apply-default-negated-permissions-before-wildcards: true and commands-allow-op: false set, makes luckperms.* being overriden.
Reproduction steps
- Open the config.yml file and set:
apply-default-negated-permissions-before-wildcards: true
commands-allow-op: false
- Run `/lp ...
After update to latest version (mohist-1.16.5-371) the log is being spammed with the following which prevents seing anything as it really does not stop.... I know it's not much info but something in the merge seems to have gone wrong...
classloading,re:classloading,re:classloading,re:classloading,re:classloading,re:classloading,re:classloading,re:classloading,re:classloading,re:classloading,re:classloading,re:classloading,re:classloading,re:classloading,re:classloading,re:classload...
Sorry I'm stupid, wrong repo
Description
Whenever there’s a database error, it always constantly spams my console, maybe remove that and replace it with something like this LuckPerms Database Is Offline! or something.
Proposed behaviour
This could work by changing it to something like this LuckPerms Database Is Offline!.
IMO, I dont see any benefit in thig change. The errors shown is important for debugging and shouldn't be cut to a single line so people can ignore them.
might it be a suggestion to add the support of HEX colors for the prefix/suffix?
this is how minecraft converts color codes
might be an usefull feature to add?
nevermind, i seem to have forgotten you need to add & before the text, it does already work
Description
I've used Luckperms for a long time and never had this issue but after the last server restart, the H2 database with all player permissions and groups just reset itself with no warnings in the logs regarding it.
Environment details
- Server type/version:
Paperrunning version1.16.5build492 - LuckPerms version:
v5.1.93
Any other relevant details
Sorry that I don't have any information to give on this but the console/logs show nothing. No plugins ...
Description
When I give a context to a permission (Work with Databases, MariaDB) and try to save them through the webgui, the plugin makes the change but when the gui is reopened all the contexts disappear.
Reproduction steps
- Open the gui
- Enter a permission in a group,
- Add a context, save send the command and close the gui.
- Finally, reopen the gui and there will be no contexts placed.
Expected behaviour
In reality he had to show me the contexts I...
What do you mean by "reopened"? Bcu you should not use the same editor link after apply edits.

In fact, as I have already written, you need to open a new editor.
And by reopened I mean I have opened a new editor.
Description
Paper 1.16.5 server with LuckPerms 5.2.76 randomly crashed
Reproduction steps
No idea, it randomly happened and has never happened before since running this server for a couple of years
Expected behaviour
It not crashing
Environment details
Paper 1.16.5 build 472
LuckPerms version 5.2.76
Log paste: https://www.lepelcraft.nl/log.txt
I used our own website as it was too big for pastebin
This doesn't seem like a LuckPerms issue but more like a problem related to entities in your server, I suggest asking in the PaperMC discord or making an issue in their repo.
But just to make sure, does it stop happening when you remove LuckPerms from the server?
I've only honestly seen this happening once, there was 1 player online, I was talking to them and just bam suddenly hundreds of errors in console until I managed to restart the server. I asked the player what they were doing but they said they were just standing still in the middle of nowhere talking to me.
I just saw it happen, was confused and decided to post here as it started off saying a luckperms process was hanging.
I have tried to fix my own but couldnt that than i came to your discord and they suggest someting but didnt solve here is my problem.
When i start my server than try to join it while server is opening (not quite opened yet) this errors comes to console
is it a big deal or not
This is because Player#getLocale() didn't exist up until 1.12(.0), before that there used to be Player.Spigot#getLocale() but it was introduced in 1.8(.0) (something easily fixable tbh); there is no fix for this issue for the Bukkit Legacy build of LuckPerms other than just gracefully falling back to English.
what should i do now couldnt understand. Maybe using another spigot ?
If you want to 100% avoid the issue you can use an older version of LuckPerms for Spigot (before v5.2, you can find those in the resource page in spigotmc.org) but this issue can be taken care of with ease.
I can't download the log file it seems.
However, as Fefo said, this is very unlikely to be a LP issue.
Description
On load the plugin cannot load the MySQL Drivers. Error: https://bytebin.lucko.me/4R3JOxIMF2
Reproduction steps
- I am not sure how I got this error, I will give you access to my server to see it though.
Expected behaviour
Plugin should load normally
Environment details
- Server type/version:
ExampleSpigotrunning version1.12.2build??? - LuckPerms version:
Bungee v5.2.120 - Flamecord:
0.4.6
Could you send a full log instead please
Da error de chat, cada vez que escribo algo salta error en la consola
I have the same problem but it makes another exception:
[InjectorReflectorException]: Could not invoke constructor of class 'class fr.exphi.authme.command.CommandHandler'
I have the same problem but it makes another exception:
[InjectorReflectorException]: Could not invoke constructor of class 'class fr.exphi.authme.command.CommandHandler'
Contact authme support. If for some reason you think is LP causing it (I doubt so), at least open a new issue.
Description
Suggestion - the ability to change the /op message when disabled (https://prnt.sc/10b24dh) through a setting in the config.
Description
Hi. Can you develop this plugin for WaterDogPE too? It will be awesome with that
Proposed behaviour
You can change the wording by editing the language file: https://luckperms.net/wiki/Locale-and-Translations
The base file is en.properties
Or, you might find it easier to use another plugin to override/block the op command before LuckPerms handles it.
Please try deleting the /plugins/LuckPerms/libs folder and restarting the proxy.
Hello, I'm interested in this update.
Are there any news about? TY
Description
I get kicked from the server when I type /lp, /luckperms etc.
Reproduction steps
- Type /lp or /luckperms in chat then hit space
Expected behaviour
User will get kicked
Environment details
- Server type/version:
Paper 1.16.4 with BungeeCord - LuckPerms version:
Latest, just tried changing it to the lastest version
Any other relevant details
This happened for the first time after adding the...
The Floodgate rewrite is probably actually coming out soon for realsies.
Insatlling ViaVersion and ViaBackwards seems to have fixed the issue?
Running mc on 1.16.4 client and server on 1.16.5
Hi I don't know what to do. My console is going crazy because of Luckperms. Trough night log file had 20gb. Please help me to fix it
Log: https://pastebin.com/6wNMT9vE
I reinstalled whole plugin so config is and was default
Help me to fix it because I wanna use this plugin any help would help
This is the part that concerns <i>you</i> and tells you what you <i>can</i> do about it.
The operation to load user data for '5eb36239-c818-3d55-8f80-648ae5312bf8' was cancelled by LuckPerms. This is NOT a bug.
The lookup request was made on the main server thread. It is not safe to execute a request to
load data for offline players from the database in this context.
If you are a plugin author, please consider making your request asynchronously.
Alternatively, server admins can disable this...
So maybe that warns are made by realscoreboard plugin ?
The warning is made by LuckPerms but it's caused by something realscoreboard does that could lag the server. What I pasted above is very explicit about what you can do but you should contact the author regardless.
Description
Error enabling plugin LuckPerms
Reproduction steps
- Start waterfall server using Luckperms 5.3.0
Expected behaviour
Load luckperms with no error on console
Environment details
- Server type/version:
Waterfall Bootstrap:1.16-R0.5-SNAPSHOT:2b1ac19:398 - LuckPerms version:
5.3.0
Error on startup: https://gist.github.com/SrBedrock/4c8bf60c27177a1c02077a79f16b2ad1
Not a LP issue, seems to be an issue with the root machine, possibly permissions?
Not a LP issue, seems to be an issue with the root machine, possibly file permissions?
Version 5.2.82 works fine
Unable to create a temporary file
AccessDeniedException: /tmp/luckperms-jarinjar6361610685842350805.jar.tmp
The user you're running the server as doesn't have permissions to write in the /tmp/ folder, this is not a LuckPerms issue. Make sure the user has read/write/execute permissions for that folder.
Good day,
It wouldn't be bad to add hex code and gradient support. It's because of the prefixes because it looks weird.
Example hex: {#FFFFFF}
Example gradient {#FFFFFF>}Text{#FFFFFF<}
Parsing of RGB format should be done by the plugin trying to display the prefix, e.g. your chat plugin.
It would be useful if you could either provide the crash log from your client, or be more specific about what version of LuckPerms you are using. "Latest" could refer to various versions depending on where you download from.
It would be useful if you could either provide the crash log from your client, or be more specific about what version of LuckPerms you are using. "Latest" could refer to various versions depending on where you download from.
Found out it was another plugin causing it.
All the settings aren't saving once i close the browser. every time i load it back up to add new perms to a role, it reverts back to the first every permissions i first uploaded when I made the server and only shows 5 of the players on the list when the server started. I now have over 10 players but only 5 of the first ever users are always shown.
Are you reusing the same editor session/link you previously closed?
I have it bookmarked. I was told by an admin on a hosting service to bookmarl it and use that. How else do I access it every time i wish to change it??
You create a new session with /lp editor. You <b>have</b> to create a new editor session if you want to keep making changes after applying them. Don't reuse old or used sessions.
That is explained in the second paragraph in the wiki page for the web editor
omfg, thank you so much. I now have to go back and redo at least 40 perm lines.....
Description
Update Extension-Legacy-API to support the new API 5.3
Proposed behaviour
Support the new API 5.3 (Extension Legacy API)
The extension will still work on 5.3?
An API method to change the server name. This would be helpful if you have a cloud system where you can store the config in the global plugins folder and then use the api to set the server name for the context.
API-Methode:
LuckPermsProvider.get().setServerName(String servername);
if you are talking about server context on backend servers, it's defined in luckperms config file, and afaik luckperms cannot change the config programmatically. Since you are using the API, you can just register your own context, and have full control over it.
Description
Paperspigot 1.8 with luckperms breaks
[17:41:00 ERROR]: Could not pass event PlayerLoginEvent to LuckPerms v5.2.76
org.bukkit.event.EventException
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:302) ~[patched.jar:git-PaperSpigot-"4c7641d"]
at co.aikar.timings.TimedEventExecutor.execute(TimedEventExecutor.java:78) ~[patched.jar:git-PaperSpigot-"4c7641d"]
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) ~[p...
Fixed in newer builds https://luckperms.net/download :)
Description
Logging in on paperspigot 1.8 throws an error (latest build from website)
[17:46:03 ERROR]: Could not pass event PlayerLoginEvent to LuckPerms v5.3.0
org.bukkit.event.EventException
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:302) ~[patched.jar:git-PaperSpigot-"4c7641d"]
at co.aikar.timings.TimedEventExecutor.execute(TimedEventExecutor.java:78) ~[patched.jar:git-PaperSpigot-"4c7641d"]
at org.bukkit.plugin.RegisteredListener.callEven...
- Follow the issue template please, it's there for a reason and get things going faster.
- Paste the entire server log (located in
logs/latest.log) in bytebin and send the link over.
Description
So if i add temp group to player, and i type somewhere placeholder %luckperms_expire_time_group.master% (it can be whatever) the placeholder says not 30 days but 5d 59h 59m 59s.
Expected behaviour
Expected is 30d not 5d 59h 59m 59s.
Environment details
- Server type/version:
PaperSpigotrunning version1.15.2buildgit-Paper-390 - LuckPerms version:
v5.3.0- i also tried5.1.26
Picture https://i.imgur.com/1CLls54.png
Description
Players with Spaces in their names can not be reached..
Reproduction steps
- Open the config.yml file and set allow-invalid-usernames to true.
- Restart the server
- Run /lp user "bob junior" info
- See you can not access the players information because they have a space in their name.
Expected behaviour
Should access Bob Juniors information
Environment details
Nukkit, latest version of it and luckperms
- Server type/version: `...
Description
When typing the command /lp editor and then executing the command, I receive this error: https://bytebin.lucko.me/5b7cruIzAG
Expected behaviour
There shouldn't be an error in the console :)
Environment details
- Server type/version: Paper 1.12.2, Paper 1.16.5
- LuckPerms version:
v5.3.0
(local database)
(the command was not executed it was an update of the record by another server)



I know I have an older version.
This is the first such b...
Description
Just a lot of errors and a crashing server, don't really know what happens.
I tried running with the lastest build on the site (5.3.0) and on old version on modrinth (5.2.92). With each build I get the errors.
When removing luckperms the server runs smooth.
Server:
2gb - shared test server
openjdk version "1.8.0_262"
OpenJDK Runtime Environment (build 1.8.0_262-b10)
OpenJDK 64-Bit Server VM (build 25.262-b10, mixed mode)
:/home/container$ java -Xms128M -Xm...
Description
When I start the server with the LuckPerms and server will load. And I see that my panel (Pterodactyl panel) is loading and MySQL server is going to time out!
Reproduction steps
- Open the config.yml file and setup the MySQL database and save.
- Restart the server
Expected behaviour
MySQL server is dropping.
Environment details
- Server type/version:
Yatopiarunning version1.16.4build40 - LuckPerms version:
v5.3.0
...
Description
When using a Unicode symbol in a group prefix, requesting info on that group will display the prefix twice.
> lp group moderator info
[12:23:00 INFO]: [LP] > Group Info: moderator
[12:23:00 INFO]: [LP] - Display Name: moderator
[12:23:00 INFO]: [LP] - Weight: None
[12:23:00 INFO]: [LP] - Contextual Data: (mode: server)
[12:23:00 INFO]: [LP] Prefix: "[★] [★]"
[12:23:00 INFO]: [LP] Suffix: None
[12:23:00 INFO]: [LP] Meta: None
This only ef...
might not fix it, but try updating to 1.16.5 (there are yatopia builds for 1.16.5, and there is no reason to stay on 1.16.4)
Description
So if player has group in some context for example server=lobby and you type /lp user nick parent removetemp group1 server=lobby it removes it in global so it says that he doesnt have this group in context global, so i have to make it manually from lp editor. This happen only in new versions like 5.3.0.
Expected behaviour
It should remove it from context Lobby but it removes it in context global
Environment details
- Server type/version: `PaperSp...
Description
Hello So i was using your Web Editor But Everytime i make a group, save it and refresh it gets deleted off of the Web Editor...
Reproduction steps
-
Fix The Issue With It Deleting Off The Web Editor
-
Open the config.yml file and set example to true.
-
Restart the server
-
Run /lp user example permission set x from the console
-
See error
Expected behaviour
it to not delete off the web editor.
Environment details
- Serv...
You have to create a new editor session if you want to keep making changes after applying them. Don't reuse old or used sessions.
This is well explained in the second paragraph in the wiki page for the web editor
Also notice the message here when you hit the save button ;)

I'm creating a pixelmon server on my computer and when I do "/lp editor" in the control panel it gives me a link that just brings me to the website and not an editor. https://luckperms.net/editor/?Jp5sOkjbsB This is an example of it. The only thing I've noticed is that there is a ? in all the links I get from the "/lp editor" command which, I don't see in any of the youtube videos showing me how to use the lucky perms mod.
Looks like you are using an outdated luckperms version, get from https://luckperms.net/download. Also, follow the issue template next time.
Description
When I try to join, it kicks me with this [LP] A database error occurred whilst loading permissions data. Please try again later. If you are a server admin, please check the console for any errors.
Reproduction steps
- Just connect LuckPermsBungeecord with MySQL
Expected behaviour
I don't know
Environment details
- Server type/version:
Aegis BungeeCord-forkrunning version1.16.5build??? - LuckPerms version:
v5.3.3
...
Description
Going through the nether or end portal crashes instaltly the server
Reproduction steps
Plugins and mods installed: GriefDefender 1.5.10, LP 5.2.76, create mod 0.3e and JEI for 1.16.4
Running with: Forge .58 and mohist 400 for 1.16.5
- Open the server.
- Use a portal.
- see crash log: crash-2021-03-14_14.22.08-server.txt
[lucko/LuckPerms] New comment on issue #2944: server crash when going through a nether or end portal
I dont see how this is related to luckperms?
[lucko/LuckPerms] New comment on issue #2944: server crash when going through a nether or end portal
Okey, my bad, pretty new on this and the crash error shows something about LuckPerms + only OP players can go through nether/end portal
The same with LuckPerms 5.3.3. Chunky's author says this is a LuckPerms issue (https://github.com/pop4959/Chunky/issues/72)
Description
Hello, I am using the plugin "JPremium". This plugin is for premium/cracked authentication. Premium players can join with no logging etc... I found this bug with Luckperms, when I remove myself from the JPremium database (premium account), then register... LuckPerms will not recognize my UUID and I have no groups, perms, etc. I think it is caused by LuckPerms, any other plugins using UUIDS like SkinsRestorer are okay with that. I think it is also when the premium player chang...
Hello, I'm trying to get Prefix of Player with LuckPerms API.
I tried this: user.getCachedData().getMetaData().getPrefix();
and it provides an NPE on this line.
Thanks - although I should also say: really it would be sensible to actually find the root cause of this problem instead of patching usages of methods which should be working.
Chances are there will be other plugins (silently) failing because of this, which is obviously not good!
Thank you, went with slightly different wording: 0f63b024e42f82d2808eaea15833cefc9fca2c47
I imagine
useris probably null.https://luckperms.net/wiki/Developer-API-Usage#obtaining-a-user-instance
I tried this, but I have same problem
Thanks - although I should also say: really it would be sensible to actually find the root cause of this problem instead of patching usages of methods which should be working.
I totally agree, however Oracle javadoc states that getPackage is nullable.
Yes, but there is no good reason for the information to be intentionally excluded, so I imagine it is a bug in Mohist / whatever.
Thank you, went with slightly different wording: 0f63b02
Much shorter, nice clear and easily to understand. Thx
[lucko/LuckPerms] Issue opened: #2948 LuckPerms stopped commands sent by RCON in the latest builds\.
Updating to a newer version actually caused my bug.
Description
Using Build 5.2.76 my SMS Scripts that use RCON to connect to servers and add ranks etc worked fine, but when I updated to 5.3.3 LuckPerms didn't add any ranks anymore (RCON still worked fine). Seemed like LuckPerms was straight up ignoring anything sent by RCON. Adding ranks by hand still worked.
Expected behaviour
I expected it to work the same as previous build. Did also test 5.3.5, but it was aff...
Hello. I am making a plugin for BungeeCord, which needs to get a list of all players in a particular group (including offline players). I did not find this function in the API. A similar situation is described here: spigotmc.org/threads/417525
Earlier, to solve my problem, I use the implementation code of the command /lp group \ listmembers
(copy-paste from me.lucko.luckperms.common.commands.group.GroupListMembers with some reflection).
This was qui...
You can use the UserManager#searchAll(NodeMatcher) to find all users having the InheritanceNode representing the group. Check out the factory methods for NodeMatcher to see how to create one and pass to the searchAll method.
So this is my solution. Ugh, it took about an hour to figure it out. It should be keep in mind that this method should be called asynchronously, since it loads data directly from storage (disk, database, etc.).
However, I think it would be great to see a simpler solution to this question in the API - I'm not the only one who needs this feature.
private List<User> getUsersInGroup(String groupName) {
LuckPerms api = LuckPermsProvider.get();
Group group = api.getGroupManage...
this method should be called asynchronously, since it loads data directly from storage
So would a possible Group#getMembers() method? Users aren't magically loaded into memory already.
this method should be called asynchronously, since it loads data directly from storage
So would a possible
Group#getMembers()method? Users aren't magically loaded into memory already.You would still need to loop through all members to add the node you want etc.
This problem can be solved by returning CompletableFuture. Or by passing Callback/Consumer to the method. There are many options...
UserManager#searchAll already returns a CompletableFuture...
Is there a reason why you need a User object for each of them and not just a UUID?
A bit more performant.. will load users in parallel.
I'm not sure whether this is something that I want to include as a utility method in the API itself - loading users is an expensive operation (relatively compared to the searchAll call) and so you should only do it if you really do need more than a UUID.
private CompletableFuture<List<User>> getUsersInGroup(String groupName) {
NodeMatcher<InheritanceNode> matcher = NodeMatcher.key(InheritanceNode.builder(groupName).build...
A bit more performant.. will load users in parallel.
I'm not sure whether this is something that I want to include as a utility method in the API itself - loading users is an expensive operation (relatively compared to the searchAll call) and so you should only do it if you really do need more than a UUID.
Yes, I need exactly the User meta data.
But if we talk about the API, I think that getting the UUID will be enough. After receiving the UUID, everyone will be able to load us...
It looks like there is a conflict between chunky pre gen and luckperms
Minecraft 1.16.5 usa jdk 11 se não me engano.
Same problem on java 11, chunky dev says its luckperms problem not his code
I want to clarify that I do not mean to assign blame here - it is entirely possible that this is not a problem in either mod. When I looked into this issue on my side, I could not find any conflicting classes. However, I was able to confirm that this only occurs when both mods are installed.
For the time being, a suitable workaround is to install Chunky and pre-generate your world, and then remove it before installing LuckPerms. Obviously less than ideal, but there isn't a suitable alterna...
LuckPerms doesn't modify the chat directly.
Yes - you are correct, these features do not work with each other.
You need to pick which one you want to enable - I don't see what the bug here is?
The "spam" in your console contains valuable information about what the problem is, and likely also hints what to do to fix it. I don't know why you would want to remove that... :)
Sounds strange, unfortunately without more detail there is nothing I can do to help / potentially fix any underlying issue.
If you want something with a little more reliability, I suggest setting up a "proper" database - MySQL or something like that.
Hey - sorry I actually implemented this a few days ago but forgot to reply here.
It's not an API method - but it will let you achieve the same thing: https://github.com/lucko/LuckPerms/commit/53bb61f9b25af8cc2588ef311ee3b8b8d18573fc
You can use System.setProperty to control this programatically.
I cannot reproduce this after setting the allow-invalid-username setting and restarting the server.
Could you provide some screenshots of what you mean?
It's fine to ignore the error - it just means that the command took a little longer to execute than expected.
- Please follow the issue template.
- Please read the issue template - it makes it very clear that you should try updating before reporting an issue.
Closing as duplicate of #2880

I cannot reproduce - probably a bug with your server / terminal app.
Thanks for reporting, this should be fixed by the above commit
This is definitely not an issue with LuckPerms, you need to speak to the author of JPremium - sorry, not much I can do to help.
I think it's best if we leave this out of the API itself for now - of course the code I posted above will work for the time being.. if more people run into the same complication we can reconsider :)
The fix is to explicitly define archivesBaseName on multi-module projects.
Both LuckPerms & Chunky were not doing this - and both called their Fabric module fabric, resulting in a conflict at runtime due to the name of the Mixin refmap file.
This should be fixed in the latest versions of each :)
Description
hi is it possible to add a negative value for the accumulate temporary modifier so you can reduce the duration of the permission instead of adding a duration? Right now, it is only possible to add a duration to the timer and im hoping i can reduce timers in the future. this would be useful for servers with large playerbases as doing it manually would be way too time consuming.
Proposed behaviour
e.g. /lp user (player) permission settemp (perm node) false (negative...
The removetemp command accepts a duration argument 😛
/lp user <player> permission unsettemp <perm node> 1d will subtract 1d from the expiry time of the node.
Description
Short report, as there is almost no support on Discord. Since the last LuckPerm update, my console commands no longer work.
Serverversion:
This server is running Paper version git-Paper-562 (MC: 1.16.5) (Implementing API version 1.16.5-R0.1-SNAPSHOT)
You are running the latest version
Previous version: git-Paper-526 (MC: 1.16.5)
LuckPerm version 5.3.0
Commands:
- '[console] lp user %player_name% permission set test.test1'
- '[...
Sir William, the post was not long ago. 12:44 :)
But in this issure are more details.
The logs just indicate that your server is struggling to keep up with LuckPerms command executions (they happen one after the other in the order in which they were executed)
I assume the commands do eventually go through?
Are you able to reliably reproduce the problem?
The problem is that no player can join the server when the problem occurs.
I always have to restart the server. The following commands (luckPerm changes) are not saved.
Yes, whenever my player group changes their race. Then many permissions are changed.
As far as I know, this happens with the latest 3.5.0 version. I will patch back today or tomorrow.
The problem is that no player can join the server when the problem occurs.
This would indicate that the problem is probably more significant than just LuckPerms.. the LP command queue getting stuck is one thing, but that wouldn't (shouldn't) prevent players from connecting to the server.
More likely you have a thread / CPU starvation problem which is resulting in the server not responding.
Description
Hi, I had a big tps drops when changing world, it took almost over 800ms. I thought it was due to Jobs plugin, but there's something that could be improved in LuckPerms, look here https://github.com/Zrips/Jobs/issues/1113#issuecomment-803400931.
Reproduction steps
- I was using PlayerWorlds plugin, but maybe isn't neccessary.
- Then I've changed world.
- Then I saw big tps drops in spark (you cansee here report for Jobs plugin https://github.com/Zrips...
Looking at the code, I see that in the ChildProcessor class, in the overwritten "refresh" method, it iterates over all the child permissions to update the existing ones according to the Spark report. For this, I suspect you have set a lot of permissions on the database? Usually it is the case that a user has a lot of something and it takes a long time for the CPU to load those elements.
https://github.com/lucko/LuckPerms/blob/6b2c4bca58df120c67ba6...
Should be improved by the above commit - although I have a feeling your lag problem actually isn't being caused by this (number of samples is quite low, it's hard to tell).
If the problem continues, it may be worth sampling at a higher accuracy - include the --interval 1 flag.
Description
I need to get the expiration date of the group.
Proposed behaviour
It should be obtainable using PlaceholderAPI.
Have you tried checking the placeholders page in the LuckPerms wiki? There is one for it, the very last one listed https://luckperms.net/wiki/Placeholders#luckperms_group_expiry_time_group-name
Yes, it is, but this is the remaining time until expiration. I would appreciate if it was possible to get an expiration date.
Ah I see what you mean. The suggestion would be best fitted in the LuckPerms/placeholders repo to keep track of it there :)
I don't know exactly. In any case, I patched the old version. Now everything works again. (LuckPerm 5.2.76)
The 20 commands are executed instantaneously without the server getting problems.
Could you try using 5.3.11 - https://luckperms.net/download
Let me know if that is any better, I've added a patch that may improve the situation :)
Just an extra note: You may find some TODOs in here, which are mostly due to lack of support for something in Krypton at its current stage. I will add those later when I add support for them in Krypton.
Hey, this is cool! Thanks for submitting as a pull request, I've had a look through your code and it looks good to me.
I am aware that this is a very, very small platform, and that this will likely be unused by a majority of users
Unfortunately, this is a big blocker in terms of having support for Krypton merged directly into LuckPerms. No matter how amazing a platform is, it isn't worth the maintenance burden if it is only going to be used by a relatively small amount of people.
...
Okay, thanks lucko! Yes, it was an enjoyable one. I released like 8 patches in a day to the server just to make this work haha. I'll maintain this in my fork for now, as you suggested, and if the platform becomes more popular, and it becomes worth it to merge this, I'll let you know.
Sounds good, thanks for understanding :)
Description
A placeholder that will only display the color of a placeholder
Proposed behaviour
Let's say that you have a VIP role with the prefix &a[VIP]. This placeholder should now only take the color and ignore anything else then color code.
Use meta:
/lp group vip meta set color &a
Then use placeholder: %luckperms_meta_color%
It doesn't work with the version either.
[00:21:46 WARN]: [LuckPerms] Command execution [user, Adurien, permission, unset, adurath.volk.halblinge] has not completed. Trace:
java.base@11.0.10/jdk.internal.misc.Unsafe.park(Native Method)
java.base@11.0.10/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
java.base@11.0.10/java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:885)
java.base@11.0.10/java.util.concurrent.locks.AbstractQueuedSynchroniz...
Can you upload your full log?
Ah ok, I think I see what the problem is.
Could you try again using v5.3.12 :)
Now it works, but there is still an error.
`[09:59:29 INFO]: [LP] Another command is being executed, waiting for it to finish...
[09:59:29 INFO]: [LP] Another command is being executed, waiting for it to finish...
[09:59:29 INFO]: [LP] Another command is being executed, waiting for it to finish...
[09:59:29 INFO]: [LP] Another command is being executed, waiting for it to finish...
[09:59:29 INFO]: [LP] Another command is being executed, waiting for it to finish...
[09:59:29 INFO]: [LP...
Description
I setup a Bungeecord network and MySQL server and also setup MySQL in Luckperms (in the config of each server).
The database is working but I have one problem:
when I created a group with lpb creategroup name and then tried to use lp group in one of the spigot servers the group didn't appear in the list.
Reproduction steps
- Setup a Bungeecord network and MySQL server.
- Setup MySQL in luckperms config in each server.
- Create group in the bungeecord server w...
Alright, 3rd time lucky... please try with 5.3.14 :)
Is it listed in /lp listgroups after running /lpb networksync?
What is sync-minutes set to in your LP config? Both in the server and proxy.
Description
Trying to replace/accumulate a temp meta node on top of an existing one results in command failure because "Player already has temp meta".
Reproduction steps
- Set a temporary meta node
- Try setting it again on the same holder with
accumulateas temporary modifier - It no work
Expected behaviour
I would expect it to:
- If using
accumulateto add the time to the existing node - If using
replaceto, well, replace the expiry time.
#...
[lucko/LuckPerms] New comment on issue #2957: 'meta settemp' ignores the provided temporary modifier
Merged your PR, thank you :)
I'm not interested in continuing it this time. Someone else may pick this up.
Is it listed in
/lp listgroupsafter running/lpb networksync?What is
sync-minutesset to in your LP config? Both in the server and proxy.
Yes It is listed.
The sync-minutes set to -1.
Also this is listed without /lpb networksync.
it dosen't appear in the tab complete but still working.
My Problem is with the tab complete in commands that have groups list in tab complete.
No problem, thank you anyway :)
OK, the Floodgate rewrite is finally out for testing. However, with the suggestion Lucko proposed, the changes in Floodgate 2.0, and me not wanting to deal with merge conflicts. I'm going to close this and make a new PR soon.
This is because LP does not send update changes when creating a group (it sends the action logging but not the actual "hey this group has updated" message) and I noticed that running /lp listgroups does "fix" it since it reloads the groups list.
Not sure why Luck decided to do it this way? I want to know what his thoughts are.
For reference (no messaging service update and same applies for other group-changing events like the deletegroup command):
https://github.com/lucko/LuckP...
This is because LP does not send update changes when creating a group (it sends the action logging but not the actual "hey this group has updated" message) and I noticed that running
/lp listgroupsdoes "fix" it since it reloads the group list.Not sure why Luck decided to do it this way? I want to know what his thoughts are.
For reference (no messaging service update and same applies for other group-changing events like the
deletegroupcommand):
https://github.com/...
That's not ideal... if you're going to make a custom plugin anyways I suggest you use the LuckPerms API and listen to the GroupCreateEvent and GroupDeleteEvent and [push updates through the messaging service](https://javadoc.io/doc/net.luckperms/api/latest/net/luckperms/api/messaging/Me...
This is hardly a critical bug that renders the plugin unusable...
I will create a plugin that will run lpb networksync command every second to fix that.
Please don't 😅
Resolved by the commit above.
Yes it works fine. Thanks. One more Question.
Is that still normal? In the past, this display did not come up, but immediately the output.
[00:34:06 INFO]: [LP] Another command is being executed, waiting for it to finish...
[00:34:06 INFO]: [LP] Another command is being executed, waiting for it to finish...
[00:34:06 INFO]: [LP] Another command is being executed, waiting for it to finish...
[00:34:06 INFO]: [LP] Another command is being executed, waiting for it to finish...
[00...
Didn't fix
Description
Without too many words, i applied manually litebans and other plugin permissions (since luckpermsbungee wasn't detecting it as normal) and still wasn't working.
Reproduction steps
Just download a plugin bungee side, luckpermsbungee and setup manually permissions (since they will not appear)
Expected behaviour
I expected that permissions will show as normal like luckperms bukkit but they didn't work.
Environment details
W...
Without too many words
Definitely not enough words, definitely.
Please close this and fill out the issue form in full, with detailed descriptions and all fields complete. Thanks.
This would be due to BungeeCord not providing a way to explicitly register permissions I believe, not an issue with LuckPerms Bungee.
Yes - that's normal.
Great that the issue is fixed!
A closing comment from me: ask yourself, is it necessary to run so many commands at once? If you are assigning lots of permissions to a user, it would be better to add those permissions to a group, then just execute one command to add the group to the user.
For example, if you want to routinely give permissions:
essentials.ban
essentials.mute
essentials.fly
to a user.
Instead of running
/lp user {USER} p...
when i use the prefix.1000.[Rank] in chat i just get:

the issue template just goes… poof. Please follow the issue template, it will help a lot in trying to debug your issue. Tho that being said, ensure you have vault and a chat plugin installed for prefix to work.
Mine just says the version every time I do /lp help or any command
@SpooksxAce-op that's because you need to follow this guide carefully: https://luckperms.net/wiki/Usage
In future, do not reply to closed issues and ask trivial support questions in the LP discord if possible, at https://discord.gg/luckperms
Thanks
@LaganDevs these links may be useful, but the issue will be closed because you did not follow the carefully crafted template.
In short, LuckPerms does not perform any chat formatting of its own.
LuckPerms only acts as the source for prefixes / suffixes, it doesn't actually apply them. You need an appropriately configured chat/tablist formatting plugin for them to be displayed. If the values appear correctly when you run /lp user <user> info, LuckPerms is doing its job!
This will help...
When the fabric version luckperms executes the / LP group default permission set command, it does not have the original permission after the set.


Mod version is 1.16.4 fabric
The server version is 1.16.5
As far as I can tell, fabric does not implement any form of permission checking for vanilla commands at the moment. So the only way to control is by giving OP for now.
As far as I can tell, fabric does not implement any form of permission checking for vanilla commands at the moment. So the only way to control is by giving OP for now.
But why did the author publish the fabric version? Isn't that meaningless? So how can we solve the problem of the plug-in permissions, except Op.
这取决于面料,而不是运气。
OK, thanks. I will wait for version 1.16.5 to come out and I will try again. If it still doesn't work, it will be really bad.
Is it also possible to autodetect any issues?
This is only for the easy to fix issues. This to solve a lot of frustrations and discord talk.
This can detect for example conflicting perm-plugins, conflicting config options and more.
This detecting can also in discord with the bot, I thought I've seen this in other discords (DiscordSync). This saves a lot of time for the helpful people
My current idea for this is just a simple /lp dump that dumps into bytebin a whole lot of info about both LuckPerms and the server, not any kind of auto-detection system or anything of the like; this would include the LuckPerms config file (excluding of course any kind of sensitive information), the data collected in /lp info (database ping, groups & users count, server name and brand, etc.), an editor link, a plugins/mods list, server info (mainly online-mode and bungeecord if on spi...
It would be beneficial to provide this info in the editor payload as well, since thousands of people use it every day, it would be a great opportunity to provide users with any extra info that could help them resolves any issues they might not even know they have.
I personally recommend adding a time-limited track function, which has the same meaning as time-limited permissions and time-limited inheritance groups, that is, after the time is up, the track will automatically be downgraded by one level, and if not, the track will be automatically kicked out.
Description
We have encountered a rather strange bug that happens every 3-4 months. After a scheduled reboot we found that all LuckPerms data has been deleted.
Reproduction steps
It is complicated to reproduce. According to our research it seems that when the database connection is restarted and closed and just at that moment a user tries to log in there is a thread that tries to make a query and fails.
. A people with non premium minecraft cant join on my server, where i have spigot 1.8.8 and offline mode. Luckperms giving a notification about pre-login and i don't know what i have to do. Luckperms when starting a server giving info, that is CraftBukkit - Bukkit but i have spigot.
Server: CraftBukkit version git-Spigot-21fe707-e1ebe52 (MC: 1.8.8) (Implementing API version 1.8.8-R0.1-SNAPSHOT)
LuckPerms version: `5.3.1...
Having the ability to write a promotion and a new time would make this amazing. You could have a promotion level (progression along the track) and a duration. So that way you could easily temp promote someone using the same command.
There would need to be a decision about making a marker for the player's base rank or just making a new track to use for this system.
Example:
Default->User->VIP->VIP+
/lp user tavies temppromote track1 1m
Using the command the first time would promote ...
We have already updated and the problem remains. What's more, it happens more frequently now.
[lucko/LuckPerms] New comment on pull request #2965: Exciting and long\-overdue changes to LuckPerms
cant wait so exciting thats dope dude
Description
I have seen instances in support that ppl doing something like /lp user ben permission set permnode true. Notice the 2 spaces between set and permnode? It cause it to set a empty permission node with context server=permnode and world=true
Reproduction steps
- Run any permission set command like this:
/lp user ben permission set permnode true - And empty permission with weird context is set.
Expected behaviour
I suggest disabling the abil...
Did your server crash or you forcefully shut it down before?
The player#hasPermission method it's returning false for temporary permissions.
` if (!player.hasPermission("essentials.fly") || !player.hasPermission("superior.island.fly")) #this check here works{
player.sendMessage(this.getMessage("no-permission"));
return true;
}
if (player.hasPermission("essentials.fly")) #this check doesn't work {
this.getServer().dispatchCommand((CommandSender)player, "essentials...
assuming the code is order as how you show it, how can hasPermission in the first if condition work, but suddenly the next if condition it returns a different value? Unless the code were pasted from different parts of your project?
I feel like your a flaw logic rather than player#hasPermission not working.
For it to even reach the second if condition, both essentials.fly AND superior.island.fly needs to be true. Furthermore, this will result in it being completely impossible to reach the third if condition, since at the point, essentials.fly will definitely be true and it will break out at the second if condtion.
It doesn't work for other conditions because it's checking if they have the permission node. They do have the permission node but it's assigned temporarily.
ok.. but whether its temp or permanent they still have that perm and player#hasPermission should return the same result. If you think otherwise, you will have to provide evidence showing the issue (e.g. logging of the player#hasPermission result).
[lucko/LuckPerms] New comment on pull request #2965: Exciting and long\-overdue changes to LuckPerms
Thanks for your valuable reviews and critiques.
We've decided that it is best if we take this idea back to the drawing board, and will get back to you all (perhaps in a years time) when we have a new version for consideration.
Happy April 1st :)
Description
When I type "/lp editor" in game or console I get the following error every single time:
https://haste.olziedev.com/icaweyapid.yaml
and it takes about 5 minutes for the command to show me the editor link
Note I'm using the same mysql for my survival servers, at first I used the same mysql for also the bungee luckperms, but I then changed it to only use the same mysql for the paper servers.
Reproduction steps
- type "/lp editor"
Environment det...
Check that whatever computer running your mc server can access https://bytebin.lucko.me/. If you are using a hosting service, I suggest you contact them.
In addition to what @benwoo1110 suggested, please also ensure that the ping from the server to the database is not extremely high, as that can easily cause this issue.
In the meantime I use LuckPerms in conjunction with player-roles-fabric, they seem to work fine together, but both have their own roles and permissions system. I couldn't find a fabric mod that enables minecraft.commands.* permissions to be managed with LuckPerms as a central system.
Hey, interesting idea!
I think for now I want to keep track promotions for permanent groups only. Of course, you can still add specific temporary groups using parent addtemp - or implement this functionality yourself using the API!
Things I can think of:
- Ensure your server has plenty of free disk space
- Ensure that when the server shuts down, it does so gracefully (doesn't force exit)
- Ensure that only one server is being ran in a given directory at a time
Failing that, it might be worth switching from H2 to a remote database like MySQL. There's a guide on the wiki that explains how to do this :)
Check with the verbose command if you're still not sure, but as Ben said I suspect this is flawed logic in your code as opposed to a bug in LP.
Your database is being slow to respond, most likely a problem with that as opposed to with LuckPerms.
Though not overly complicated, when using the parent addtemp, having to remove the temp before re-adding it to renew the time rather than it overwriting seems like an extra step (though I can see it making sense if the time is less). My thinking with the temppromote could simplify rank changes as well as upgrades using a single command.
As the name of the setting suggests, you need to "be member of the group" / inherit a group to be able to edit it, this also applies to which groups are uploaded to bytebin when you run /lp editor. The groups are still there and their permissions are still there, but the editor will not upload the groups you do not inherit (at the time of running /lp editor).
Also as for the backing reason why you set it to true in the first place (which there was no need) you want to set up argument based permissions to let other people use LuckPerms but in a very limited way based on the actual arguments passed to the commands (group name, track name, contexts, etc.).
As I'm thinking of the best way to implement this for Floodgate 2.0, I do have a question - why is allow-invalid-usernames a setting that defaults to false? Hypothetically, should that setting be removed and/or its true behavior being the standard, then Floodgate support is of no concern.
Description
When i set a temp group or permission it changes to a perm group or permission sometimes when switching servers on bungee
Reproduction steps
It just happened randomly
Expected behaviour
The permission not to turn perm
Environment details
- Server type/version:
Paperrunning version1.16.4build416 - LuckPerms version:
v5.3.17
Ill post if needed, im in a rush
Any other relevant details
None
In the meantime I use LuckPerms in conjunction with player-roles-fabric, they seem to work fine together, but both have their own roles and permissions system. I couldn't find a fabric mod that enables permissions to be managed with LuckPerms as a central system.
Oh,thank you very much!Have you tried 'minecraft.commands.*' alone in LuckPrems before and did it work?
Description
Could not pass event PlayerJoinEvent to LuckPerms v5.3.17
java.lang.IncompatibleClassChangeError: Found interface us.myles.ViaVersion.ViaManager, but class was expected
Reproduction steps
- when player login in server
- See error
Expected behaviour
Environment details
- Server type/version: Paper
running version1.12.2build1618` - LuckPerms version:
v5.3.17
Any other rele...
I tried to use minecraft.commands.ban and minecraft.commands.whitelist in LuckPerms for Fabric, but that didn't work. benwoo1110 is right, I looked into the Minecraft code and indeed this is just a Spigot thing.
Also see these Discord messages about the same issue: #789953494534324264 message
Viaversion, Viabackwards, Viarewind, Protocllibare latest dev builds.
Is this reproducible on latest stable for these? This looks like an issue on their end, not LP.
I think I have seen this before, it's probably due to their latest dev build having API breakages since the release version works from what I know.
this adds 3 lines too many for a fefo pr. wtf.
Description
Luckperms config folder is now located within the mods folder, rather than the config folder. It ignores the existing configs in configs/luckperms, and creates a new folder at mods/luckperms.
Reproduction steps
- Install LP 5.3.9 on a fabric server
- Start server
- Open mods folder to see a new luckperms folder populared with files.
Expected behaviour
In LuckPerms 5.2.29, LP created and used the configs located at config/luckperms. I believe it ...
Description
Running the command /lp editor takes a really long time to execute (about 2-5 mins).
Reproduction steps
- Open the config.yml file, set storage-method to MySQL, fill out the rest of the necessary fields
- Restart the server
- Run /lp editor
- Nothing happens, then after a few seconds errors appear in console
Expected behaviour
A web editor link is generated in a few seconds.
Environment details
- Server type/version:
Tuinity...
what about any of the other commands that send data to bytebin, e.g. /lp tree /lp verbose record (then /lp verbose paste) or /lp export --upload ?
You're absolutely right, thanks for the detailed bug report! :)
I've made some changes which should make this process faster (and therefore not cause the warning to be printed)
If there are still issues, then it is likely just down to your MySQL server being a little slow.
I'm gonna need some more details in order to look into this for you.
Could you perhaps provide some screenshots of what you mean? I can't really follow your explaination.
Description
There is a state that a User has no Group not even the default group.
Short Conversation on Discord: #luckperms-api message
Reproduction steps
final var uuid = plugin.getUUID(sender); // Get UUID from CommandSender
LuckPermsProvider.get().getUserManager().modifyUser(uuid, user -> user.data().clear(NodeType.INHERITANCE::matches)).thenAccept(v -> {
final var groups = LuckPermsProvider.get().g...
When luckperms does .hasPermission(permission), it gets a null pointer exception
Hello, this is what im meaning:
The group with the expiry added onto it didnt actually work as afew minutes later when switching servers it added one that has no expiry https://gyazo.com/04479c9ae58ef01ff912e15c1bdfe960
Description
08.04 15:24:36 [Server] ERROR java.lang.IllegalStateException: zip file closed
08.04 15:24:36 [Server] WARN java.lang.IllegalStateException: zip file closed
08.04 15:24:36 [Server] WARN at java.util.zip.ZipFile.ensureOpen(ZipFile.java:686)
08.04 15:24:36 [Server] WARN at java.util.zip.ZipFile.getEntry(ZipFile.java:315)
08.04 15:24:36 [Server] WARN at java.util.jar.JarFile.getEntry(JarFile.java:240)
08.04 15:24:36 [Server] WARN at java.util.jar.JarFile.getJarEntry(JarFile...
Attach a list of the other mods you are using and what platform/version(bukkit/paper/spigot/fabric)
1.Advanced Enchantments
2.Better RTP
3.Chat Filter
4.Clear lag
5.Discord SRV
6.Dead chest
7.Enjinminecraftplugin
8.essentials
9.head drops
10. Holographic disaplays
11. jobs
12.Luckperms
13.Matrix
14. ShopGUIplus
15. Silk spawners
16. Single Player Sleep
17. world edit
18. world guard
19.mcmmo
JAR file- Paper-1.16.5-584 <----- Build#
If you remove LuckPerms does it all work?
we switched to luckperms and paper last night. None of these areas were here before luckperms
we initially switched because some permission didn't work with group manager but luck perms fixed it. Then all of these errors were showing up
- Please don't dismiss the issue template, it's there for a reason, it helps everyone help faster, even yourself.
- You didn't list all your plugins (you clearly have ProtocolLib according to the stack trace, something you didn't list)
- Please use a paste site such as https://paste.lucko.me/ to paste logs and errors
- Please provide all kinds of information that could be useful (entire server log, LP version, LP config, etc)
so what else do you need?
Description
I want to set up a disallowed permission on a context. I this style command:
/lp user PietElite permission set my.command false my=context
I can see my context my=context listed in the context list with:
/lp user PietElite info
I can see that my context is working correctly (showing false) by running
/lp check PietElite my.command my=context
However, when I turn on /lp verbose and I perform the action that should be denied, it still works an...
You are in a bit of an old version, I suggest you:
- First try updating see if that fixes the issue
- If it doesn't, share screenshots of
/lp info,/lp user <user> info,/lp user <user> permission check <permission>and a/lp verbose uploadURL too.
You are in a bit of an old version, I suggest you:
- First try updating see if that fixes the issue (https://luckperms.net/download)
- If it doesn't, share screenshots of
/lp info,/lp user <user> info,/lp user <user> permission check <permission>and a/lp verbose uploadURL too.
I've updated the issue with those notes
Hm looks like registered/non-stock contexts are not being considered in the real permission calculation.. at all? That's what verbose suggests compared against the permission check command result.
I vaguely remember noticing this before so it's not new either, thanks for all the info!
I tried to use and in LuckPerms for Fabric, but that didn't work. benwoo1110 is right, I looked into the Minecraft code and indeed this is just a Spigot thing.
Also see these Discord messages about the same issue: #789953494534324264 messageminecraft.commands.ban``minecraft.commands.whitelist
Thanks for your help! As you said before, luckperms and player-roles-fabric will work together. Will player roles fabric work alone?
this is the template. you should have seen it as you were making the issue.
Will player roles fabric work alone?
Yes, the player-role-fabric mod can function independently. It is an alternative to LuckPerms. These two mods do not interact/integrate with each other, but they are compatible and the permissions stack. I've installed both because I want to use LuckPerms were possible, and only use player-role-fabric for the vanilla commands which LuckPerms can't control.
Description
I just updated the plugin from 5.2.106 to 5.3.21, and find out commands that worked before are not working now.
In version 5.2.106, /lp commands cannot be used in command blocks directly, but can be used with the PsudoCommands plugin.

; not entirely sure if this is intended or not.. I'm curious as to what Luck thinks.
What you can do for now is set that setting to true.. that's the only way to get it to work.
Same here with LuckPerms v5.3.21 on Waterfall build 405.
The following exceptions are being spammed over and over again when a user joins and plays on any server:
[12:29:49 WARN] [LuckPerms]: An exception was thrown by me.lucko.luckperms.bungee.context.RedisBungeeCalculator whilst calculating the context of subject Galexrt
java.lang.NoClassDefFoundError: com/imaginarycode/minecraft/redisbungee/RedisBungee
at me.lucko.luckperms.bungee.context.RedisBungeeCalculator.calculate(Redis...
Bulk edit is a very dangerous operation that should not be done by automation or without confirmation.
May I ask what is your use case that requires the confirmation to be removed ?
I don't know the java language but with cmi and luckperms I can do a lot of different features, with permission I can track and manage them for the players. So I can make a point through cmi portals to which the player will capture it, only he will be given a special permission, and everyone else will ...
Thanks! The command block can run lp commands (with or without psudo) after setting commands-allow-op to true. However, it worked before in version 5.2.106 with commands-allow-op: false so I'm not sure if it's considered as a bug or not.
What changed is how and what LuckPerms considers a command sender "console", this changed for security reasons as players could take advantage of a network exploit and LuckPerms would consider them to be "console".
Now LP considers console in a safer manner, this is something that can easily be changed to allow command blocks in.
think I have the latest 5.3.3
Description
org.bukkit.plugin.InvalidPluginException: me.lucko.luckperms.common.loader.LoadingException: Unable to create bootstrap plugin instance
Reproduction steps
- make a server using mohist 1.12.2
- add a som mods(think this is none important tho)
- start the server
Expected behaviour
the plugin should get loded and work
Environment details
- Server type/version:
mohistrunning version1.12.2build `...
Forge + Bukkit servers are not a supported server platform.
Feel free to paste in gist the entire server log (/logs/latest.log) for additional details (maybe it is something fixable), but there is absolutely no guaratee it will work.
now I have added the log
I see you are running SpongeForge + LuckPerms for Sponge, please don't use the Bukkit version of LuckPerms if you are using the Sponge version.
On another note you shouldn't be using Essentials, you should be using Nucleus which is also a Sponge plugin, but that's another topic not related to LP.
Hi i removed the sponge version of luckperms and now I get the luckperm logog in the consol, /lp works to
Description
Reproduction steps
- Open the config.yml file and set example to true.
- Restart the server
- Run /lp user example permission set x from the console
- See error
Expected behaviour
Environment details
- Server type/version:
ExampleSpigotrunning version1.12.2build??? - LuckPerms version:
v???
Any other relevant details
I have 0 idea what the issue is. Fill in the issue template in detail if you wish to get any help.
Description
Java 16 issue with doing commands in game
Bungee cord version : 1.16-R0.5-SNAPSHOT:a7c6ede:1549 by md_5
paper version : git-Paper-586 ( MC : 1.16.5)
- LuckPerms version: `v5.3.21'
This is after typing command /lpb editor.
lp commands seem to work so it appears to be a proxy issue. lp editor in the paper servers console also works.
/lp editor in game also appears to work just not /lpb editor
Same here. Thought it was due to the switch to Docker but seems to be a general problem
[03:10:01 INFO]: [LP] Running LuckPerms v5.3.3 by Luck.
[03:10:01 INFO]: [LP] - Platform: BungeeCord
[03:10:01 INFO]: [LP] - Server Brand: Waterfall
[03:10:01 INFO]: [LP] - Server Version:
[03:10:01 INFO]: [LP] git:Waterfall-Bootstrap:1.16-R0.5-SNAPSHOT:004e802:406
[03:10:01 INFO]: [LP] - Storage:
[03:10:01 INFO]: [LP] Type: MongoDB
[03:10:01 INFO]: [LP] Ping: 4ms
[03:10:...
No, the server did not crash when it was restarted.
We were using H2 storage, switched to MySQL and so far it hasn't been a problem.
Hello,
My suggestion is for a command to be added for ranking up to a specific rank.
Here's an example:
The Rank Track:
Default -> Member -> Sr. Member -> Mega Member
I have vouches implemented into my server so there's the ability to claim a rank that's lower than their current rank:
Example:
Default gets Mega Member rank, uses the voucher, and gets Mega Member rank.
Mega Member gets Member rank and uses the voucher, would be demoted to Member rank.
If possible, could a tr...
I am getting a me.lucko.luckperms.lib.mongodb.MongoSocketException please help
Can you upload your logs/latest.log file to a paste site like https://paste.lucko.me/? Also next time please follow the issue template, it's there for a reason.
I feel like this is a very specific use case that you either should trigger a promote/demote command on voucher usage, or use the luckperms API and code a custom plugin to handle the behaviour to your liking.
OK, sorry. Here is the link: https://paste.lucko.me/wq9wUGhHhU
I reloaded several times
A few things, don't reload your server just restart read more here. Your host address is unknown, try using quirkycraft.ygqma.mongodb.net instead of quirkycraft.ygqma.mongodb.net/luckperms? If that doesn't work you'll want to contact your hosting for help with that.
I am using default mongodb hosting and I did try the other one
Description
Hi, when i put some hexadecimal code une permission prefix like prefix.50.&8● 	a4dff
When i update my perm i have some MySQL error in console :
Reproduction steps
juste put hexadécimal prefix in some group
Expected behaviour

Environment details
Debian 9
Spigot 1.16.3
java version "1.8.0_151"
Luckperm 5.3.3 and lastest vault and...
Description
Currently, I am unable to use the PlaceholderAPI ParseOther extension to return LuckPerms prefixes for players that are offline. I would like this to be possible, as it can really help. I understand reading a previous issue about offline placeholders that unless PAPI is async it wouldn't be added - however we would really appreciate the feature. Perhaps making it optional?
Proposed behaviour
Placeholders such as ``%parseother_{{username}}_{luckperms_prefix_eleme...
Description
Migrated my server from a SparkedHost server over to a dedicated server via r-sync, one of my developers added a PMA (PhpMyAdmin) during this. Everytime I try to give someone a permission group or permission it says its completed it but doesn't follow through with genuinely giving the permission.
Reproduction steps
Best way I can reproduce the error is simply just doing /lp user MrCaust permission set * and it replies with "[Thu, 15. Apr 2021 19:44:03 PDT WARN...
Description:
Context server = hub
Doesnt work for velocity commands.
Image:
image with explaination:
https://ibb.co/HH9Rk3f
Details:
Server: yatopia
Proxy: velocity
Java: 16
Windows 10
I have a problem with uuid player who logins premium account.I have a plugin that allows premium account, but I have this error
[13:22:27] [Netty Worker IO Thread #1/INFO] [LuckPerms]: Processing pre-login for fb23a81a-cd7f-49cb-b886-56faf0a0a840 - CrazyLegend_
[13:22:27] [Netty Worker IO Thread #1/INFO] [LuckPerms]: Processing post-login for bdd35907-83e4-3f50-8548-b8723d29120d - CrazyLegend_
[13:22:27] [Netty Worker IO Thread #1/WARN] [LuckPerms]: User bdd35907-83e4-3f50-8548-b8723d291...
Whatever login plugin you are using is altering UUID in a way that will cause UUID to change in an unexpected way. Ask your login plugin on it, or in fact, just do away with these type of janky login plugins.
Description
When I'm trying to connect LuckPerms on a MySQL database, its timing out... But when I connect LuckPerms to this same database in another server, it work succesfully.
Reproduction steps
- Open config.ylm file
- enter the database infos (username, password, etc..) and change storage-method to MySQL
- restart server
- See error
Expected behaviour
LuckPerms connects to the database and I can synchronize my perms on differents servers.
...
I cannot copy all the error, sorry... My GitBash is impossible......
It means I need to change my auth plugin, which can change uuid to luckperms database?
Caused by: me.lucko.luckperms.lib.mysql.cj.exceptions.CJCommunicationsException: Communications link failure
Your database just cant be access by your server, nothing much luckperms can do.
see https://luckperms.net/wiki/Storage-system-errors#luckperms-cannot-connect-to-my-mysql-server











