A Minecraft datapack aimed at handling player data easily.
Designed for use in multiplayer maps/datapacks.
Automatically handles player name changes.
Handles up to 32 players.
Execute function suso.player_data:get/do as the player whose data you want to get. This will result in that player's data being copied to path storage suso:pldata working_data.
After editing the data, the result contained in this path can be saved by running function suso.player_data:put/do, again, as the player in question. If the data wasn't edited (read only operations), there's no need to run this function.
Every player's data starts off as a blank nbt object ({}).
If used on a world that's going to be distributed, run function suso.player_data:package to reset the pack. This will pause it until the next reload.
Accessing the same player's data multiple times in a row is faster than when switching between players. When possible, this should be taken into account to optimize usage. For this reason, functions may be tagged under #suso.player_data:player_tick to be run each tick per player, grouping player data operations.
test:example.mcfunction:
#Get player data
function suso.player_data:get/do
#Add one to a counter
execute store result score $temp objective run data get storage suso:pldata working_data.counter
scoreboard players add $temp objective 1
execute store result storage suso:pldata working_data.counter int 1 run scoreboard players get $temp objective
#Store the players currently held item
data modify storage suso:pldata working_data.held set value {}
data modify storage suso:pldata working_data.held set from entity @s SelectedItem
#Save player data
function suso.player_data:put/doIn this case, running execute as @p run function test:example would increase a counter inside the nearest player's data, as well as storing their held item.
This library is licensed under the Apache License 2.0. When using it as part of your own projects, you must:
- Include crediting for the library in a way visible to players. This probably fits best into the credits section of your map/datapack in-game, but in case that's impossible it may be done within a text file or documentation distributed with the project.
- Include a copy of the license.