NBT and data on things

Data can be kept on a thing itself: on the item in somebody's hand, on a creature or a player, or on a block that holds something (a chest, a sign, a furnace). The server saves it in the thing's NBT, so it travels with the item from player to player and is still there after a restart.

command /soulbind:
    trigger:
        set nbt "owner" of tool of player to player.name
        set nbt "kills" of tool of player to 0
        send "&dThis item is yours now."

on entity death:
    if killer is set:
        if nbt "owner" of tool of player is player.name:
            set {_kills} to nbt "kills" of tool of player + 1
            set nbt "kills" of tool of player to {_kills}
            send action bar "&7Kills with this item: &f%{_kills}%" to player

on right click:
    if nbt "locked" of block at event's location is true:
        if nbt "owner" of block at event's location is not player.name:
            cancel event
            send "&cThis is not yours."

command /lock:
    trigger:
        set {_chest} to target block of player
        set nbt "locked" of block at {_chest} to true
        set nbt "owner" of block at {_chest} to player.name
        set nbt "visits" of player to nbt "visits" of player + 1
        delete nbt "tutorial" of player
        send "&7%nbt of tool of player%"

command /trophy:
    permission: "trophy.give"
    trigger:
        set {_trophy} to gold ingot named "&6Trophy" with nbt "winner" player.name with nbt "year" 2026
        give player {_trophy}
        set {_winner} to nbt "winner" of {_trophy}
        send "&7It says: %{_winner}%"
        set nbt of tool of player to "{Unbreakable:1b}"

on mob spawn:
    if event.entity is "zombie":
        set nbt of event entity to "{Silent:1b}"

command /fillchest:
    permission: "fill.use"
    trigger:
        set nbt of block at target block of player to "{Lock:\"secret\"}"

• A value is a text, a number, or true / false.
• Whether something is there is asked with is set: if nbt "owner" of tool of player is not set:.
• A key written plainly, such as "kills", is HyperScript's own and no other plugin touches it. A key written with a colon, such as "otherplugin:level", is what another plugin keeps under that name, and can be read and changed the same way.
• Keys and whole NBT are two things. A key (nbt "kills" of ...) is data of your own, kept apart from the game's, and it is what a script should use for its own bookkeeping. The whole NBT (set nbt of ... to "{...}") is the game's own tags, for what has no statement of its own. What is written there is handed to the game as it is, so a tag the game does not know is refused by the game, and the console says so.
• For what there is a statement for, use the statement: set health of, enchanting an item, unbreakable. They work the same on every version; the names of the game's tags do not.
• Data on an item belongs to that one item. tagged and with model are still the simple way to mark an item a script hands out; see Players.