Too Many Attributes (TMA) is a Fabric mod for Minecraft 1.20.1 that adds new building blocks to Origins datapacks. Everything it adds is used from power JSON with "type": "too-many-attributes:<id>", the same way as Origins' own origins:<id> types.

What it adds:

• 41 entity conditions for things Origins can't check: attack cooldown, recent damage and damage blocked, knockback, crouch depth, sprint time, glide ratio, friction, light level at the eyes, moon phase, sleeping, redstone power, vanilla statistics, and more.
• A block condition for redstone signal strength (redstone_power), usable wherever Origins checks a block.
• Actions Origins lacks: turn an entity's view (set_rotation, look_at), fake block-crack animations (play_block_crack), item and vibration cooldowns, phantom mobs and fake players only chosen players can see, which powers can act on (spawn_phantom, phantom_action), and disguises that make an entity look like another type (disguise).
• Signals: one power announces something by name (emit_signal) and unrelated powers react (action_on_signal), so separately written origins can work together.
• Fake blocks: show chosen players a different block at a position, without changing the world (set_fake_block, the fake_blocks power, /tma fakeblock).
• Power tags: group powers in one datapack file (wildcards included), then filter on them with has_power_tag, without touching the powers themselves.
• 45 read-only attributes with the same values, readable with /attribute and Origins' origins:attribute condition, with no power needed.
• A settable drag attribute on every living entity, a direct stand-in for vanilla's fall-drag constant, without touching gravity or jump height.
• Variables and lists. Typed per-player data (int, double, String, …) that you change and check with Java expressions. You can use it in any Origins field and in commands, and it can read scoreboards and the items in a power inventory.
• A global store. Typed values and lists addressed by a key instead of an entity, saved with the world, with optional locking and automatic cleanup of keys tied to entities.
• Power inventories read and written from commands, including each slot's item id as plain text.
• Simple Voice Chat integration: conditions for talking, whispering and groups, plus voice broadcast, forced mute and forced deafen.
• Hardcore Revival integration: an is_downed condition for players knocked out in Hardcore Revival.
• Commands: /tma with (variables in any command), /tma powerinv (read and write origins:inventory powers), /tma phantom, /tma disguise, /tma global, /tma fakeblock, /tma powertag, /disableshield, /tmavc.

The pages are meant to be read in order, like slides, but each one also stands alone as a reference. Every page has ← previous · contents · next → links at the top and bottom.

What's new in 2.2.0

2.2.0 has breaking changes. Read Upgrading to 2.2.0 before updating a pack that uses shield_block_dot or phantom ids.

New types

Phantoms

• Powers can reach phantoms through the three types above and the new /tma phantom run <id> <command>, which runs a command with the phantom as @s. What works on a phantom lists what actions can and can't do to one.
• Ids are whole numbers, handed out automatically (1, 2, 3, …) unless you choose one. /tma phantom spawn and skin return the id and say it in their feedback, so execute store result can keep it for /tma phantom remove, which suggests the ids of live phantoms.
• New behavior stationary: the phantom never moves and only turns to look at nearby viewers.
• Fake players can move: hostile, neutral and passive now work for them too, with the normal walk animation. Left out, a fake player is still stationary. /tma phantom skin takes a behavior like spawn does.
• Phantoms can't be hurt or killed by anything, including /kill, so a phantom mob can't drop real loot. Remove one with despawn_phantom.
• Fixed: fake players wore a default skin (Steve, Alex, …) instead of the named account's. TMA now asks Mojang for signed skin data, which the client requires. A misspelled username, or an account with no skin, is now logged.

Other changes

• Pehkui is no longer required. TMA never used it.
• Hardcore Revival is now listed as a suggested mod, next to Simple Voice Chat. It stays optional.

Not yet tested in-game. Everything above was checked against Minecraft's, Apoli's and Fabric API's code and builds, but none of it has been run in a live game. Treat the (check in-game) notes on each page as exactly that.

Upgrading to 2.2.0

A power that uses a removed id or an old field type fails to load, and the log names the problem.

• Fake players from spawn_phantom with a behavior set now walk. Before, the field was ignored for them. Remove it, or set "behavior": "stationary", to keep them standing still.

What's new in 2.1.3

Everything in 2.1.3 is new. Nothing was removed or renamed, and no field changed meaning, so a pack written for 2.1.0 keeps working as it is.

New conditions

TMA now has block conditions at all, on the new page 5.

New actions

New power types

Bigger additions

• The global store (new page 12): typed values and lists addressed by a key instead of an entity, saved with the world, with optional locking and cleanup for keys tied to entities.
• Power tags (new page 16): group powers in one datapack file, wildcards included, then filter on them.
• Phantoms can be named and removed: an id on spawn_phantom, unique across the server, plus despawn_phantom and /tma phantom remove.
• Fake players: a phantom shaped like a player, wearing a skin looked up by username, with no tab-list row and no name tag.
• New in code: Death.* (where you last died), Stat.get (vanilla statistics) and Global.*.
• New attributes: last_death_distance and redstone_power.
• New commands: /tma phantom, /tma disguise, /tma global, /tma fakeblock and /tma powertag.
• New gamerule tmaPlayerExpiryDays (real days, default 30, 0 = never): how long a player's tracked values and the global keys bound to them are kept after they stop logging in.
• Fixed: tracker maps no longer grow forever. A mob's tracked values are dropped when it's killed, removed or unloaded, and a player's when they pass the gamerule above (page 1).

Not yet tested in-game. Everything above was checked against Minecraft's and Apoli's code, and the parser and store logic were tested on their own, but none of it has been run in a live game. Treat the (Suspected) notes on each page as exactly that.

Upgrading to 2.1.0

2.1.0 removes types that Origins 1.10.0 already provides. A power that uses a removed id fails to load, and the log names the unknown type. Swap in the Origins type:

• Attributes removed with them: fall_distance, oxygen_remaining, is_gliding, sky_visible, wall_collision, rain_level and thunder_level. In functions, data get entity @s FallDistance and data get entity @s Air read the same vanilla values.
• potion_amplifier checks with a comparison become a range. For example, ">=", 1 becomes "min_amplifier": 1. For "doesn't have the effect", use origins:status_effect with "inverted": true.
• New: friction, a condition and attribute for the effective slipperiness of the block you move on, including origins:modify_slipperiness powers.
• New: is_downed, a condition and attribute for whether a player is knocked out in Hardcore Revival - optional, false without it installed.
• New: drag, a settable attribute on every living entity (not just players) that's a direct stand-in for vanilla's fall-drag constant, without touching gravity or jump height.
• Fixed: has_attack_target now works for goal-based mobs (zombies, skeletons, …), not just brain-based ones (piglins, wardens, …).

Pages

Every id

Condition types

Action types

Power types

Commands

The 45 read-only attributes (plus drag) are listed on page 7.

These docs cover TMA 2.2.0. What that version changed is listed in What's new, and what a pack needs to change in Upgrading to 2.2.0.

Requirements

Install TMA like any Fabric mod, on the server and on every client. Clients need it because some values are synced to them, for example variables shown in HUD bars and the attributes.

Your first TMA power

A TMA type goes anywhere Origins accepts that kind of type. Use its id with the too-many-attributes: namespace.

data/mypack/powers/steady_aim.json: +20% damage while you stand still and your attack is fully charged.

{
  "type": "origins:modify_damage_dealt",
  "condition": {
    "type": "origins:and",
    "conditions": [
      { "type": "too-many-attributes:attack_cooldown_progress", "comparison": ">=", "compare_to": 1.0 },
      { "type": "too-many-attributes:sprint_ticks", "comparison": "==", "compare_to": 0 },
      { "type": "too-many-attributes:time_airborne", "comparison": "==", "compare_to": 0 }
    ]
  },
  "modifier": { "operation": "multiply_total_multiplicative", "value": 0.2 }
}

Add the power to an origin as usual ("powers": ["mypack:steady_aim"] in data/mypack/origins/<origin>.json), or grant it directly to test:

power grant @s mypack:steady_aim

How these docs are laid out

Each type gets a block like the Origins docs:

Sprint ticks

too-many-attributes:sprint_ticksentity condition

What it checks, in one or two sentences.

Field	Type	Default	Description

An example with an explanation.

• Field types use the Origins names: Comparison ("<", "<=", ">", ">=", "==", "!="), Integer, Float, Double, String, Identifier, and the Origins "type" data types, such as Bi-entity condition type.
• Default: required means the field has no default and must be given.
• Enum fields (like axis or component) accept any capitalization: "y" and "Y" both work.
• Confidence notes. Descriptions come from the mod's source code. A note marked (Suspected) is an inference that hasn't been confirmed. Check it in-game before relying on it.

Things that apply to every page

• Ticks. A tick is 1/20 of a second: 20 ticks = 1 second, 1200 ticks = 1 minute.
• Bi-entity pairs. In a bi-entity condition or action, the actor is the first entity, usually the power holder (self). The target is the second entity, the one being hit, looked at, and so on (other). This matches Origins.

• Tracked values live on the server and aren't saved. Several conditions read values TMA records as things happen: last damage, recent damage, knockback, attack reach, shield angle, time since last meal, airborne and sprint ticks, crouch depth, vibration cooldown, and the voice chat state. They are:

  • kept in memory on the server, per entity
  • reset when the server restarts, and never written to the world
  • forgotten when a mob or other non-player entity leaves the world: killed, removed, or unloaded with its chunk. Changing dimension keeps them.
  • kept for players through deaths and logouts, until the player has been offline longer than the gamerule tmaPlayerExpiryDays (real days, default 30, 0 = never). The global store uses the same gamerule for keys bound to a player.
  • 0 / false on the client. A condition Origins checks on the client, such as a hud_render condition, reads them as 0 or false. The attributes are synced to clients every tick, so client-side checks can use origins:attribute instead.
• Players versus other entities. Some conditions only work on players (they're false for anything else). Each entry says so.

TMA's 40 general entity conditions. They go anywhere Origins accepts an entity condition: a power's condition, origins:and/or, if_else, a target_condition, and so on.

Most of them compare a number, the same way Origins' own number conditions do:

Every entry below also lists its attribute (page 7), when it has one. Voice chat conditions are on page 13, and expression / with_variables on pages 8 and 9.

is_downed (below) is an optional integration: it needs Hardcore Revival installed, and is simply false without it.

"Tracked" marks a value TMA records while the game runs. It lives on the server, resets on restart, and reads as 0 on the client (page 1).

At a glance

Removed in 2.1.0 because Origins already has them. Use the Origins type instead:

Their attributes were removed too. The full list, including bi-entity and item conditions, is in Upgrading to 2.1.0.

Combat

Attack cooldown progress

too-many-attributes:attack_cooldown_progressentity conditionplayers only

How charged the player's attack is, from 0.0 (just swung) to 1.0 (fully charged). This is the value behind vanilla's attack indicator.

Example:

{
  "type": "origins:modify_damage_dealt",
  "condition": { "type": "too-many-attributes:attack_cooldown_progress", "comparison": "<", "compare_to": 0.5 },
  "modifier": { "operation": "multiply_total_multiplicative", "value": -0.5 }
}

Hits made before the attack is half charged deal half damage, on top of vanilla's own reduction.

Attribute: attack_cooldown_progress

Critical hit eligible

too-many-attributes:critical_hit_eligibleentity conditionplayers only

True when the player is in the air in a way that makes a hit a critical: falling (fall distance above 0), not on the ground, not riding anything, and not sprinting.

No fields.

• This is simpler than vanilla's check. Vanilla also requires a charged attack (above 0.9), not climbing, not in water, and no Blindness. Add attack_cooldown_progress to get closer.

Example:

{
  "type": "origins:modify_damage_dealt",
  "condition": {
    "type": "origins:and",
    "conditions": [
      { "type": "too-many-attributes:critical_hit_eligible" },
      { "type": "too-many-attributes:attack_cooldown_progress", "comparison": ">=", "compare_to": 0.9 }
    ]
  },
  "modifier": { "operation": "multiply_total_multiplicative", "value": 0.25 }
}

Critical hits deal 25% more, on top of vanilla's critical bonus.

Attribute: critical_hit_eligible

Last attack reach

too-many-attributes:last_attack_reachentity conditionplayers onlytracked

The distance, in blocks, between the player and the entity they last attacked, measured as the attack starts.

• It's 0 until the player first attacks, and keeps its value until the next attack.
• It's recorded at the start of the attack, before damage is worked out, so inside modify_damage_dealt it's the distance of the current hit. (From source.)

Example:

{
  "type": "origins:modify_damage_dealt",
  "condition": { "type": "too-many-attributes:last_attack_reach", "comparison": ">", "compare_to": 2.5 },
  "modifier": { "operation": "multiply_total_multiplicative", "value": 0.25 }
}

Hits landed from more than 2.5 blocks away deal 25% more: a spear-tip bonus.

Attribute: last_attack_reach

Hurt time

too-many-attributes:hurt_timeentity condition

Ticks left in the entity's "just got hurt" animation (the red flash). Set to 10 when it takes damage, then counts down by 1 each tick to 0.

• False for entities that aren't living (like boats).

Example:

{
  "type": "origins:modify_damage_dealt",
  "condition": { "type": "too-many-attributes:hurt_time", "comparison": ">", "compare_to": 0 },
  "modifier": { "operation": "multiply_total_multiplicative", "value": 0.3 }
}

For half a second after being hurt, your hits deal 30% more: retaliation.

Attribute: hurt_time

Invulnerable ticks

too-many-attributes:invulnerable_ticksentity condition

Ticks left in the entity's damage cooldown. When hurt, it's set to 20 and counts down. While it's above 10, a new hit only gets through if it's stronger than the last one.

Example:

{
  "type": "origins:action_over_time",
  "interval": 1,
  "condition": { "type": "too-many-attributes:invulnerable_ticks", "comparison": ">", "compare_to": 10 },
  "entity_action": {
    "type": "origins:execute_command",
    "command": "particle minecraft:enchanted_hit ~ ~1 ~ 0.3 0.5 0.3 0 2"
  }
}

Sparkles while you're protected from weaker follow-up hits.

Attribute: invulnerable_ticks

Recent damage taken

too-many-attributes:recent_damage_takenentity conditiontracked

The total damage the entity took in the last window_ticks ticks.

• It adds up the raw damage of each hit as it arrives, before armor, enchantments and effects reduce it. (From source.)
• Hits fully blocked by a shield aren't counted; recent damage blocked adds those up instead.
• (From source) Hits ignored because of the damage cooldown (invulnerable ticks) are still counted.
• False for entities that aren't living.

Example: berserk.

{
  "type": "origins:action_over_time",
  "interval": 20,
  "condition": {
    "type": "too-many-attributes:recent_damage_taken",
    "window_ticks": 100,
    "comparison": ">",
    "compare_to": 10
  },
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:strength", "duration": 40, "amplifier": 0 }
  }
}

After taking more than 10 damage (5 hearts) within 5 seconds, you get Strength, refreshed every second while that stays true.

Attribute: recent_damage_taken (always a 60-tick window)

Recent damage blocked

too-many-attributes:recent_damage_blockedentity conditiontracked

The total damage the entity blocked with a shield in the last window_ticks ticks. The blocked-hits counterpart of recent damage taken.

• It adds up the raw damage of each blocked hit, as it would have been before armor. (From source.)
• Hits that got past the shield aren't counted; those go to recent damage taken.
• (From source) Blocked hits during the damage cooldown (invulnerable ticks) are still counted.
• False for entities that aren't living.

Example: shield bash.

{
  "type": "origins:action_over_time",
  "interval": 20,
  "condition": {
    "type": "too-many-attributes:recent_damage_blocked",
    "window_ticks": 100,
    "comparison": ">=",
    "compare_to": 12
  },
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:strength", "duration": 40, "amplifier": 0 }
  }
}

After blocking 12 or more damage within 5 seconds, you get Strength, refreshed every second while that stays true.

Attribute: recent_damage_blocked (always a 60-tick window)

Last damage amount

too-many-attributes:last_damage_amountentity conditiontracked

The raw damage of the most recent hit the entity took, before armor and effects.

• It keeps its value until the next hit, so combine it with hurt_time for "just now".
• Hits blocked by a shield count here too.

Example: heavy hits stagger you.

{
  "type": "origins:action_over_time",
  "interval": 1,
  "condition": {
    "type": "origins:and",
    "conditions": [
      { "type": "too-many-attributes:hurt_time", "comparison": ">=", "compare_to": 9 },
      { "type": "too-many-attributes:last_damage_amount", "comparison": ">=", "compare_to": 8 }
    ]
  },
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:slowness", "duration": 20, "amplifier": 1 }
  }
}

Right after a hit of 8 or more damage, you get Slowness II for a second.

Attribute: last_damage_amount

Last damage type

too-many-attributes:last_damage_typeentity conditiontracked

True when the most recent hit was of this damage type.

• It's the message id (the name death messages use), not the damage type's registry id. For example, minecraft:player_attack has the message id player. Common ones: fall, player, mob, arrow, lava, inFire, onFire, drown, magic. (From source: vanilla damage type data.)
• It's "" until the entity first takes damage, and keeps its value until the next hit.

Example: land roll.

{
  "type": "origins:action_over_time",
  "interval": 1,
  "condition": {
    "type": "origins:and",
    "conditions": [
      { "type": "too-many-attributes:hurt_time", "comparison": ">=", "compare_to": 9 },
      { "type": "too-many-attributes:last_damage_type", "value": "fall" }
    ]
  },
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:speed", "duration": 40, "amplifier": 1 }
  }
}

Right after taking fall damage, you get Speed II for 2 seconds.

Recent knockback

too-many-attributes:recent_knockbackentity conditiontracked

The strength of the last knockback the entity received. Vanilla melee knockback is about 0.4, and the Knockback enchantment adds more.

• It's the strength vanilla asked for, before knockback resistance reduces it. (From source.)
• It keeps its value until the next knockback.

Example:

{
  "type": "origins:action_over_time",
  "interval": 1,
  "condition": {
    "type": "origins:and",
    "conditions": [
      { "type": "too-many-attributes:hurt_time", "comparison": ">=", "compare_to": 9 },
      { "type": "too-many-attributes:recent_knockback", "comparison": ">=", "compare_to": 1.0 }
    ]
  },
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:slow_falling", "duration": 40, "amplifier": 0 }
  }
}

When you're knocked back hard, you get Slow Falling so you don't take fall damage.

Attribute: recent_knockback

Last hit was crit

too-many-attributes:last_hit_was_critentity conditiontracked

True when the entity's most recent attack was a critical hit: the jump attack, or a fully drawn bow shot. It stays true until that entity attacks again without critting.

No fields.

• Melee and arrows both count. A melee crit is vanilla's own decision (falling, not on the ground, not sprinting, not riding, attack charged), and an arrow counts when it was a critical arrow.
• It's set as the hit resolves, not before it. Inside origins:modify_damage_dealt or origins:action_on_hit for that hit, it still holds the previous attack's answer. To react to a crit, run the check a tick later (an action_over_time with interval: 1 and a rising_action), or use critical_hit_eligible, which asks whether a hit would crit right now.
• It's false until the entity's first attack, isn't saved, and resets when the server restarts.

Example: after landing a critical hit, you glow briefly.

{
  "type": "origins:action_over_time",
  "interval": 1,
  "condition": { "type": "too-many-attributes:last_hit_was_crit" },
  "rising_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:glowing", "duration": 40 }
  }
}

rising_action runs on the tick the condition turns true, which is the tick after the crit lands.

No attribute.

Last damage was crit

too-many-attributes:last_damage_was_critentity conditiontracked

True when the last damage this entity took was a critical hit, melee or a critical arrow. Any other damage, including a normal hit, fall damage or fire, sets it back to false.

No fields.

• It's set just after that damage is applied, so like the condition above it isn't ready during the hit itself. Check it from a later tick.
• It's false until the entity is first damaged, and isn't saved.

Example: being critted makes you flee-footed for a moment.

{
  "type": "origins:action_over_time",
  "interval": 1,
  "condition": { "type": "too-many-attributes:last_damage_was_crit" },
  "rising_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:speed", "duration": 60, "amplifier": 1 }
  }
}

No attribute.

Is blocking

too-many-attributes:is_blockingentity condition

True while the entity is blocking with a shield (after the shield has finished rising).

No fields.

Example:

{
  "type": "origins:modify_damage_taken",
  "condition": { "type": "too-many-attributes:is_blocking" },
  "modifier": { "operation": "multiply_total_multiplicative", "value": -0.2 }
}

While blocking, hits that get past the shield (from the side or behind) deal 20% less.

Attribute: is_blocking

Movement

Velocity

too-many-attributes:velocityentity condition

The entity's velocity along one axis, in blocks per tick.

Example: feather fall.

{
  "type": "origins:action_over_time",
  "interval": 1,
  "condition": { "type": "too-many-attributes:velocity", "axis": "y", "comparison": "<", "compare_to": -1.0 },
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:slow_falling", "duration": 10, "amplifier": 0 }
  }
}

When you fall faster than 1 block per tick, you get Slow Falling.

Attributes: velocity_x, velocity_y, velocity_z

Look angle

too-many-attributes:look_angleentity condition

Where the entity is looking.

• Pitch: −90 is straight up, 0 level, 90 straight down.
• Yaw: 0 faces south (+Z), 90 west, ±180 north, −90 east. (Suspected: the raw yaw isn't wrapped, so after turning around several times it can be outside −180 – 180. The attribute is clamped to that range.)

Example: stargazer.

{
  "type": "origins:action_over_time",
  "interval": 40,
  "condition": {
    "type": "origins:and",
    "conditions": [
      { "type": "too-many-attributes:look_angle", "component": "pitch", "comparison": "<=", "compare_to": -70 },
      { "type": "origins:daytime", "inverted": true },
      { "type": "origins:exposed_to_sky" }
    ]
  },
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:regeneration", "duration": 50, "amplifier": 0 }
  }
}

Looking up at the open night sky regenerates you.

Attributes: look_pitch, look_yaw

Is jumping

too-many-attributes:is_jumpingentity condition

True while the entity's jump input is held.

No fields.

Attribute: is_jumping

Time airborne

too-many-attributes:time_airborneentity conditionplayers onlytracked

Ticks since the player was last on the ground. 0 while on the ground.

• Anything that isn't "on the ground" counts: jumping, falling, swimming, flying and gliding.

Example: glider.

{
  "type": "origins:action_over_time",
  "interval": 1,
  "condition": { "type": "too-many-attributes:time_airborne", "comparison": ">", "compare_to": 60 },
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:slow_falling", "duration": 10, "amplifier": 0 }
  }
}

After 3 seconds in the air, you fall slowly.

Attribute: time_airborne

Sprint ticks

too-many-attributes:sprint_ticksentity conditionplayers onlytracked

Ticks the player has been sprinting without stopping. Goes back to 0 the moment they stop.

Example: second wind.

{
  "type": "origins:action_over_time",
  "interval": 20,
  "condition": { "type": "too-many-attributes:sprint_ticks", "comparison": ">=", "compare_to": 60 },
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:speed", "duration": 30, "amplifier": 0 }
  }
}

After 3 seconds of non-stop sprinting, you get Speed.

Attribute: sprint_ticks

Crouch depth

too-many-attributes:crouch_depthentity conditionplayers onlytracked

How far into a sneak the player is, from 0.0 (standing) to 1.0 (fully crouched). It moves a third of the way toward 1 each tick while sneaking, and back toward 0 when not, so a full crouch takes 3 ticks.

• Only players are tracked; it's 0 for other entities.

Example:

{
  "type": "origins:modify_damage_taken",
  "condition": { "type": "too-many-attributes:crouch_depth", "comparison": ">=", "compare_to": 1.0 },
  "modifier": { "operation": "multiply_total_multiplicative", "value": -0.1 }
}

While fully crouched, you take 10% less damage.

Attribute: crouch_depth

Glide ratio

too-many-attributes:glide_ratioentity condition

While flying with an elytra: horizontal speed divided by vertical speed. High values mean a flat glide; low values mean a steep dive. With almost no vertical movement, it's the horizontal speed × 1000.

• False when not gliding, whatever the comparison.

Example:

{
  "type": "origins:action_over_time",
  "interval": 2,
  "condition": { "type": "too-many-attributes:glide_ratio", "comparison": "<", "compare_to": 1.0 },
  "entity_action": {
    "type": "origins:execute_command",
    "command": "particle minecraft:cloud ~ ~ ~ 0.2 0.2 0.2 0 3"
  }
}

A trail of cloud particles while you dive steeply.

Attribute: glide_ratio (0 when not gliding)

Is moving loudly

too-many-attributes:is_moving_loudlyentity condition

True while the entity is on the ground, not crouching, and moving faster than 0.15 blocks per tick horizontally, like walking or running.

No fields.

• For players, this also drives the automatic vibration cooldown.

Example:

{
  "type": "origins:action_over_time",
  "interval": 10,
  "condition": { "type": "too-many-attributes:is_moving_loudly" },
  "entity_action": {
    "type": "origins:execute_command",
    "command": "particle minecraft:sculk_charge_pop ~ ~0.1 ~ 0.3 0 0.3 0 3"
  }
}

Sculk particles puff up from your steps while you move loudly.

Attribute: is_moving_loudly

Friction

too-many-attributes:frictionentity condition

The friction the entity gets from the block it's moving on. It's that block's slipperiness, after any origins:modify_slipperiness powers the entity has that apply to that block.

• Block values: 0.6 for most blocks, 0.8 for slime blocks, 0.98 for ice, packed ice and frosted ice, and 0.989 for blue ice. Higher is slipperier.
• The block is the one vanilla uses for movement: half a block below the feet. That position and the power modifiers are taken exactly as Origins applies them. (From source: Apoli 2.9.2 LivingEntityMixin.)
• In the air it still reads whatever is half a block below. That's usually air, which is 0.6. Vanilla only uses block friction on the ground, so add origins:on_block when that matters.
• Reading instead of checking: to test a block's own slipperiness without the power modifiers, use Origins' origins:on_block with an origins:slipperiness block condition. This condition, and its attribute, give you the effective value, which Origins can't read.

Example: skates. Faster on anything slippery.

{
  "type": "origins:conditioned_attribute",
  "condition": {
    "type": "origins:and",
    "conditions": [
      { "type": "origins:on_block" },
      { "type": "too-many-attributes:friction", "comparison": ">=", "compare_to": 0.9 }
    ]
  },
  "modifier": {
    "attribute": "minecraft:generic.movement_speed",
    "operation": "multiply_base",
    "value": 0.3
  },
  "tick_rate": 10
}

On ice, blue ice, or ground a modify_slipperiness power has made slippery, you move 30% faster.

Attribute: friction (clamped to 0 – 2)

Submersion depth

too-many-attributes:submersion_depthentity condition

How many fluid blocks are above the entity's eyes, counting the block at eye level, up to 16. 0 when the entity isn't in water, or when its eyes are above the surface.

Example: water pressure.

{
  "type": "origins:action_over_time",
  "interval": 20,
  "condition": { "type": "too-many-attributes:submersion_depth", "comparison": ">=", "compare_to": 6 },
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:mining_fatigue", "duration": 30, "amplifier": 0 }
  }
}

Six or more blocks under water, you get Mining Fatigue.

Attribute: submersion_depth

Body

Exhaustion

too-many-attributes:exhaustionentity conditionplayers only

The player's food exhaustion. Actions like sprinting, jumping and fighting raise it. When it passes 4.0, vanilla takes 4 away and removes a point of saturation or food.

Example:

{
  "type": "origins:action_over_time",
  "interval": 10,
  "condition": { "type": "too-many-attributes:exhaustion", "comparison": ">=", "compare_to": 3.5 },
  "entity_action": {
    "type": "origins:execute_command",
    "command": "title @s actionbar {\"text\":\"You feel tired…\",\"color\":\"gray\"}"
  }
}

A warning just before you lose food.

Attribute: exhaustion

Time since last meal

too-many-attributes:time_since_last_mealentity conditionplayers onlytracked

Ticks since the player's food level last went up.

• TMA notices a meal by the food level rising. (Suspected: anything else that raises it, like Peaceful difficulty or a power that feeds you, counts as a meal too.)
• A player who hasn't eaten since the server started has a very large value, so ">" checks are true.

Example:

{
  "type": "origins:action_over_time",
  "interval": 100,
  "condition": { "type": "too-many-attributes:time_since_last_meal", "comparison": ">", "compare_to": 12000 },
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:weakness", "duration": 120, "amplifier": 0 }
  }
}

If you haven't eaten in 10 minutes, you're weakened.

Attribute: time_since_last_meal

XP progress

too-many-attributes:xp_progressentity conditionplayers only

Progress toward the next experience level, from 0.0 to 1.0: how full the XP bar is.

Example:

{
  "type": "origins:modify_damage_dealt",
  "condition": { "type": "too-many-attributes:xp_progress", "comparison": ">=", "compare_to": 0.9 },
  "modifier": { "operation": "multiply_total_multiplicative", "value": 0.1 }
}

When you're about to level up, your hits deal 10% more.

Attribute: xp_progress

Stat

too-many-attributes:statentity conditionplayers onlyserver only

Compares one of the player's vanilla statistics: the numbers on the Statistics screen, such as blocks mined, jumps, distance walked, mobs killed or items crafted. They're lifetime totals, saved with the player.

Stat types: minecraft:mined, minecraft:crafted, minecraft:used, minecraft:broken, minecraft:picked_up, minecraft:dropped (the id is a block or item), minecraft:killed, minecraft:killed_by (an entity type), and minecraft:custom (the id is a general stat like minecraft:jump, minecraft:deaths, minecraft:play_time or minecraft:walk_one_cm).

• Units are vanilla's. Distances are in centimetres (walk_one_cm: 100 = 1 block), times are in ticks (play_time), and damage is in tenths of a heart-point (damage_dealt: 10 = 1 damage).
• Server only. The client doesn't have stats, so in client-checked places like hud_render this is always false.
• To change a stat, use Origins' origins:modify_stat. For maths on stats (per hour, ratios), use Stat.get in code.

Example: "Veteran miner". After mining 10,000 stone, you mine faster.

{
  "type": "origins:modify_break_speed",
  "condition": {
    "type": "too-many-attributes:stat",
    "stat": { "type": "minecraft:mined", "id": "minecraft:stone" },
    "comparison": ">=",
    "compare_to": 10000
  },
  "modifier": { "operation": "multiply_total_multiplicative", "value": 0.2 }
}

No attribute: statistics are an open-ended list.

Is sleeping

too-many-attributes:is_sleepingentity condition

True while the entity is asleep: a player lying in a bed, or a villager sleeping at night.

No fields.

• It turns true the moment sleep starts, not when the night skips. To run something once at that moment, use the action_on_sleep_start power.
• Sleeping is synced to clients, so this also works in client-checked places like hud_render. (Suspected; not yet checked in-game.)

Example: a sleeper's regeneration.

{
  "type": "origins:action_over_time",
  "interval": 40,
  "condition": { "type": "too-many-attributes:is_sleeping" },
  "entity_action": { "type": "origins:heal", "amount": 1 }
}

While you sleep, you heal half a heart every 2 seconds.

No attribute.

World

Light at eyes

too-many-attributes:light_at_eyesentity condition

The light level at the entity's eye height, 0 – 15: the brighter of block light and sky light, with sky light dimmed at night and in rain.

Example: light-sensitive.

{
  "type": "origins:action_over_time",
  "interval": 20,
  "condition": { "type": "too-many-attributes:light_at_eyes", "comparison": ">=", "compare_to": 12 },
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:weakness", "duration": 30, "amplifier": 0 }
  }
}

Bright light weakens you.

Attribute: light_at_eyes

Biome temperature

too-many-attributes:biome_temperatureentity condition

The base temperature of the biome the entity is in, not adjusted for height. For example: snowy plains 0.0, plains 0.8, jungle 0.95, desert and the Nether 2.0, frozen peaks −0.7.

Example: heat-adapted.

{
  "type": "origins:action_over_time",
  "interval": 40,
  "condition": { "type": "too-many-attributes:biome_temperature", "comparison": ">=", "compare_to": 1.5 },
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:fire_resistance", "duration": 60, "amplifier": 0 }
  }
}

Fire Resistance in hot biomes (deserts, badlands, savannas and the Nether).

Attribute: biome_temperature

Moon phase

too-many-attributes:moon_phaseentity condition

The current moon phase, 0 – 7. 0 is the full moon and 4 the new moon.

Example: werewolf.

{
  "type": "origins:action_over_time",
  "interval": 20,
  "condition": {
    "type": "origins:and",
    "conditions": [
      { "type": "too-many-attributes:moon_phase", "comparison": "==", "compare_to": 0 },
      { "type": "origins:daytime", "inverted": true }
    ]
  },
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:strength", "duration": 30, "amplifier": 1 }
  }
}

On full-moon nights, you get Strength II.

Attribute: moon_phase

Regional difficulty

too-many-attributes:regional_difficultyentity condition

The local difficulty where the entity stands, 0.0 – 6.75. It grows with the world's difficulty setting, how long players have spent in that chunk, and the moon phase. It's the "Local Difficulty" shown on the F3 screen.

Example:

{
  "type": "origins:modify_damage_dealt",
  "condition": { "type": "too-many-attributes:regional_difficulty", "comparison": ">=", "compare_to": 4 },
  "modifier": { "operation": "multiply_total_multiplicative", "value": 0.2 }
}

In dangerous areas, you rise to the challenge: +20% damage.

Attribute: regional_difficulty

Distance to nearest player

too-many-attributes:distance_to_nearest_playerentity condition

The distance, in blocks, to the closest other player in the same dimension. With no other players there, it's a huge number, so ">" checks are true.

Example: hermit.

{
  "type": "origins:action_over_time",
  "interval": 40,
  "condition": { "type": "too-many-attributes:distance_to_nearest_player", "comparison": ">", "compare_to": 100 },
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:regeneration", "duration": 50, "amplifier": 0 }
  }
}

More than 100 blocks from everyone else, you slowly regenerate.

Attribute: distance_to_nearest_player (clamped to 1,000,000)

Has power tag

too-many-attributes:has_power_tagentity conditionalso a bi-entity condition

True when the entity holds a power in a power tag: a group of powers listed in a datapack file. Full details, the file format and the /tma powertag command are on page 16.

A tag name without a namespace gets the namespace of the power the condition is written in.

{ "type": "too-many-attributes:has_power_tag", "tag": "mypack:magic" }

No attribute.

Redstone power

too-many-attributes:redstone_powerentity condition

The redstone signal, 0 to 15, reaching the block the entity's feet are in. It's the entity version of the redstone_power block condition, which has the full description and more modes.

{ "type": "too-many-attributes:redstone_power", "comparison": ">=", "compare_to": 1 }

Attribute: redstone_power

Mobs and other entities

Has attack target

too-many-attributes:has_attack_targetentity condition

True when the entity is a mob that currently has any attack target.

No fields.

• False for anything that isn't a mob, such as players.
• It covers both kinds of mob AI: goal-based mobs like zombies and skeletons (their target), and brain-based mobs like piglins, hoglins and wardens (their attack-target memory). (Fixed in 2.1.0; before that, goal-based mobs were missed.)
• To check whether a mob is targeting a specific entity, use Origins' origins:attack_target bi-entity condition.

Example:

{
  "type": "origins:modify_damage_dealt",
  "target_condition": { "type": "too-many-attributes:has_attack_target" },
  "modifier": { "operation": "multiply_total_multiplicative", "value": 0.25 }
}

Your hits deal 25% more to mobs that are busy hunting someone.

Projectile age

too-many-attributes:projectile_ageentity condition

How many ticks the entity has existed since it was created or last loaded. It works on any entity, but it's most useful on projectiles: how long an arrow has been flying.

• The count isn't saved. It starts again at 0 when the entity is loaded from a chunk (and for a player, when they join).

Example: long-range arrows hurt you less.

{
  "type": "origins:modify_damage_taken",
  "damage_condition": {
    "type": "origins:projectile",
    "projectile_condition": { "type": "too-many-attributes:projectile_age", "comparison": ">=", "compare_to": 40 }
  },
  "modifier": { "operation": "multiply_total_multiplicative", "value": -0.5 }
}

Projectiles that were in flight for 2 seconds or more deal half damage to you.

Items

Item on cooldown

too-many-attributes:item_on_cooldownentity conditionplayers only

Checks vanilla's item cooldown: the one that greys out an ender pearl or chorus fruit in the hotbar after you use it, or a shield after an axe hits it. This isn't Origins' origins:cooldown power; that's a separate timer, and nothing in Origins reads this one.

• Without comparison it's true while the item is on cooldown at all.
• With comparison, an item that isn't on cooldown has 0 ticks left.
• Cooldowns belong to the item type, not the stack: every ender pearl is on the same cooldown. In 1.20.1 there are no cooldown groups, so each item has its own.
• An empty slot is never on cooldown. A bad slot name is an error when the datapack loads.
• Vanilla sends cooldowns to the client, so this also works in client-checked places like hud_render.
• Set one yourself with set_item_cooldown. Read the ticks in code with Item.cooldown.

Example: a pearl's recoil. While your ender pearl is cooling down, you're slower.

{
  "type": "origins:conditioned_attribute",
  "condition": { "type": "too-many-attributes:item_on_cooldown", "item": "minecraft:ender_pearl" },
  "modifier": {
    "attribute": "minecraft:generic.movement_speed",
    "operation": "multiply_base",
    "value": -0.3
  },
  "tick_rate": 1
}

For the 20 ticks after you throw a pearl, you move 30% slower.

Example: the item in your hand has more than 5 seconds of cooldown left.

{ "type": "too-many-attributes:item_on_cooldown", "comparison": ">", "compare_to": 100 }

Attribute: mainhand_cooldown (ticks left on the item in your main hand)

Vibrations

Vibration on cooldown

too-many-attributes:vibration_on_cooldownentity conditiontracked

True while the entity's vibration cooldown is above 0. This is TMA's own timer, not vanilla sculk:

• Set it with set_vibration_cooldown.
• For players, TMA sets it to 40 ticks automatically each time they move loudly while it's 0.
• It counts down by 1 every tick.

No fields.

For a moving player, it turning true means "a vibration just happened". Origins' rising_action runs on exactly that moment.

Example:

{
  "type": "origins:action_over_time",
  "interval": 1,
  "condition": { "type": "too-many-attributes:vibration_on_cooldown" },
  "rising_action": {
    "type": "origins:execute_command",
    "command": "playsound minecraft:block.sculk_sensor.clicking player @a ~ ~ ~ 1 1"
  }
}

Everyone nearby hears a sculk click each time you make a vibration, at most every 2 seconds.

Attributes: vibration_cooldown (ticks left), vibration_on_cooldown

Integrations

Is downed

too-many-attributes:is_downedentity conditionplayers onlyneeds Hardcore Revival

True while the player is knocked out (downed, awaiting rescue or revival) in Hardcore Revival. Without Hardcore Revival installed, this is always false - TMA loads normally either way.

No fields.

Example: crawl speed while downed.

{
  "type": "origins:speed",
  "condition": { "type": "too-many-attributes:is_downed" },
  "modifier": { "operation": "multiply_total_multiplicative", "value": -0.7 }
}

While downed, movement speed drops by 70%.

Attribute: is_downed

A bi-entity condition checks a pair of entities: the actor and the target (page 1). Which entity is which depends on the power or action the condition sits in; the Origins docs say so for each field.

Removed in 2.1.0: is_targeting. Use Origins' origins:attack_target, which does the same and also covers zombies, skeletons and other goal-based mobs.

Is observed by

too-many-attributes:is_observed_bybi-entity condition

True when the target is looking toward the actor: the actor is within max_distance blocks of the target, and inside the target's field of view.

• Only direction and distance are checked. Blocks don't hide you: an actor behind a wall still counts as observed. (From source.) For line of sight, add Origins' origins:can_see bi-entity condition in an origins:and.
• The angle is measured from the target's position toward the actor's position, compared with the target's look direction (including pitch).

Example: a backstab.

{
  "type": "origins:modify_damage_dealt",
  "bientity_condition": {
    "type": "too-many-attributes:is_observed_by",
    "fov_degrees": 120,
    "inverted": true
  },
  "modifier": { "operation": "multiply_total_multiplicative", "value": 0.5 }
}

In modify_damage_dealt, the actor is you and the target is the entity you hit. "inverted": true flips the result, so hits on anything that isn't looking toward you (within a 120° cone) deal 50% more damage.

Removed in 2.1.0: the item condition durability_percent. Use Origins' origins:relative_durability, which compares the same fraction (currentDurability / maxDurability). TMA has no item conditions now.

Damage source NBT

too-many-attributes:damage_source_nbtdamage condition

Checks one NBT value on the entity that directly caused the damage: the arrow or other projectile for ranged hits, or the attacker for melee.

• False when there's no direct entity, as with fall damage, fire or drowning.
• The value is compared as text. Strings are compared as they are. Other values use their SNBT form, so a number includes its suffix (1b, 5, 1.5d) and a list includes its brackets. Vanilla saves true/false values as bytes, so "true" is 1b. (From source.)
• Only top-level keys work. There are no paths like Item.id.
• Entity ids aren't in this data; use Origins' origins:projectile damage condition for the projectile type.

Example: crossbow bolts hurt you less.

{
  "type": "origins:modify_damage_taken",
  "damage_condition": {
    "type": "too-many-attributes:damage_source_nbt",
    "key": "ShotFromCrossbow",
    "value": "1b"
  },
  "modifier": { "operation": "multiply_total_multiplicative", "value": -0.3 }
}

Arrows shot from a crossbow deal 30% less damage to you.

TMA's block conditions. They go anywhere Origins accepts a block condition: origins:on_block, origins:in_block, origins:block_in_radius, origins:block_collision, origins:action_on_block_use, a raycast's block_condition, and so on.

Redstone power

too-many-attributes:redstone_powerblock conditionalso an entity condition

The redstone signal strength at a block, from 0 to 15. Origins has no way to read redstone.

The three modes are vanilla's three redstone reads:

• A block with nothing powering it reads 0 in every mode.
• emitted with a direction is what the neighbour on that side would receive from this block. A redstone torch, for example, sends 15 to the sides and up but nothing into the block it's attached to. A solid block that's strongly powered also counts that power as emitted, as vanilla does.
• It's read live when the condition runs, so it follows redstone the same tick it changes.

Example: "Current sense". While you stand on a powered block, you're faster.

{
  "type": "origins:conditioned_attribute",
  "condition": {
    "type": "origins:on_block",
    "block_condition": { "type": "too-many-attributes:redstone_power", "comparison": ">", "compare_to": 0 }
  },
  "modifier": { "attribute": "minecraft:generic.movement_speed", "operation": "multiply_base", "value": 0.3 },
  "tick_rate": 1
}

Example: any fully powered block within 5 blocks of you.

{
  "type": "origins:block_in_radius",
  "radius": 5,
  "block_condition": { "type": "too-many-attributes:redstone_power", "comparison": "==", "compare_to": 15 },
  "comparison": ">=",
  "compare_to": 1
}

Example: a lever that's on, checked from the side the signal leaves through.

{ "type": "too-many-attributes:redstone_power", "mode": "emitted", "direction": "up", "comparison": ">", "compare_to": 0 }

As an entity condition

too-many-attributes:redstone_powerentity condition

The received signal at the block the entity's feet are in, the same as the block condition with no mode, run on that block. It has only comparison and compare_to (Integer, 0 – 15).

• The feet block is the one the entity stands in, not the one under it, and received means power coming into that block from its neighbours. A pressure plate you stand on doesn't power its own block, so it doesn't count. A strongly powered block under you does. For the block underneath, use origins:on_block with the block condition, as in the first example.

{ "type": "too-many-attributes:redstone_power", "comparison": ">=", "compare_to": 1 }

Attribute: redstone_power (the same value, for players)

TMA's actions, and the page each one is documented on:

This page also covers the event powers: power types that run actions on death, join, disconnect, start tracking, mob conversion and sleep start. It also covers signals (emit_signal and the action_on_signal power), fake blocks (set_fake_block and the fake_blocks power), and the power type action_on_chat, which runs actions on chat messages.

Set vibration cooldown

too-many-attributes:set_vibration_cooldownentity action

Sets the entity's vibration cooldown, in ticks. This is TMA's own per-entity timer, checked with vibration_on_cooldown and the vibration_cooldown attribute. It counts down by 1 every tick.

How the timer behaves:

• It's not vanilla's sculk cooldown. It doesn't change when sculk sensors or wardens react. It's a value for your own powers to read, for a "vibration" or "noise" mechanic.
• Players set it themselves. At the end of every server tick, a player who moves loudly while the cooldown is 0 gets a cooldown of 40 ticks, the same re-trigger delay as a vanilla sculk sensor. So while a player keeps running, it's on cooldown about every 40 ticks, and vibration_on_cooldown turning true means "a vibration just happened".
• Setting a long cooldown hides a player's noise for that long, because the automatic 40 only applies when it's 0.
• It isn't saved and resets when the server restarts.

Example: "Hush". Press your primary key to stay silent for 10 seconds.

{
  "type": "origins:active_self",
  "key": { "key": "key.origins.primary_active" },
  "cooldown": 600,
  "hud_render": { "should_render": true },
  "entity_action": {
    "type": "too-many-attributes:set_vibration_cooldown",
    "ticks": 200
  }
}

For 200 ticks the cooldown stays above 0. Any power that reacts to fresh vibrations (for example, one that alerts nearby players when vibration_on_cooldown turns true) stays quiet until it runs out.

Set item cooldown

too-many-attributes:set_item_cooldownentity actionplayers only

Puts an item on vanilla's item cooldown, or takes it off. It's the cooldown ender pearls and chorus fruit use: the item greys out in the hotbar and can't be used until it runs out. It works on any item: vanilla checks the cooldown before every right-click use, so a block on cooldown can't be placed and a bow can't be drawn. Attacking with it still works. Check it with item_on_cooldown.

• It replaces any cooldown the item already has, longer or shorter.
• Cooldowns belong to the item type: cooling down the pearl in your hand cools down every pearl.
• An empty slot does nothing. A bad slot name is an error when the datapack loads.
• Vanilla sends the change to the player, so the hotbar shows it. Like vanilla's, it isn't saved: it's gone after relogging.

Example: "Anchor". Getting hit locks your ender pearls for 5 seconds.

{
  "type": "origins:action_when_damage_taken",
  "entity_action": {
    "type": "too-many-attributes:set_item_cooldown",
    "item": "minecraft:ender_pearl",
    "ticks": 100
  },
  "cooldown": 1
}

Example: clear the cooldown on whatever you're holding.

{ "type": "too-many-attributes:set_item_cooldown", "ticks": 0 }

Set rotation

too-many-attributes:set_rotationentity action

Turns the entity to face a direction. Origins has no action that changes where an entity looks.

How it works:

• Players: the server sends a teleport that keeps the position and only changes the view, because a player's client decides where they look. Movement isn't reset. (Suspected: no visible rubber-banding. Check in-game.)
• Mobs: the head and body turn too. Their AI may turn them back on its next tick, so run the action every tick if a mob needs to keep facing a way.
• Other entities (armor stands, projectiles) just get the new angles.
• Cost: for players, each call that changes the view sends a packet. Smooth turning with max_step sends one per call, so it's more packets than one snap. Set min_step (for example 1) so calls stop once the view is already close enough, which also avoids tiny camera jitters.

Example: "Compass lock". While sneaking, your view turns north, 10 degrees per tick.

{
  "type": "origins:action_over_time",
  "interval": 1,
  "condition": { "type": "origins:sneaking" },
  "entity_action": {
    "type": "too-many-attributes:set_rotation",
    "yaw": 180,
    "pitch": 0,
    "max_step": 10,
    "min_step": 1
  }
}

Look at

too-many-attributes:look_atentity action and bi-entity action

Turns an entity's eyes toward a point, with the same turning rules as set_rotation.

As an entity action, it looks at a position:

As a bi-entity action, the actor looks at the target:

Example: "Stare down". Hitting a mob turns your view to its eyes.

{
  "type": "origins:action_on_hit",
  "bientity_action": { "type": "too-many-attributes:look_at", "anchor": "eyes" },
  "cooldown": 1
}

Example (an action): make everything within 8 blocks of you turn to look at you (for mobs, only until their AI turns them away).

{
  "type": "origins:area_of_effect",
  "radius": 8,
  "bientity_action": {
    "type": "origins:invert",
    "action": { "type": "too-many-attributes:look_at" }
  }
}

Play block crack

too-many-attributes:play_block_crackblock action

Shows the crack overlay you see while mining a block, stepping from stage 0 to 9 over a set time, without anyone mining it. Nothing happens to the block itself unless on_finish is break.

It's a block action, so it goes wherever Origins takes one: origins:block_action_at (the block at an entity's position), a raycast's block_action, origins:action_on_block_use, and so on.

• One crack per block. While a crack is running or held at a block, starting another one there does nothing.
• It stops early if the block changes (broken, replaced, or its state changes) or its chunk unloads. The overlay is removed.
• Who sees it: the same players who'd see a real player mining it, in that dimension within 32 blocks. Each stage is sent when it starts, so a player who walks into range sees the crack from the next stage on.
• Air can't crack; the action does nothing on an empty block.
• It isn't saved: cracks stop when the server restarts.

Example: "Rot touch". Right-clicking a block with an empty hand makes it decay and break over 3 seconds.

{
  "type": "origins:action_on_block_use",
  "item_condition": { "type": "origins:empty" },
  "block_action": {
    "type": "too-many-attributes:play_block_crack",
    "duration": 60,
    "on_finish": "break"
  }
}

Spawn phantom

too-many-attributes:spawn_phantomentity action

Spawns a phantom: a mob that only exists on the screens of the players allowed to see it. The server never adds it to the world, so it can't be hit for real, doesn't collide with anyone, and nothing it does changes the world. Everyone else sees nothing. Use it for hallucinations, spirits only one player can see, or jump scares.

Behavior. Mobs walk with their own vanilla pathfinding and physics, but none of their normal AI runs. Fake players move the same way. Instead:

• A chasing phantom stops when it reaches its target (within melee reach) and stands facing them. It follows again if they move away.
• Hitting a phantom does no damage, knockback or sound. It makes a passive phantom chase you and runs its spawner's action_on_phantom_hit powers.
• Entity types that aren't mobs, such as armor stands, just stay where they spawned. Walking mobs move best. Flying or hopping mobs (bats, slimes) may not move well. (Suspected; check in-game.)
• A phantom is silent. It makes no sound for anyone, including its viewers.
• Whatever its type would normally do can't happen: attacks, arrows, explosions, dropping items, trampling crops, pressing pressure plates, pushing entities or setting off sculk sensors.
• It disappears when its lifetime runs out and when the server stops. It isn't saved. It only moves while its chunk is loaded.
• With a viewer_condition, a phantom whose spawner has left (logged out or unloaded) can't be seen by any new viewers.

Example: "Stalker". Every 30 seconds, a zombie only you can see appears 12 blocks behind you and chases you for up to 10 seconds.

{
  "type": "origins:action_over_time",
  "interval": 600,
  "entity_action": {
    "type": "too-many-attributes:spawn_phantom",
    "entity_type": "minecraft:zombie",
    "x": 0, "y": 0, "z": -12,
    "behavior": "hostile",
    "lifetime": 200,
    "viewer_condition": { "type": "origins:equal" }
  }
}

origins:equal is true when the actor and target are the same entity, so only the spawner sees it. The offset is in world directions, not relative to where you face.

Fake players

Set entity_type to minecraft:player and a phantom looks like a player instead of a mob.

{
  "type": "too-many-attributes:spawn_phantom",
  "entity_type": "minecraft:player",
  "skin": "Notch",
  "id": 50,
  "x": 0, "y": 0, "z": 2,
  "lifetime": 200
}

• The skin is looked up by username, the same way the server looks up any account: its own cache first, then Mojang. The lookup happens in the background, so the very first time a name is used the phantom may appear in the default skin for a moment and then change. An offline server, or one with no internet, keeps the default skin.
• It's not in the tab list, and it has no name tag above its head.
• It stands still unless you give it a behavior. Left out, a fake player is stationary; any other behavior makes it walk, chase and wander like a mob.
• How it walks: players have no pathfinding, so an unseen husk (never shown to anyone, and never in the world) does the walking, and the fake player copies where it goes. It moves at a husk's speed, climbs what a husk climbs, and can't open doors. Viewers see the normal player walk animation. (From source; check in-game.)
• Its username and UUID are made up, so it never clashes with the real account, even if that player is online.

From a command: /tma phantom spawn, or /tma phantom skin for a fake player.

Reaching phantoms

A phantom isn't in the world, so nothing that searches the world finds it: selectors like @e, area_of_effect, raycasts and mob targeting all miss it. These TMA types hand the phantom to Origins directly instead.

What works on a phantom (from source; check in-game):

• Looks reach its viewers on the next tick: glowing, invisibility, being on fire, a custom name, pose, and other entity data.
• Movement: velocity (origins:add_velocity), facing, and teleporting in a command (tp @s). A walking phantom may walk off again right away.
• Effects apply and show. They wear off on mobs, but never on fake players, because a fake player doesn't tick. Remove them with origins:clear_effect.
• It can't be hurt or killed, not even by /kill: dying would drop real loot. Use despawn_phantom instead.
• It can't hold powers. Powers only run on entities that tick in the world, so a phantom is only ever the target.
• The rest of the world is real. An action that spawns particles, plays a sound or summons an entity at the phantom does it for everyone, not only its viewers.
• An action that fails on a phantom (something a player-less entity can't do) is skipped and logged, rather than breaking the power.

Phantom action

too-many-attributes:phantom_actionentity action

Runs actions on phantoms.

Example: your phantoms glow for 5 seconds.

{
  "type": "too-many-attributes:phantom_action",
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:glowing", "duration": 100 }
  }
}

Phantom condition

too-many-attributes:phantomentity condition

Counts the phantoms that match, and compares the count.

With only the defaults, it's "this entity has at least one phantom".

Example: true while one of your phantoms is within 3 blocks of you.

{
  "type": "too-many-attributes:phantom",
  "bientity_condition": { "type": "origins:distance", "comparison": "<=", "compare_to": 3 }
}

Action on phantom hit

too-many-attributes:action_on_phantom_hitpower type

Runs when a player who can see one of the holder's phantoms hits it. The holder is the phantom's spawner.

• It runs for every behavior, and a passive phantom still starts chasing whoever hit it.
• The phantom takes no damage or knockback, so use the actions to show the hit.

Example: a decoy that vanishes when it's hit and gives the attacker Slowness.

{
  "type": "too-many-attributes:action_on_phantom_hit",
  "bientity_action": {
    "type": "origins:and",
    "actions": [
      { "type": "origins:actor_action", "action": { "type": "origins:apply_effect", "effect": { "effect": "minecraft:slowness", "duration": 60 } } },
      { "type": "origins:target_action", "action": { "type": "origins:execute_command", "command": "particle minecraft:poof ~ ~1 ~ 0.3 0.5 0.3 0 20" } }
    ]
  },
  "entity_action": { "type": "too-many-attributes:despawn_phantom" }
}

despawn_phantom without an id removes all of the holder's phantoms. With several out at once, give each an id and a matching action_on_phantom_hit.

Despawn phantom

too-many-attributes:despawn_phantomentity action

Removes phantoms early, before their lifetime runs out.

• Ids are unique across the server, so an id removes that phantom whoever spawned it. Without an id, only the running entity's own phantoms go.
• Phantoms from /tma phantom get assigned ids counting up from 1. Picking high numbers for your pack's own ids keeps them clear of those.
• Removing a phantom that isn't there does nothing.
• Viewers see it disappear on the next tick.

Example: a spirit you can summon and dismiss with the same key.

{
  "type": "origins:active_self",
  "key": { "key": "key.origins.secondary_active" },
  "cooldown": 20,
  "entity_action": { "type": "too-many-attributes:despawn_phantom", "id": 7001 }
}

From a command: /tma phantom remove.

Disguise

too-many-attributes:disguiseentity action

Makes other players see the entity as another entity type: a player who looks like a zombie, a cow that looks like a creeper. It's visual only. The entity keeps its own hitbox, health, AI and abilities on the server, and mobs still treat it as what it really is.

• What shows through: the real entity's held items and armor, when the disguise type can show equipment (zombies, skeletons, armor stands, …). Nothing else does: no name tag, no sneaking or swimming pose, no fire, glowing or invisibility effects. An invisible player in a disguise is still visible as the disguise.
• The disguised player sees their own normal body in third person. Only other players see the disguise.
• The client uses the disguise's size to aim at it, so a small disguise on a big entity can be hard to hit, and the other way round.
• Disguising an entity that's already disguised replaces the disguise. It isn't saved: it ends when the entity unloads, a player logs out, or the server stops.

Example: "Skin of the dead". Your primary key disguises you as a zombie for 30 seconds, for players who don't have your origin.

{
  "type": "origins:active_self",
  "key": { "key": "key.origins.primary_active" },
  "cooldown": 1200,
  "entity_action": {
    "type": "too-many-attributes:disguise",
    "entity_type": "minecraft:zombie",
    "duration": 600,
    "viewer_condition": {
      "type": "origins:actor_condition",
      "condition": {
        "type": "origins:origin",
        "origin": "mypack:ghoul",
        "inverted": true
      }
    }
  }
}

Undisguise

too-many-attributes:undisguiseentity action

Ends the entity's disguise. Everyone sees the real entity again. No fields. It does nothing if the entity isn't disguised.

{ "type": "too-many-attributes:undisguise" }

From a command: /tma disguise and /tma undisguise.

Event powers

Six power types that run actions when something happens to the holder. Origins has no power for any of these moments. They all run on the server only.

All six accept Origins' usual condition field: the power does nothing while its condition is false. In bi-entity actions and conditions, the actor is always the holder.

Fields:

What each event means exactly:

• action_on_death runs after the holder has died, so the actions see a dead entity. Use it for effects on the world, the killer or scores, not to save the holder (for that, use origins:prevent_death). The "killer" is the entity credited by the damage source: the shooter of an arrow, not the arrow.
• action_on_join runs once the player is fully in the world, with their powers loaded. That's every login, not just the first one.
• action_on_disconnect runs while the player is leaving, before their data is saved, so variable changes made here are kept.
• action_on_start_tracking is about network range, not sight. It fires when the server starts sending an entity to the player. That range depends on the entity type's tracking range, scaled by the server's entity-broadcast-range-percentage and capped by view distance. Walls, where the player is looking and invisibility don't matter, and it isn't the same as simulation distance. It fires again each time the entity comes back into range, and for every entity near a player who joins or teleports, so keep its condition cheap.
• action_on_mob_conversion covers vanilla conversions such as a zombie villager being cured, a zombie drowning into a drowned, a pig or villager struck by lightning, and a tadpole growing up. The powers belong to the old mob. The new mob doesn't inherit them, so the bi-entity action is the place to set it up.
• action_on_sleep_start runs the moment the holder lies down and falls asleep, before the night is skipped. It only runs for sleep that actually starts: a bed that's too far, a monster nearby, daytime, or an origins:prevent_sleep power stop it from firing. (Suspected from how Fabric's event is called; not yet checked in-game.) Origins' origins:action_on_wake_up covers the other end. To check "asleep right now", use is_sleeping.

Example: "Last words". When you die to another player, they get Glowing for 30 seconds.

{
  "type": "too-many-attributes:action_on_death",
  "bientity_condition": {
    "type": "origins:target_condition",
    "condition": { "type": "origins:entity_type", "entity_type": "minecraft:player" }
  },
  "bientity_action": {
    "type": "origins:target_action",
    "action": { "type": "origins:apply_effect", "effect": { "effect": "minecraft:glowing", "duration": 600 } }
  }
}

Signals

too-many-attributes:emit_signalentity action too-many-attributes:action_on_signalpower type

One power announces something by name, and any power listening for that name reacts. Everything else in Origins is either polled or scanned at one instant; signals let two separately written origins work together without either knowing the other's power ids.

Sending:

Listening:

It also takes Origins' usual condition: a listener ignores signals while it's false.

• The sender never hears its own signals, even with *.
• Any living entity can listen, not just players.
• Signals are instant, not stored: a listener that isn't loaded at that moment misses it.
• A listener's actions can send signals of their own, up to 8 levels deep. Past that they're dropped and the log says so, to stop two powers setting each other off forever.
• Cost: with a radius, only entities in that area are checked. Without one, every loaded entity in the world is checked, so keep those for rare moments.

Example: "War cry". Your primary key sends a signal 24 blocks around you.

{
  "type": "origins:active_self",
  "key": { "key": "key.origins.primary_active" },
  "cooldown": 200,
  "entity_action": { "type": "too-many-attributes:emit_signal", "signal": "mypack:war_cry", "radius": 24 }
}

Example: "Rally". Any origin with this power gets Strength when it hears a war cry from a friend.

{
  "type": "too-many-attributes:action_on_signal",
  "signals": ["mypack:war_cry"],
  "bientity_condition": { "type": "origins:in_same_team" },
  "entity_action": {
    "type": "origins:apply_effect",
    "effect": { "effect": "minecraft:strength", "duration": 200 }
  }
}

Fake blocks

Shows chosen players a different block at a position. The world doesn't change: the real block stays what it was, and only the chosen players are sent something else. Origins' block powers all change the real block.

There are three ways to make one: the set_fake_block action, the fake_blocks power, and /tma fakeblock.

What to know before using any of them:

• Players move by what they see. A fake solid block really stops that player. A fake air block where a real wall stands lets their client walk in, and the server pulls them back. Use fakes for things to look at, or for solid illusions, rather than for fake openings.
• Breaking a fake block doesn't work. The player mines it, the server says the real block is still there, and it comes straight back.
• A real change removes the fake. If the real block is broken, placed or changed by anything, viewers see reality again.
• Fakes aren't saved: they end when the server restarts. They belong to positions, not players, so a player who relogs sees them again.
• Interacting with the real block still happens normally: a fake block over a real chest still opens the chest.

Set fake block

too-many-attributes:set_fake_blockentity action and block action too-many-attributes:clear_fake_blockentity action and block action

• The position is fixed when the action runs. It doesn't follow the entity afterwards.
• Setting a fake at a position that already has one replaces it.
• clear_fake_block takes the same position fields (entity action) or the block it's run on, and removes the fake there.
• Nothing happens in an unloaded chunk.

Example: "Wall of illusion". Right-clicking a block with an empty hand makes it look like bedrock, for everyone, for 10 seconds.

{
  "type": "origins:action_on_block_use",
  "item_condition": { "type": "origins:empty" },
  "block_action": {
    "type": "too-many-attributes:set_fake_block",
    "block": "minecraft:bedrock",
    "duration": 200
  }
}

Fake blocks power

too-many-attributes:fake_blockspower type

While the holder has this power, blocks near them look different. Two modes, and one power can use both.

• Replace mode shows the holder only, unless viewer_condition adds others.
• Cost: replace mode checks every block in the cube each recompute: radius 8 is about 4,900 blocks, radius 16 about 35,900. Raise interval if you use a big radius.
• The power's condition turns it off: the blocks go back to normal within a couple of seconds.

Example: "Ore sight". While the power is active, stone within 8 blocks looks like glass.

{
  "type": "too-many-attributes:fake_blocks",
  "block": "minecraft:glass",
  "block_condition": { "type": "origins:block", "block": "minecraft:stone" },
  "radius": 8,
  "interval": 20
}

Example: a ghost wall two blocks in front of you, that only other players see.

{
  "type": "too-many-attributes:fake_blocks",
  "block": "minecraft:cobweb",
  "offsets": [{ "x": 0, "y": 0, "z": 2 }, { "x": 0, "y": 1, "z": 2 }],
  "rotate_with_facing": true,
  "show_to_holder": false,
  "viewer_condition": { "type": "origins:distance", "comparison": "<=", "compare_to": 16 }
}

Action on chat

too-many-attributes:action_on_chatpower type

Runs actions when a chat message contains certain text. It can react to messages the holder sends (spoken spells, trigger words), messages the holder receives from other players, or both. Origins has no way to read chat.

It also accepts Origins' usual condition: the power ignores chat while it's false.

• Only real chat messages count. /say, /me, /msg, /tell and command blocks don't trigger it.
• The text is what the player typed, before any server formatting.
• Several powers can match the same message, and they all run. If any matching outgoing power hides the message, it's hidden.
• A hidden message runs no incoming powers, since nobody received it.
• Your own message never counts as incoming for you, so direction: both can't run a power twice for one message.
• Everyone online receives every chat message, so "incoming" means any other player's message, from anywhere in the world.

Example: "Word of fire". Saying "ignis" (in any capitalisation) sets every player within 10 blocks on fire. The word isn't shown in chat.

{
  "type": "too-many-attributes:action_on_chat",
  "substrings": ["ignis"],
  "case_sensitive": false,
  "direction": "outgoing",
  "hide_message": true,
  "bientity_condition": { "type": "origins:distance", "comparison": "<=", "compare_to": 10 },
  "bientity_action": {
    "type": "origins:target_action",
    "action": { "type": "origins:set_on_fire", "duration": 5 }
  }
}