Resource (Command)

Reads and writes the value behind an apoli:resource or apoli:cooldown power. The short alias is /resource. The same values can also be written from /execute store.

Sub-commands

<power> tab-completes to the resource and cooldown powers the targets hold, and falls back to every loaded one when the targets can't be resolved yet.

<power> also accepts any power type with a built-in cooldown field: apoli:action_on_key_press, apoli:action_on_key_sequence, apoli:fire_projectile, apoli:action_on_hit, apoli:action_when_hit, apoli:action_on_kill, apoli:action_on_collision and apoli:game_event_listener. The value is the remaining cooldown in ticks, so set <power> 0 clears the cooldown and makes the ability usable again.

Examples

resource get @s example:mana
resource set @s example:mana 20
resource change @s example:mana -5
resource has @a example:mana

Table resources take the slot as the optional position:

resource list @s example:table
resource get @s example:table 2
resource set @s example:table 5 2
resource set @s example:table 0

The last line has no position, so it clears every slot at once.

This stores a resource in a scoreboard:

execute store result score @s mana run resource get @s example:mana

Targets that don't hold the power are skipped. If no target holds it, the command reports that and returns 0, so /execute if behaves sensibly.

Scoreboard operations

operation does to a resource what /scoreboard players operation does to a score. The resource is on the left of the operator, and one score (<source> in <objective>) is on the right.

resource operation @s example:mana += @s mana_bonus
resource operation @a example:mana < #cap settings
resource operation @s example:table 2 = @s picked_slot

The operators behave exactly like the vanilla command's, because they are the vanilla command's. Dividing or taking a remainder by 0 fails with "Cannot divide by zero" and changes nothing. <source> is a single score holder: a player name, a fake name like #cap, or a selector that matches one entity. As with the vanilla command, naming a holder that has no score yet gives it a score of 0.

The result is clamped to the power's min and max like any other write. With ><, the score always receives the resource's old value, even when the resource couldn't take the whole score.

With a position, the operation works on that slot of a table resource. Without one, it reads slot 0 and writes the result to every slot, like set.

Storing with /execute

resource is also a target for /execute store, next to score, entity and the others:

execute store result resource <targets> <power> run <command>
execute store success resource <targets> <power> run <command>

result writes the command's result into each target's resource, and success writes 1 if the command succeeded and 0 if it failed. The write is clamped to the power's bounds like set, and on a table resource it fills every slot.

execute store result resource @s example:mana run data get entity @s XpLevel
execute as @a store result resource @s example:mana store result score @s mana run function example:roll

The second line stores the same result in a resource and a score at once. store resource chains with every other /execute sub-command, including other store clauses, the same way store score does.

Notes

• A resource's stored value outlives the power itself, so granting the power again restores what you had. Every sub-command therefore checks that the target still holds the power before reading or writing a value, and a leftover value from a power you no longer have never shows up.
• get and change without a position read and write slot 0 of a table resource, the same value the HUD bar and an Expression reference without an index see. set, operation and store resource write every slot when no position is given.
• set, change and operation respect the power's own bounds, so you can't push a resource past its max or below its min. To go further, change the power.