Setting tp permissions to users
Hey so im refreshing my knowledge on LuckPerms. I wanted to give everyone in my server access to the tp command, but when i add the permission not only to the user, but also maing a group and putting that user into said geoup, they still did not have access to the tp command. Even trying it myself when i added the tp command and deoping myself dosnet work for.me either. For context its a modded server thats running bettermc 3 fabric, and luckperms is running off of fabric with minecraft 1.21.1(since thats the version of better mc). I stg i must be missing something but idk wha.
Solution:Jump to solution
something you might wanna look into is https://github.com/DrexHD/VanillaPermissions
GitHub
GitHub - DrexHD/VanillaPermissions: This fabric mod adds permission...
This fabric mod adds permission checks into vanilla, to allow for full permission customization. - DrexHD/VanillaPermissions
8 Replies
It sounds like you’ve done most things correctly, but there are a few points you can check to ensure that permissions are set up properly and functioning as intended. Here are some steps you can go through:
1. Check the Permission: Make sure you are using the correct permission for the TP command. In many cases, the permission for the teleport command is
essentials.tp (if you are using Essentials) or minecraft.command.tp (for the vanilla command). Check the documentation of the plugin you are using to ensure you have the right permission.
2. Permission Hierarchy: LuckPerms uses a permission system that is based on hierarchies. If a user is in multiple groups, one group can deny a permission that another group grants. Check the permissions of all groups that the user is in to ensure that no group is denying the TP permission.
3. LuckPerms Cache: Sometimes, it can help to clear the LuckPerms cache. You can do this by using the command /lp recalculate <username> to recalculate the permissions for a specific user.
4. Server Restart: After making changes to permissions, it may sometimes be necessary to restart the server for the changes to take effect.
5. Check the Console for Errors: If you try the command and it doesn’t work, check the server console for any error messages that might indicate that the permission is not recognized or that there is another issue.
6. Using LuckPerms Commands: You can also use the command /lp user <username> info to see what permissions the user has and which groups they belong to. This can help you determine if the permission is set correctly.
7. Plugin Compatibility: Since you are using a modified server with BetterMC, make sure that all the plugins you are using are compatible with LuckPerms and the version of Minecraft you are playing.I did test minecraft.command.tp and that also didnt work. Tried restsrting the server and also no bueno, other stuff you mentioned i haven't tried yet
Ill do it when i get home
I wouldnt think any mods are conflicting bc i was able to give myself access to edit luckperms all together
If it wasnt working i wouldnt be able to give myaelf the perms to edit it i think
Also also i did run the info part to see if it had it and it said it did. Also on the web editor it was there as well
Didnt run any errors as far as i know
Also i set that permission on the default group as well
then I don't know what to do, sorry
i dont think minecraft has permission nodes
since they are added by craftbukkit usually
Solution
something you might wanna look into is https://github.com/DrexHD/VanillaPermissions
GitHub
GitHub - DrexHD/VanillaPermissions: This fabric mod adds permission...
This fabric mod adds permission checks into vanilla, to allow for full permission customization. - DrexHD/VanillaPermissions
Hm
So im guessing it would be put into the mods folder right, since i dont have a plugins folder?
Ill try this
vanillapermissions is a fabric mod so yeah
Yea that was a dumb question lmao
Ok so this did work, and i still had to add minecraft.command.tp
And it works, just not fully, they cant do @e or @s, which i think should be a simple fix of just adding a .*to the end of it right?
Or is it more complicated?
Ok so i looked it up and its apperently the target selectors
How do i enable that perm?
Nvm found it, its at the very bottom of the config called resolve-command-selectors
Thank you all for the help you have no idea how much i appreaciate it