kradle 0.6.13 → 0.6.14

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1543,5 +1543,5 @@
1543
1543
  ]
1544
1544
  }
1545
1545
  },
1546
- "version": "0.6.13"
1546
+ "version": "0.6.14"
1547
1547
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "kradle",
3
- "version": "0.6.13",
3
+ "version": "0.6.14",
4
4
  "description": "Kradle's CLI. Manage challenges, experiments, agents and more!",
5
5
  "keywords": [
6
6
  "cli"
@@ -45,6 +45,18 @@ Gather requirements by asking these questions. Save answers in a markdown summar
45
45
 
46
46
  **Important**: roles should just be alphanumeric, no hypen no underscore
47
47
 
48
+ **Targeting a role in Actions:** Roles are implemented as player **tags**, not Minecraft scoreboard teams. To target all players of a role, pass the role name as a string to any Action's `target`:
49
+
50
+ ```typescript
51
+ // Teleport all "red" role players to (15, 0, -60)
52
+ Actions.teleport({ target: "red", x: 15, y: 0, z: -60, absolute: true });
53
+
54
+ // Give items to "blue" role players
55
+ Actions.give({ target: "blue", item: "minecraft:iron_sword", count: 1 });
56
+ ```
57
+
58
+ Under the hood this resolves to `@a[tag=<role>]`. If you need a raw selector, use `Selector("@a", { tag: "red" })` — **not** `{ team: "red" }` (no scoreboard team of that name exists).
59
+
48
60
  ### Things to consider when building a challenge:
49
61
 
50
62
  - Agents don't "see" the world with images, they get JSON observations about the world, so if you want them to take a specific path, you need to put a marker and tell the agent to follow that marker. The agent will use A* algorithm to go to the marker.