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
{{ message }}
Repository navigation
Permission seeingui let user wear cosmetics even if they don't have the wear permission #346
I'm using the very latest version of CosmeticsCore and its dependencies.
I already searched on this Github page to check if the same issue was already reported.
I already searched on the plugin wiki to know if a solution is already known.
I already searched on the Discord server to know if anyone already provided a solution in the past for the issue.
Discord tag (optional)
ouafax
What happened?
When I give the player the permission cosmeticscore.user.cosmetics.seeingui.* or cosmeticscore.user.cosmetics.seeingui.ANY_COSMETIC_NAME they can see every or the specified cosmetics in their /cosmetics command. The problem is that even with cosmeticscore.user.cosmetics.wear.* set to false (so it should only allow them to see them as Locked in their inventory) they can still wear them.
Steps to reproduce the issue
Using any permission plugin (like luckperms) set the wear.* permission to false
Using any permission plugin (like luckperms) set the seeingui.* permission to true
In that setup, you can see every cosmetics and wear them.
It wont save but you can still wear them in the current session.
Server version
This server is running Paper version 1.21.8-6-main@782ce95 (2025-07-18T20:26:58Z) (Implementing API version 1.21.8-R0.1-SNAPSHOT)
You are 54 version(s) behind
Download the new version at: https://papermc.io/downloads/paper
Previous version: 1.21.7-32-e792779 (MC: 1.21.7)
Hello, it's almost a year since this issue was open. I wish at least to get an update when we paid for the product and that it cause us trouble using it...
I saw some bug fix on new version but is it planned to fix this kind of ... important issue ?
Hello, it's almost a year since this issue was open. I wish at least to get an update when we paid for the product and that it cause us trouble using it...
I saw some bug fix on new version but is it planned to fix this kind of ... important issue ?
thanks
Haiii, a fix has been made, I'm just waiting on LoneDev now to publish the new version
I'm really sorry for the wait
Activity
Joao-Victor-Liporini commentedon Feb 14, 2026
Can confirm this bug in latest version of cosmeticscore, 1.3.9
My server version is 1.21.10.
Protocollib v5.4.0
siberanka commentedon Mar 8, 2026
I can confirm too
ouafax commentedon Sep 7, 2026
Hello, it's almost a year since this issue was open. I wish at least to get an update when we paid for the product and that it cause us trouble using it...
I saw some bug fix on new version but is it planned to fix this kind of ... important issue ?
thanks
PuppyTransGirl commentedon Sep 7, 2026
Haiii, a fix has been made, I'm just waiting on LoneDev now to publish the new version
I'm really sorry for the wait