Skip to content

1.21.8 texturepack issues #344

Open
Open

Description

@Dondius

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)

Dondius

What happened?

texture pack broke before adding anything of mine to it

Image Image Image

Steps to reproduce the issue

Followed the toturials on the wiki for first install to the T. and decided to only use the UI to get my own cosmetics in but the texturepack there follow the plugin is not combatible with 1.21.8

Server version

No response

CosmeticsCore Version

Image

ProtocolLib Version

Image

FULL server log

latest.log

Error (optional)

CosmeticsCore config.yml

lang: en
prefix: '&5Cosmetics&r '
extract_default_assets: true
cosmetics:
  max_equippable:
    body: 3
    balloon: 2
  hide_during_combat:
    enabled: true
    combat_duration_ticks: 600
    only_pvp: true
  fix_invisible_nametag: false
  hide_in_vanish: true
  worlds:
  - '*'
wardrobe_room:
  allow-not-owned-preview: true
  camera:
    hide_actionbar_texts: true
    use_invisibility_potion: false
    rotation:
      manual:
        enabled: true
        step: 20
      auto:
        enabled: true
        direction: RIGHT
        step: 1.5
        pause_ticks_on_manual_rotation: 60
    zoom:
      enabled: true
      min: 2
    fade_effect: true
    location:
      world: towerlobby
      x: -121.60558403462078
      y: 87.62000000476837
      z: 6.50543322178649
      yaw: 90.543335
      pitch: 31.499744
  mannequin:
    location:
      world: towerlobby
      x: -128.5
      y: 84.0
      z: 6.5
      yaw: -91.24548
      pitch: 1.049947
  teleport_area:
    enter:
      world: towerlobby
      pos1:
        x: -121.0
        y: 83.0
        z: 8.0
      pos2:
        x: -121.0
        y: 86.0
        z: 6.0
    exit_location:
      world: towerlobby
      x: -114.23771528050422
      y: 80.0
      z: 7.452918926817849
      yaw: -90.19559
      pitch: -0.75008756
  gui:
    cursor_default: fermented_spider_eye:9000001
    cursor_rotate: fermented_spider_eye:9000002
    cursor_pointer: fermented_spider_eye:9000003
    dyeing_pointer: fermented_spider_eye:9100003
    tutorial_gui: fermented_spider_eye:9100004
    tutorial_gui_checked: fermented_spider_eye:9100005
    slots:
      colors:
        owned: 56,67,100
        not_owned: 195,147,57
        wearing: 57,70,195
        wearing_preview: 195,120,57
        max_amount_reached_owned: 24, 29, 43
        max_amount_reached_not_owned: 64, 48, 17
      add_item_in_blank_slots:
        # This is useful only for some expert users that need to do some crazy stuff.
        # Do not enable it if you don't know what you are doing.
        enabled: false
        type: PAPER
        custom_model_data: 1337666
  commands:
    whitelist:
      enabled: true
      list:
      - msg
      - tell
      - r
      - reply
      - help
    blacklist:
      enabled: false
      list:
      - home
      - sethome
send_creative_hidden_hat_message: true
save:
  # Use only one at a time
  file:
    enabled: true
  mysql:
    enabled: false
    url: jdbc:mysql://my_url_database_69.com:3306/database_name
    username: username
    password: password
    table: cosmeticscore_saved
debug: false

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)

No response

Activity

  1. ColorsASD commented on Oct 22, 2025

    @ColorsASD

    I tried to fix this issue, but it seems that starting from version 1.21.6+, the client (GUI) now clips items within their slot boundaries. To disable this behavior, a MOD is required — neither textures nor plugins can modify this part of the rendering pipeline.

    I tried resizing it, but the image always stayed confined within the small “slot” square; when you enlarge it, the excess parts simply get cut off for every item.

    We probably noticed this change when every slot started being fully rendered, even if an image was drawn above it — previously, you could only see the outline when hovering over items, but now the full slot square is always visible.

    Solution:
    Move everything into a Chest GUI (which I believe is already the case). This way, the Chest title (header) can be modified freely.
    That fermented spider eye should be removed, as it will no longer work. (The clickable, interactive part can still be handled using invisible items.)

    Image
  2. ColorsASD commented on Oct 22, 2025

    @ColorsASD

    @Dondius By the way, starting from version 1.21.4+, your custom items don’t appear because you’re using an old texture format!

    You can easily update your textures using the following tool:
    👉 https://github.com/BrilliantTeam/Minecraft-ResourcePack-Migrator

    (From version 1.21.6, Mojang changed the rendering system — the client now prevents item textures from extending beyond the slot (small square) boundaries.
    Essentially, you’ll be able to update all elements using the application; however, tutorial.png and tutorial_dont_show_again.png will still not appear, as this is a completely different issue.
    In addition, it’s likely that the large images on the elements will also be clipped, so instead of covering the full screen, they will only appear within a small square area.)

  3. Dondius commented on Oct 22, 2025

    @Dondius
    Author

    so i fixed the testurepack for the cursor but how do i move the tutorial.png and tutorial_dont_show_again.png up to the title header?

  4. ColorsASD commented on Oct 22, 2025

    @ColorsASD

    Only LoneDev will be able to fix that because the plugin is not open source.

  5. ColorsASD commented on Oct 22, 2025

    @ColorsASD

    And you’re not fixing the cursor, you’re fixing the items — the models.

    Old format: assets/minecraft/models/item/...
    New format: assets/minecraft/items/...

  6. ColorsASD commented on Nov 7, 2025

    @ColorsASD

    I switched from 1.19.4 to 1.20.6. I’m not sure whether ViaVersion was the issue or if the built-in shaders from ItemsAdder fixed it, but everything is working fine for me now.
    So: 1.20.6 server with a 1.21.8 client. Latest ViaVersion and ItemsAdder.

  7. nillpoe commented on Apr 16, 2026

    @nillpoe

    @LoneDev6 Please check this one

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