Skip to content

Update 1.21.5 #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
+93 −2
Open

Update 1.21.5 #9

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
827119d
Update storeinventory.md
Jun 9, 2025
303b3fe
mbmb
PhxThePizza Jun 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
95 changes: 93 additions & 2 deletions questions/storeinventory.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,7 @@ There are community made datapacks that do the heavy lifting for you like [Playe

#### In storage

Since version 1.20.2, [macro](https://minecraft.wiki/w/Function_(Java_Edition)#Macros) have been added that allow you to insert any data into any part of the command, making storing/returning easier.
Since version 1.20.2, [macros](https://minecraft.wiki/w/Function_(Java_Edition)#Macros) have been added that allow you to insert any data into any part of the command, making storing/returning easier.

Below is an example of storing a player's inventory in storage using the [scoreboard ID system](/wiki/questions/linkentity), or you can store the UUID / nickname instead of using the scoreboard ID system. To do this you need to run the function `example:storing` as a player.

Expand All @@ -125,9 +125,54 @@ This player data storage system will create an in storage `example:inv` object f
# storage example:inv players[{ID:5}]
{ID:5,Inventory:[{Slot:0b,id:"minecraft:stick",Count:1b}]}
```

However, this implementation can support any data other than player `ID` and `Inventory` and you can easily add saving any other data.


In 1.21.5, all of the NBT paths for equipment slots (except for mainhand in players) were moved to the equipment map.
e.g.
```Inventory[{Slot:-106b}]``` moved to ```equipment.offhand```
```Inventory[{Slot:100b}]``` moved to ```equipment.feet```
etc.
In order to account for this, some small tweaks are needed in order for proper storing and loading of items in offhand and armor slots to occur. One implementation of that is shown below.

<details markdown="1">
<summary style="color: #e67e22; font-weight: bold;">See example</summary>

```mcfunction
# function example:storing
data remove storage example:inv this

execute store result storage example:inv this.ID int 1 run scoreboard players get @s ID

data modify storage example:inv this.Inventory set from entity @s Inventory

data modify storage example:inv this.Equipment[{equipment:"weapon.offhand"}] merge from entity @s equipment.offhand
data modify storage example:inv this.Equipment[{equipment:"weapon.offhand"}] merge value {Slot:0b}
execute unless data entity @s equipment.offhand run data modify storage example:inv this.Equipment[{equipment:"weapon.offhand"}] set value {Slot:0b,count:1,equipment:"weapon.offhand",id:"minecraft:air"}

data modify storage example:inv this.Equipment[{equipment:"armor.feet"}] merge from entity @s equipment.feet
data modify storage example:inv this.Equipment[{equipment:"armor.feet"}] merge value {Slot:1b}
execute unless data entity @s equipment.feet run data modify storage example:inv this.Equipment[{equipment:"armor.feet"}] set value {Slot:1b,count:1,equipment:"armor.feet",id:"minecraft:air"}

data modify storage example:inv this.Equipment[{equipment:"armor.legs"}] merge from entity @s equipment.legs
data modify storage example:inv this.Equipment[{equipment:"armor.legs"}] merge value {Slot:2b}
execute unless data entity @s equipment.legs run data modify storage example:inv this.Equipment[{equipment:"armor.legs"}] set value {Slot:2b,count:1,equipment:"armor.legs",id:"minecraft:air"}

data modify storage example:inv this.Equipment[{equipment:"armor.chest"}] merge from entity @s equipment.chest
data modify storage example:inv this.Equipment[{equipment:"armor.chest"}] merge value {Slot:3b}
execute unless data entity @s equipment.chest run data modify storage example:inv this.Equipment[{equipment:"armor.chest"}] set value {Slot:3b,count:1,equipment:"armor.chest",id:"minecraft:air"}

data modify storage example:inv this.Equipment[{equipment:"armor.head"}] merge from entity @s equipment.head
data modify storage example:inv this.Equipment[{equipment:"armor.head"}] merge value {Slot:4b}
execute unless data entity @s equipment.head run data modify storage example:inv this.Equipment[{equipment:"armor.head"}] set value {Slot:4b,count:1,equipment:"armor.head",id:"minecraft:air"}
function example:storing/update with storage example:inv this

# function example:storing/update
$execute unless data storage example:inv players[{ID:$(ID)}] run data modify storage example:inv players append value {ID:$(ID)}
$data modify storage example:inv players[{ID:$(ID)}] merge from storage example:inv this
```
</details>

#### In marker entity

The way to do this is to store the players `Inventory` NBT somewhere safe. There are many things in the game that can store arbitrary NBT data (storage, item tag nbt, etc), and they sure are all good solutions in their own right. In this case, since we're assuming that one player is supposed to be connected to one Inventory save, without any further knowledge of the environment, we'll be using the `marker` entities ability to store arbitrary data for us. *(In case a player is bound to a certain area in a map for example, an item in a jukebox might be a better choice. In any situation, using the `storage` might be a better choice for various reasons, if you know how to properly link data in there with players.)*
Expand Down Expand Up @@ -295,6 +340,52 @@ $execute if score #this Slot matches 103 run loot replace entity @s armor.head l
```
</details>

In 1.21.5, all of the NBT paths for equipment slots (except for mainhand in players) were moved to the equipment map.
e.g.
```Inventory[{Slot:-106b}]``` moved to ```equipment.offhand```
```Inventory[{Slot:100b}]``` moved to ```equipment.feet```
etc.
In order to account for this, some small tweaks are needed in order for proper storing and loading of items in offhand and armor slots to occur. One implementation of that is shown below.

<details markdown="1">
<summary style="color: #e67e22; font-weight: bold;">See datapack</summary>

```mcfunction

# function example:returning
scoreboard objectives add Slot dummy
execute store result storage example:inv this.ID int 1 run scoreboard players get @s ID
function example:returning/read with storage example:inv this
execute unless data storage example:inv this.Inventory[-1].components run data modify storage example:inv this.Inventory[-1].components set value {}
function example:returning/item with storage example:inv this.Inventory[-1]
function example:returning/equipment with storage example:inv this.Equipment[-1]

# function example:returning/read
$data modify storage example:inv this set from storage example:inv players[{ID:$(ID)}]

# function example:returning/item
$scoreboard players set #this Slot $(Slot)
execute if score #this Slot matches 0..35 run function example:returning/inventory with storage example:inv this.Inventory[-1]
data remove storage example:inv this.Inventory[-1]
execute unless data storage example:inv this.Inventory[-1].components run data modify storage example:inv this.Inventory[-1].components set value {}
function example:returning/item with storage example:inv this.Inventory[-1]

# function example:returning/inventory with storage example:inv this.Inventory[-1]
$loot replace entity @s container.$(Slot) loot {pools:[{rolls:1,entries:[{type:"minecraft:item",name:"$(id)",functions:[{function:"minecraft:set_count",count:$(count)},{function:"minecraft:set_components",components:$(components)}]}]}]}

# function example:returning/equipment
$scoreboard players set #thisEquipmentVersion Slot $(Slot)
execute if score #thisEquipmentVersion Slot matches 0..4 run function example:returning/equipment_return with storage example:inv this.Equipment[-1]
data remove storage example:inv this.Equipment[-1]
execute unless data storage example:inv this.Equipment[-1].components run data modify storage example:inv this.Equipment[-1].components set value {}
function example:returning/equipment with storage example:inv this.Equipment[-1]

# function example:returning/equipment_return
$loot replace entity @s $(equipment) loot {pools:[{rolls:1,entries:[{type:"minecraft:item",name:"$(id)",functions:[{function:"minecraft:set_count",count:$(count)},{function:"minecraft:set_components",components:$(components)}]}]}]}

```
</details>

#### Putting things in the original slot (from marker)

This one is a little command intensive, but probably the easiest to understand. All we do is use `item replace` to return all the items back to the player, for every slot. But because we can't get the item data directly from the data storage, we first need to put it into a different container or entity inventory. So lets assume we have a chest placed at `<pos>` that we can store these items into (you can instead use an entity that has an inventory and summon it as needed).
Expand Down