Skip to content

Permission seeingui let user wear cosmetics even if they don't have the wear permission #346

Open

Description

@ouafax

Terms

  • 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

  1. Using any permission plugin (like luckperms) set the wear.* permission to false
  2. 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)

CosmeticsCore Version

CosmeticsCore version 1.3.8

ProtocolLib Version

ProtocolLib version: 5.4.0

FULL server log

No response

Error (optional)

CosmeticsCore config.yml

Problematic items yml configuration file (optional)

Other files, you can drag and drop them here to upload. (optional)

No response

Screenshots/Videos (you can drag and drop files or paste links)

Image Image Image Image

Activity

  1. Joao-Victor-Liporini commented on Feb 14, 2026

    @Joao-Victor-Liporini

    Can confirm this bug in latest version of cosmeticscore, 1.3.9

    My server version is 1.21.10.
    Protocollib v5.4.0

  2. siberanka commented on Mar 8, 2026

    @siberanka

    I can confirm too

  3. ouafax commented on Sep 7, 2026

    @ouafax
    Author

    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

  4. PuppyTransGirl commented on Sep 7, 2026

    @PuppyTransGirl

    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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: bugSomething isn't working

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions