Skip to content

Add support for expanded custom model data. #7782

@Evanbeer

Description

@Evanbeer

Skript/Server Version

[Skript] Skript's aliases can be found here: https://github.com/SkriptLang/skript-aliases
[Skript] Skript's documentation can be found here: https://docs.skriptlang.org/
[Skript] Skript's tutorials can be found here: https://docs.skriptlang.org/tutorials
[Skript] Server Version: 1.21.4-222-9b1798d (MC: 1.21.4)
[Skript] Skript Version: 2.10.2 (skriptlang-github)
[Skript] Installed Skript Addons: 
[Skript]  - SkBee v3.10.2 (https://github.com/ShaneBeee/SkBee)
[Skript]  - DiSky v4.22.1
[Skript] Installed dependencies: 
[Skript]  - Vault v1.7.3-b131
[Skript]  - WorldGuard v7.0.13+82fdc65

Bug Description

Custom model data got changed in 1.21.4. I can still add custom model data to items using the existing expression, but the textures assigned to that item will not appear.

Expected Behavior

It should behave like it used to, you can add a custom model data to an item and it will use the correct texture assigned with that custom model data.

Steps to Reproduce

Run a server and client on 1.21.4, create a texturepack which assigns a texture to an item when it has a specific custom model data. You can use this new 1.21.4 command to give yourself the working item with the correct texture:
/minecraft:give player map[minecraft:custom_model_data={strings:['1']}]

Then make a skript with something like:
Give 1 map with custom model data 1 to player

And then the texture wont appear even through the item has the custom model data.
I believe this is caused by the game expecting a list and not a single integer.

Errors or Screenshots

The one made with skript:
Image

The one made with commands:
Image

Other

I need custom model data to use my texturepack, i would really appreciate if this gets patched back to its normal behavior as soon as possible.

Agreement

  • I have read the guidelines above and affirm I am following them with this report.

Metadata

Metadata

Assignees

No one assigned

    Labels

    completedThe issue has been fully resolved and the change will be in the next Skript update.enhancementFeature request, an issue about something that could be improved, or a PR improving something.priority: lowIssues that are not harmful to the experience but are related to useful changes or additions.

    Type

    No type

    Projects

    Status

    Done - Released

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions