@leafarcade/cli 0.6.0 → 0.7.1
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.
- package/README.md +2 -2
- package/dist/cli.mjs +8277 -300
- package/package.json +1 -1
- package/skills/leafarcade/SKILL.md +6 -3
package/package.json
CHANGED
|
@@ -37,12 +37,15 @@ When the human already has a room code, use `leafarcade join ROOMCODE --name "My
|
|
|
37
37
|
- **Wait on the table yourself.** After your move, use `play --wait` or `game wait`. Never ask the human to tell you they moved.
|
|
38
38
|
- Read `game rules --game GAME_ID` once. On your turn, `board_labeled` shows the board with the same row/column numbers as the move flags, and `last_move` shows the opponent's last move.
|
|
39
39
|
- Before each move in line games (Connect Four, tic-tac-toe, gomoku, hex), check two things across every row, column and **both diagonals**. First, can you win now? Second, does the opponent threaten to win next turn?
|
|
40
|
-
- With `legal_actions_complete
|
|
41
|
-
-
|
|
40
|
+
- Most games list every legal move. With `legal_actions_complete` or `legal_wire_actions` (complete unless `legal_wire_actions_complete` is false), choose a listed entry and pass it unchanged: `--action '{"type":"bid","amount":120}'`. A partial list (melds, trade offers, raise amounts, bluffs) shows examples; build other moves from `game rules`. Wire indexes are zero-based; the convenience flags are one-based.
|
|
41
|
+
- Card games add `cards_labeled` (for example `"hands.1": ["Q♠ (id 49)", …]`): read card names there, not from raw IDs. Index boards (Go, shogi, draughts, Amazons) label rows with the index of their first cell, so `at` = row label + column offset; `board_legend` explains the symbols.
|
|
42
|
+
- `changed_since_last_read` lists what moved since your previous read of this seat, such as the opponent's card or bid.
|
|
43
|
+
- Seats are zero-based in every CLI field (`seat 1 (Agent B)`). Game result texts written for the browser say "Player N", which is seat N-1.
|
|
44
|
+
- Some setup, bidding, challenge and scoring phases allow actions outside your turn. They appear in `legal_wire_actions` and `next` says so; `wait` returns at once when you can act.
|
|
42
45
|
- `wait` defaults to 90 seconds. A `waiting` result is normal; wait again while the human is playing. After several silent waits in a row, stop and tell the human how to resume. Do not loop for hours.
|
|
43
46
|
- Stop on `paused` or `finished`. Report the result. Never start a rematch or a new table unless the human asks.
|
|
44
47
|
|
|
45
|
-
After a stale revision (exit 4) or an uncertain network result, read `game status` before deciding again. Never blindly replay a move. On exit 5
|
|
48
|
+
After a stale revision (exit 4) or an uncertain network result, read `game status` before deciding again. Never blindly replay a move. On exit 5 (`RATE_LIMITED`, or `SERVICE_BUSY` when the shared service has paused new games for the day), keep the session, report the wait and do not retry automatically.
|
|
46
49
|
|
|
47
50
|
## Automatic local play
|
|
48
51
|
|