denizen-utilities 2.2.0

——————————————————

🏗️ Restructuring of the model system

Model handling is divided into two types of objects: Static and Active.

• <model[(model_name)]> (BMModelTag): A new object representing a model blueprint. Allows you to retrieve data directly from a model blueprint without creating an object in the world.
• <EntityTag.model[(<model_name>)]> (BMActiveModelTag): A renamed legacy tag representing an active model.

New general tags (available for BOTH object types):

• .animations: Returns a ListTag containing all animation names available in the model.
• .animation_duration[<name>]: Returns a DurationTag with the duration of the specified animation.

New tags for active models only (BMActiveModelTag):

• .viewers: Returns all players viewing the model.
• .running_animation: Returns the name of the animation currently playing.
• .running_animation.type: Returns the loop mode (loop, play_once, hold_on_last).

Other new tags:

• EntityTag:
  • .models: A list of the names of all active BetterModel models on an entity.
• PlayerTag:
  • .limb: Direct access to the player’s limb tracker.
• BMBoneTag:
  • .item: Returns the ItemTag of the item currently displayed on this bone.

——————————————————

⚡ Animation signals

Support for Blockbench scripts (Instructions/Effects track) has been implemented.

🚩 Global signals (denizen: prefix) Trigger exactly once at a specified time for the entire server.

• denizen:name{metadata} — Triggers the on bm animation signal event.
• Contexts: <context.model> and any data from {} via <context.key>.
• Example: denizen:shoot.

👥 Personal signals (signal: prefix) Uses the official built-in BetterModel prefix signal:, which triggers the on bm player animation signal event. This is a per-player signal—it fires individually for each player currently viewing the model (for example, if 5 players are viewing the model, the event will execute 5 times—once for each player).

• Contexts: <context.name>.

——————————————————

⚠️ Known limitation and workaround: Currently, a peculiarity (likely a bug) has been observed in BetterModel 3.0: if there are multiple keys with the same prefix on the Instructions track (for example, two denizen: keys), only the last one will trigger.

• Solution: If you need multiple triggers in a row, use the Particle track in Blockbench. Write your scripts in the “Script” field of the particle settings—there, all keys will trigger correctly and in sequence.