Custom model data for tokens

[Moltanicaa]

At the moment, only paper is used without the ability to set either another material or a custom model data. I would just like to make a token store so that players can buy different tokens, so I would like to be able to set the CMD for each token separately. Maybe not even for each one separately, but at least for the tokens as a whole.

[hyperdefined]

I'm not sure what this is asking. You can use /toolstats givetokens <player> <token-type> <amount> to give tokens.

[Moltanicaa]

I'm not sure what this is asking. You can use /toolstats givetokens <player> <token-type> <amount> to give tokens.

No, i mean custom texture

[hyperdefined]

Tokens store NBT data on what token they are. I'm not sure if this is enough to support custom textures for them.

Would you want something like this?

paper[minecraft:item_model="toolstats:damage-done-token"]

[hyperdefined]

Quick test with Paper's API, this is what I can do I believe:

minecraft:paper[lore=[{color: "dark_gray", italic: 0b, text: "Combine with a melee or ranged weapon in an anvil to track player kills."}],custom_data={PublicBukkitValues: {"toolstats:token-type": "player-kills"}},custom_model_data={strings: ["player-kills"]},custom_name={extra: [{color: "gray", text: "ToolStats: "}, {color: "dark_gray", text: "Player Kills Token"}], italic: 0b, text: ""}]

This is a player kills token.

[Moltanicaa]

I mean something like this:

i also rewrite lore for me + add info about consuming levels, but i did this in russian language so i retranslate it back through deepseek

  data:
    player-kills:
      title: "&7ToolStats: &8Player Kills Token"
      lore:
        - "&8Combine with melee or ranged weapon in an anvil"
        - "&8Tracks player kill count"
        - "&8Consumes 1 experience level when applied" #Need to add %levels% placeholder to display required levels
      levels: 1
    mob-kills:
      title: "&7ToolStats: &8Mob Kills Token"
      lore:
        - "&8Combine with melee or ranged weapon in an anvil"
        - "&8Tracks mob kill count"
        - "&8Consumes 1 experience level when applied"
      levels: 1
    blocks-mined:
      title: "&7ToolStats: &8Blocks Mined Token"
      lore:
        - "&8Combine with pickaxe, axe, shovel or shears in an anvil"
        - "&8Tracks mined blocks count"
        - "&8Consumes 1 experience level when applied"
      levels: 1
    crops-mined:
      title: "&7ToolStats: &8Harvested Crops Token"
      lore:
        - "&8Combine with hoe in an anvil"
        - "&8Tracks harvested crops"
        - "&8Consumes 1 experience level when applied"
      levels: 1
    fish-caught:
      title: "&7ToolStats: &8Caught Fish Token"
      lore:
        - "&8Combine with fishing rod in an anvil"
        - "&8Tracks caught fish"
        - "&8Consumes 1 experience level when applied"
      levels: 1
    sheep-sheared:
      title: "&7ToolStats: &8Sheep Shearing Token"
      lore:
        - "&8Combine with shears in an anvil"
        - "&8Tracks sheared sheep count"
        - "&8Consumes 1 experience level when applied"
      levels: 1
    damage-taken:
      title: "&7ToolStats: &8Damage Taken Token"
      lore:
        - "&8Combine with armor piece in an anvil"
        - "&8Tracks damage taken"
        - "&8Consumes 1 experience level when applied"
      levels: 1
    damage-done:
      title: "&7ToolStats: &8Damage Dealt Token"
      lore:
        - "&8Combine with melee or ranged weapon in an anvil"
        - "&8Tracks damage dealt"
        - "&8Consumes 1 experience level when applied"
      levels: 1
    arrows-shot:
      title: "&7ToolStats: &8Arrows Shot Token"
      lore:
        - "&8Combine with bow or crossbow in an anvil"
        - "&8Tracks arrows shot count"
        - "&8Consumes 1 experience level when applied"
      levels: 1
    flight-time:
      title: "&7ToolStats: &8Flight Time Token"
      lore:
        - "&8Combine with elytra in an anvil"
        - "&8Tracks flight time"
        - "&8Consumes 1 experience level when applied"
      levels: 1
    reset:
      title: "&7ToolStats: &8Stats Reset Token"
      lore:
        - "&8Combine with item in an anvil"
        - "&8Resets ALL stats for this item"
        - "&8Tokens REMAIN in the item"
        - "&8Consumes 1 experience level when applied"
      levels: 1
    remove:
      title: "&7ToolStats: &8Item Purge Token"
      lore:
        - "&8Combine with item in an anvil"
        - "&8Removes ALL stats from this item"
        - "&8Tokens are DELETED from the item"
        - "&8Consumes 1 experience level when applied"
      levels: 1

[hyperdefined]

%levels% can be added, good idea. For custom_model_data, what does the number mean?

[Moltanicaa]

%levels% can be added, good idea. For custom_model_data, what does the number mean?

this is old format for custom_model_data. now this can be as a string, but then this wan only a number. many plugins support old float format and don't know anything about string format, so I don't see a problem using number (float) format and further

[Moltanicaa]

The custom_model_data is assigned by the resource pack, this is already on the player's side (the player creates his resource pack independently), so the ability to specify a custom_model_data can be specified in the file header so that the player, if anything, could register the values ​​himself. It is not necessary (and undesirable) to offer values ​​yourself, only if the plugin does not come with a resource pack.

[hyperdefined]

%levels% can be added, good idea. For custom_model_data, what does the number mean?

this is old format for custom_model_data. now this can be as a string, but then this wan only a number. many plugins support old float format and don't know anything about string format, so I don't see a problem using number (float) format and further

Look at the example I gave:

minecraft:paper[lore=[{color: "dark_gray", italic: 0b, text: "Combine with a melee or ranged weapon in an anvil to track player kills."}],custom_data={PublicBukkitValues: {"toolstats:token-type": "player-kills"}},custom_model_data={strings: ["player-kills"]},custom_name={extra: [{color: "gray", text: "ToolStats: "}, {color: "dark_gray", text: "Player Kills Token"}], italic: 0b, text: ""}]

This has custom_model_data={strings: ["player-kills"]}, which is what you are asking.

The idea is to add a field under each token that let's you specify a string to be added to the custom_model_data. (Example, add string player-kills).

[Moltanicaa]

%levels% can be added, good idea. For custom_model_data, what does the number mean?

this is old format for custom_model_data. now this can be as a string, but then this wan only a number. many plugins support old float format and don't know anything about string format, so I don't see a problem using number (float) format and further

Look at the example I gave:

minecraft:paper[lore=[{color: "dark_gray", italic: 0b, text: "Combine with a melee or ranged weapon in an anvil to track player kills."}],custom_data={PublicBukkitValues: {"toolstats:token-type": "player-kills"}},custom_model_data={strings: ["player-kills"]},custom_name={extra: [{color: "gray", text: "ToolStats: "}, {color: "dark_gray", text: "Player Kills Token"}], italic: 0b, text: ""}]

This has custom_model_data={strings: ["player-kills"]}, which is what you are asking.

The idea is to add a field under each token that let's you specify a string to be added to the custom_model_data. (Example, add string player-kills).

Yea, this is great. But the "string" format does not migrate to versions below 1.21.4. If this suits you, great.

[hyperdefined]

Oh, I see. Could add custom_model_data_type and custom_model_data_value so you can specify a data type?

[Moltanicaa]

I don't really know because I haven't worked with the "string" format. I'm used to working with the "float" format (this format used for years). I use Nexo to assign the "custom_model_data" format and it simply doesn't work with the "string" format, it just removes the values. So I think at this point it's best to just let the player assign the float (this is important) custom_model_data values ​​themselves until plugins learn to work with the string format properly.

The example below shows how the plugin works with this format - it simply removes the string format and replaces it with the legacy format.

[Moltanicaa]

i suggest comething like this

[hyperdefined]

Sounds good, I can work on implementing this.

[Moltanicaa]

For future innovations, you can also add a field to select an item so that it is not only paper. In case the player does not use the resource pack, but also does not want to see simple sheets of paper.