Replies: 25 comments 43 replies
-
|
I'd change the name to LuckyPerms |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for being courageous and finally speaking out about this issue. |
Beta Was this translation helpful? Give feedback.
-
|
I know way to many people who always call it LuckyPerms. Might be the easiest solution |
Beta Was this translation helpful? Give feedback.
-
|
Absolutely! |
Beta Was this translation helpful? Give feedback.
-
|
The permission check command only looks at specifically defined permissions, it would be helpful to have a version of it that factors in things like wildcard permissions. |
Beta Was this translation helpful? Give feedback.
-
|
I've had a go at implementing this!
So, what are we looking at here.. well:
All of this is now under one command instead of three, As for what the output shows.. well, we can see that there has been a misconfiguration! "luck", an admin, inherits the true version of the permission, but this is actually being overridden by the false setting in the default group. So, we probably need to setup some group weights!
The second screenshot shows some of the other processors in action - firstly the Bukkit defaults processor, then, after setting a wildcard for I think definitely an improvement over what we had before! |
Beta Was this translation helpful? Give feedback.
-
|
Looks awesome! |
Beta Was this translation helpful? Give feedback.
-
|
Also now includes relevant wildcard permissions!
|
Beta Was this translation helpful? Give feedback.
-
|
Awesome! This is exactly the kind of thing I was looking for and more! |
Beta Was this translation helpful? Give feedback.
-
|
Wow cool! |
Beta Was this translation helpful? Give feedback.
-
|
LuckPerms telling you it has an update, at the moment there isn't a system in place and you are pretty much reliant on reading #changelog for whenever an update comes. I feel like either some kind of message in console when the server boots saying you're using an outdated version or something could be nice. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah it would get annoying but it would be nice for the people who care to keep there plugins up to date or lp having an extension for auto updates that would just get installed whenever the server reboots. |
Beta Was this translation helpful? Give feedback.
-
|
im always extremely irritated by these update logs. Either you just dont see them anymore or they clog up your console and chat. |
Beta Was this translation helpful? Give feedback.
-
|
I think is good idea, I always at least 40+ versions behind because of this. But in config add setting "checkforupdate: "true or false"" . So if someone not like it you never see it. I even goo soo fare to say a ingame notis, is even better. But with only of you has luckperms.updatenotis all other plugin some has it ingame has a perm like this (I know some has * perm in lucky, but set it to false shall work if you not like it or you has the perm outside of normal luck.* perms, so you have to add this extra perm for see ingame notis). |
Beta Was this translation helpful? Give feedback.
-
|
100% agree with this, but with the option to disable in config.. so works for those who are for and against. |
Beta Was this translation helpful? Give feedback.
-
|
This is codes that used to make minecraft!? |
Beta Was this translation helpful? Give feedback.
-
|
I want the prefixes to appear above a players' head. |
Beta Was this translation helpful? Give feedback.
-
|
You can do that... With a name tag plugin. It isn't the job of LuckPerms to display prefixes anywhere. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, good point... |
Beta Was this translation helpful? Give feedback.
-
|
Velocity-global permissions. A way for different instances to communicate with each other using luckperms and hook into velocity globally. I use multiple different platforms for my network, and having that would be a lifesaver. |
Beta Was this translation helpful? Give feedback.
-
|
I assume by "different instances" you mean Bukkit, Sponge etc? |
Beta Was this translation helpful? Give feedback.
-
|
Mhm |
Beta Was this translation helpful? Give feedback.
-
|
I would've renamed it into FloofPewms (uwu) |
Beta Was this translation helpful? Give feedback.
-
|
-_- |
Beta Was this translation helpful? Give feedback.
-
|
Make the commands a bit easier (aliases?) for newcomers and market more on the /lp editor feature. I love luckperms but i have seen a lot of people struggling because they are not what you expect from other plugins. E.g. alias parent to group and make it more clear on the plugin page how easy the web editor is. |
Beta Was this translation helpful? Give feedback.
-
|
also: allow |
Beta Was this translation helpful? Give feedback.
-
|
I have a feeling adding more ways to do the same task will only confuse people more |
Beta Was this translation helpful? Give feedback.
-
|
full-on renaming would be worse for existing implementations so i feel like this would be the best "inbetween" option. But for the people ive had to help this was one of the major issues coming from pex/groupmanager |
Beta Was this translation helpful? Give feedback.
-
This will only make it more confusing with 2 different argument doing the same thing. Basing off your example, there is Also, this will get increase the amount to documentation needed for the added alias. |
Beta Was this translation helpful? Give feedback.
-
|
There used to be these aliases you spoke of in version 4 but they were removed in v5 with the following reason:
I'd also like to point out how ridiculous this command would be:
:P |
Beta Was this translation helpful? Give feedback.
-
|
I'd suggest a description database similar to ultra permissions that the community can update together. Then allowing a hover feature or some kind of feature to utilize this so that users don't have to go back and forth for perm descriptions. Also maybe a way to list all available perms from a plugin in the web UI. Having to type out each one, especially if there are a lot of perms in a plugin can get extremely tiresome. |
Beta Was this translation helpful? Give feedback.
-
|
the system they use to day, use some type of cache (when plugin sends perm checks). One thing should bee better is tabcomplete in editor, some not add the perm to the list (so you can edit it before you add it). |
Beta Was this translation helpful? Give feedback.
-
|
Personally I find it should be the job of the plugin developers to document their permissions properly. It shouldn't be LuckPerms' job to tell users what permissions are meant to do. Not to mentioned the absurd amount of work required to get this to function properly for most popular plugins. Also as @broken1arrow mentioned about permissions being cached - this means that your suggestion of the Editor showing only certain permissions from a plugin is not really going to work when the suggested permissions on the Editor is almost never a complete list. I agree that it can be hard to find the right permissions but maybe you should just try |
Beta Was this translation helpful? Give feedback.
-
|
I would implement a Tablistprefix System. |
Beta Was this translation helpful? Give feedback.
-
|
Unnecessary, when there are plugins that do this already and it's not the job of LP to display prefixes/suffixes anywhere. |
Beta Was this translation helpful? Give feedback.
-
|
Can't think of anything honestly! This plugin is already all I could ask for and more! |
Beta Was this translation helpful? Give feedback.
-
|
The possibility to give people permission to check certain groups instead off all groups. Like all groups that start with survival_ could be inspected with certain permissions. |
Beta Was this translation helpful? Give feedback.
-
|
This is likely already possible with a combination of Argument Based Command Permissions and Regex permissions. |
Beta Was this translation helpful? Give feedback.
-
|
The ability to export |
Beta Was this translation helpful? Give feedback.
-
|
Maybe even an online viewer 😉 |
Beta Was this translation helpful? Give feedback.
-
|
Ohhh yeah, nice idea. |
Beta Was this translation helpful? Give feedback.
-
|
I'm a little new to running servers, so this idea may not be smart, or maybe there is something I'm missing. I wish there were a way in LP to force nasty commands that do not have permissions to behave better. (I'm specifically thinking of WorldEdit, but there are a few others.) It there were a way to assign the command a permission and then allow LP to manage the custom permission, it would simplify my current process. Right now, I use a combination of command.yml (if I don't want it used at all) or PL-Hide to manage the permissions of the group that can use it. I tried using MyCommand, but I never could get it to work just right. As a next step, I would love a feature to alias commands and hide them and skip command.yml. Really, that's not LPs job, but it would make my life simpler being able to manage all that in one place. Again, LP has a lot of functions I know I'm not totally tapping into yet because it was too much to take in all at once. Maybe this can already be done and if so, yay! I would love to hear more about how you would go about it. edited typos |
Beta Was this translation helpful? Give feedback.
-
|
Add support for the pgup/pgdn (page-up/page-down) buttons to scroll in the web-editor. I'm someone who barly uses the mouse and try do as much as possible with the keyboard, mostly because the keyboard is a lot faster if you know what you're doing. But I just came to the conculsion that the web-editor doesn't support the pgup/pgdn buttons to scroll very fast trough the long list of permissions. I know the arrow keys are used to select one above or beneath, but I want something faster. |
Beta Was this translation helpful? Give feedback.
-
Which list do you mean, exactly? The group's/user's list of permissions, or the list in the dropdown menu when you add perms? You can use pg-up/down in the main window but you have to focus it first by clicking on a node. The "add node" permission list can't be focused due to the nature of the input component that's being used - I need to replace that with something a bit more usable but can't say when that will happen. More info on how you'd like to use the keyboard to navigate would be pretty good 👍 (I'd also recommend opening an issue on the lucko/LuckPermsWeb repo on the subject) |
Beta Was this translation helpful? Give feedback.
-
|
I mean the groups/users list of permission.
Besides that maybe the ability like scrolling with your mouse; when you hover the box you can control it with pgup/pgdn. |
Beta Was this translation helpful? Give feedback.
-
Hmm, yeah unfortunately that's a side-effect of the solution I used to minimise lag for users with thousands of nodes in a single group/user. Possibly I could fix it by putting space around the nodes where you can click without focusing on a certain node but still focus the list.
Sadly I don't think that's possible with how browser focus works. I'm sure I can figure something out though. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe the ability to add multiple permission nodes at once (in a single command). Kind of like worldedit does it where you separate them with commas. So like |
Beta Was this translation helpful? Give feedback.
-
|
Why don't you use the web-editor? There you can add multiple nodes at the same time. |
Beta Was this translation helpful? Give feedback.
-
Well, it's easier and quicker to just do a command. Instead of opening a new editor session every time. I only really use the editor when I'm doing large changes (changing every groups prefix for example) |
Beta Was this translation helpful? Give feedback.
-
|
I think this is a very valid suggestion. It could even work with creating groups, adding parents, etc. |
Beta Was this translation helpful? Give feedback.
-
|
A permission node, that makes it so you can only add certain nodes/groups. Say you want group admin to be able to promote other people to any rank including admin, but not owner. You can’t do that. With this it could be some kind of permission like |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
A way to toggle permission nodes for a specific group, depending on if another group has members online or not. For example: Builders don't get worldedit permission, only Creative. But if a Higher-Up is online, it toggles them to be able to use WorldEdit. And if no Higher-Ups are one, the permissions to use WorldEdit get disabled. |
Beta Was this translation helpful? Give feedback.
-
Definitely would use this. Didn't think of it but it's awesome! Could be as simple as another context like |
Beta Was this translation helpful? Give feedback.
-
|
Totally agree! I would absolutely love to use this kind of feature! |
Beta Was this translation helpful? Give feedback.
-
|
I've recently been needing this feature and it would be really handy, the ability to check for false contexts. I wanted this one user to have a certain group, when in all but one server. To do this I had to manually add each check for every server EXCEPT the one that I wanted them not to have it. So I think it would be good if we could have contexts like |
Beta Was this translation helpful? Give feedback.
-
|
Master, Slave thing. So you can block luckperms commands from console (except bulkupdate ofc) so you could have only specific servers run luckperms commands from console. |
Beta Was this translation helpful? Give feedback.
-
|
GitHub disscussions are very good for people! |
Beta Was this translation helpful? Give feedback.
-
|
The ability to specify which group to promote or demote a player on a certain track. Currently, the command for promoting/demoting goes like I would like the command to have an additional, optional variable: This would also be useful to prevent accidental demotions/promotions of players. If you try to promote a player to a group that is lower than his current group, the command wouldn't work. If you try to demote a player to a higher group than his current group, the command also wouldn't work. A perfect example of this is, sadly outdated, GroupManager. I have used it for a long time before finally switching to LuckPerms and I haven't looked back since. But this one little feature is missing. And GM had it. This is my suggestion for the plugin. Feel free to leave any feedback or comments. |
Beta Was this translation helpful? Give feedback.
-
|
I'm sorry that you had to write all of that only to find out that the parent settrack command does exactly what you are asking for 😅 |
Beta Was this translation helpful? Give feedback.
-
|
Not quite, the |
Beta Was this translation helpful? Give feedback.
-
|
I would suggest the ability to set a required amount of playtime in order to be promoted to a specific group. I have a small server with friends, but we are open to inviting friends of friends etc. I don't want people to be able to join and immediately bypass spawn protections or anything like that. I want to turn on spawn protection but not have to give people who join for 5 minutes access to possibly grief us, and I am not home enough to manually add additional people. |
Beta Was this translation helpful? Give feedback.
-
|
I am running an economy on my server as well, and I was wanting to try to sell permissions such as additional sethomes and things of that sort to players. The only way I could think to do this since there does not seem to be any option for something like this was to use command blocks. It does not seem that command blocks have access to use LuckPerms. |
Beta Was this translation helpful? Give feedback.
-
|
@ReturnDesender these are great ideas but they are IMO out of scope for a permission plugin. There are other plugins available which can help accomplish these things. |
Beta Was this translation helpful? Give feedback.
-
|
Allow submitting multiple contexts like I can with permissions. I sadly have a high number of contexts that I use, its sometimes dreadful to know if I need to add a new pernission node I sometimes have to click through like 12 contexts to add them. Would be noice to be able to paste in a context using a pair format.
|
Beta Was this translation helpful? Give feedback.
and others
-
Hello! 👋
Welcome to GitHub Discussions - isn't this fancy!
I thought we could try and use this new discussion functionality to fill the gap between conversations on Discord (which tend to get left behind and lost quite quickly!) and the regular ol' issues tab, which is strictly for bug reports and feature suggestions.
So, to get things started, I have a question for you!
If there was one thing you could change about LuckPerms, what would it be?
I'm thinking things along the lines of:
.. but really, these are just some ideas, anything is valid!
Please react with 👍 to ideas you agree with, and 👎 to ideas you don't!
Feel free to reply to comments if you have something to add. Looking forward to seeing what you guys have to say! <3
Beta Was this translation helpful? Give feedback.
All reactions