Problem

In Minecraft 1.20.5 new Componments were added to item data. These components replace the old NBT based system for storing properties like custom name, durability, enchanments, etc ...

In addition there is no way to read all properties of an item (which are now stored as components) We already know the enchantments and disaplay name of an item but not all components.

Mods add their own components like Create which has create:package_address or the computercraft:computer_id component from CC: Tweaked but there is no way to read this information.

Solution

My propopsal would be to add a components field to the return value of inventory.getItemDetail, an example would be:

{
    ...
    components: {
        "minecraft:stored_enchantments" = {levels = {"minecraft:aqua_affinity" = 1}},
        "minecraft:custom_name" = "Epic book"
    }
    ...
    maxCount = 1,
    name = "minecraft:enchanted_book",
}

Example

A purpose to use item components from computers could be a postcode based package routing machine by reading the create:package_address component from a package and comparing it agnist a routing table.

Wouldn't this run into same issue nbt reading idea had where it could expose information mod potentially don't want user to know?
Are components considered something that will not have secret information?

@Wojbie But the vanilla /data command can be used to see the data of items and the potentially secret value.

If a mod is using item compoents for secret information I would say that is bad mod design. Although on most servers the /data comamnd can only be used by operators but if something is meant to be secret the operators shouldn't even know it.

Wouldn't this run into same issue nbt reading idea had where it could expose information mod potentially don't want user to know?
Are components considered something that will not have secret information?

CC:T deliberately avoids exposing raw NBT (and now components, in a post-1.20.5 world) for a couple of reasons:

• There are some cases where item NBT should not be exposed to the player — not necessarily secret information, but breaking mod progression. The classic example here is Forestry bees — if computers can read their NBT, then you bypass the whole research mechanic!

• Item NBT have no stability/format guarantees. Mojang frequently changes the format of components, and before we take mods into the mix! The point of the item detail system is to provide a stable API over Minecraft's changing internals.

I would like to make it easier to extend what data is exposed. There is a public API for it, but maybe we should look into easier KubeJS and/or datapack support for this.