Execute Command (Entity Action Type)

Executes a command with the entity as the source (i.e. @s will select the entity itself).

Type ID: apoli:execute_command

Fields#

Field	Type	Default	Description
command	String		The command to execute on the entity.
arguments	Macro Arguments	optional	Values for $(key) placeholders in command, including live resource values. See Macro arguments.

Examples#

"entity_action": {
    "type": "apoli:execute_command",
    "command": "tellraw @a {\"text\": \"Hello world!\", \"color\": \"green\"}"
}

This example will execute a /tellraw command that will print a green-colored “Hello world!” message to all players.

Macro arguments#

arguments fills $(key) placeholders in command before the command is parsed — the same shape a vanilla function macro uses, but done by Apoli, so it works on every version whether or not the game has function macros.

Field	Type	Default	Purpose
storage	Identifier	optional	Read the values from this command storage.
path	String	""	A dot-separated key path inside that storage.
resources	Resource map	optional	Resource values read live off the entity the command runs as. See Resources in a command.
values	NBT Compound	optional	Inline values. Applied last, so they win on a key clash.

Values are written out the way a function macro writes them: strings bare, numbers as numbers, compounds and lists as SNBT. If a $(key) in the command has no matching value, the command is skipped rather than run malformed — and Apoli logs one line naming the key that was missing, so a typo or an absent resource does not fail silently.

Resources in a command#

resources puts apoli:resource and apoli:cooldown values straight into the command, read at the moment it runs. Write it as key: id:

"arguments": {
  "resources": {
    "mana": "example:mana"
  }
}

or as a plain list, which keys each resource by the last segment of its path — example:mana becomes $(mana):

"arguments": {
  "resources": ["example:mana"]
}

resources takes either an object of key: id pairs or a plain list of ids — never a mix. "resources": ["mana": "example:mana"] is not valid JSON, and a data pack file that contains it fails to parse in full, so the power never loads at all. Check the log for Couldn't parse data file if a power seems to do nothing.

When a $(key) cannot be filled the command is skipped and one line is logged naming the key and the reason — the power id is not loaded, the holder does not have it, or the power it names is not a resource. Turn on /apoli:dev_mode and that line is also sent to you in chat, every time, rather than once to the log.

Each key also gets _max and _min companions wherever the resource declares those bounds, so a readout needs no second lookup:

"entity_action": {
  "type": "apoli:execute_command",
  "command": "say mana: $(mana)/$(mana_max)",
  "arguments": {
    "resources": ["example:mana"]
  }
}

That prints mana: 7/10 in chat — which is the quickest way to watch a resource move while you are building the power that changes it. Turn on /apoli:dev_mode and every apoli:execute_command also echoes its finished command to you, macros already expanded, so you can see exactly what ran.

apoli:store_data is the usual way to fill that storage — it writes id, pos, x/y/z and, for blocks, a state string that /setblock accepts as-is:

"entity_action": {
  "type": "apoli:execute_command",
  "command": "setblock $(pos) $(state)",
  "arguments": {
    "storage": "example:scratch",
    "path": "block"
  }
}