You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting a permission for a user, if that user is offline, the permission is set normally and will be applied as expected. However, if that user is online, an error is thrown in console and the permission claims to be applied, but is not.
An example can be seen near line 559 of the supplied log.
Step to reproduce
Set permission for offline user /lp user <name> permission set <node> <value>
Check permissions for offline user and see it is applied /lp user <name> permission info
Have the affected user log in
Try to modify the permissions for that user in any way (Set a new one, unset one, change value of existing permission)
Check permissions for the affected user. Changes will not have been properly applied, despite Luckperms saying they were.
Oh, you're using the 5.4.153 version of Luckperms, which is for 1.21.4.
Changing to the correct version for 1.21.1 will help.
Btw, you can download the history versions of luckperms in modrinth or curseforge.
The version of mods must be exactly matched, but the plugins are not.
Completely missed that, thank you. I normally check that sort of thing, not sure how it slipped past me. Fixing the mod version seems to have fixed the issue.
I have confirmed that ...
Arclight version
arclight-1.21.1-1.0.1-SNAPSHOT-38d813d
OS & Java versions
openjdk version "21.0.6"
Plugins and Mods
Description
When setting a permission for a user, if that user is offline, the permission is set normally and will be applied as expected. However, if that user is online, an error is thrown in console and the permission claims to be applied, but is not.
An example can be seen near line 559 of the supplied log.
Step to reproduce
/lp user <name> permission set <node> <value>
/lp user <name> permission info
Logs
2025-02-26-1.log
Server pack link (Optional)
No response
The text was updated successfully, but these errors were encountered: