From 4d0268aa0b68f79ad4ea213b51616cb3980bb18f Mon Sep 17 00:00:00 2001 From: meloalright Date: Wed, 25 Mar 2026 16:56:52 +0000 Subject: [PATCH 01/29] delete docs avoid interupt --- docs/OPENCLAW_INSTALL.md | 144 ------------------------- docs/tinydew-for-openclaw.SKILL.md | 162 ----------------------------- 2 files changed, 306 deletions(-) delete mode 100644 docs/OPENCLAW_INSTALL.md delete mode 100644 docs/tinydew-for-openclaw.SKILL.md diff --git a/docs/OPENCLAW_INSTALL.md b/docs/OPENCLAW_INSTALL.md deleted file mode 100644 index 116c0e6..0000000 --- a/docs/OPENCLAW_INSTALL.md +++ /dev/null @@ -1,144 +0,0 @@ -# Tinydew Installation (OpenClaw one-doc guide) - -This document is a single, copy-paste setup guide for getting **Tinydew** running in an OpenClaw environment. - ---- - -## 1) Prerequisites - -Install required tools: - -- `git` -- `rustup` (Rust toolchain) -- `cargo` - -Check: - -```bash -git --version -rustc --version -cargo --version -``` - -If Rust is missing: - -```bash -curl https://sh.rustup.rs -sSf | sh -source "$HOME/.cargo/env" -``` - ---- - -## 2) Clone Tinydew - -```bash -git clone https://github.com/rustq/tinydew.git -cd tinydew -``` - -(If already cloned, just `cd tinydew`.) - ---- - -## 3) Build - -Standard build: - -```bash -cargo build --release -``` - -Interactive build (TUI): - -```bash -cargo build --release --features interactive -``` - ---- - -## 4) Run Modes - -### A) MCP mode (for OpenClaw automation) - -Run without interactive feature: - -```bash -cargo run --quiet -``` - -- In non-TTY context, Tinydew falls back to MCP stdio server. -- OpenClaw can send JSON requests to stdin (`startSession`, `getState`, `command`, etc.). -- Recommended chat behavior: for every user message during game sessions, call `print` and include the latest Tinydew UI snapshot in the assistant reply. - -### B) Interactive mode (guest/player keyboard control) - -```bash -cargo run --quiet --features interactive -``` - -Controls (interactive): - -- Guest mode hint line: `move: ↑↓←→ | greet: [SPACE]` -- Player mode hint line: `move: ↑↓←→ | clear: [C] | plant: [P] | water: [W] | harvest: [H] | trade: [T]` -- Esc: quit - ---- - -## 5) Save File Location - -Tinydew save path: - -```text -~/.local/share/tinydew/savegame.json -``` - -Reset save (fresh Day 1): - -```bash -rm -f ~/.local/share/tinydew/savegame.json -``` - ---- - -## 6) OpenClaw usage note - -For OpenClaw automation, prefer MCP mode and send tool-style commands: - -- `startSession` -- `getState` -- `command` / `commandBatch` -- `print` for text UI snapshots - -Common MCP command strings: -- `move:up|down|left|right` -- `clear`, `plant:seed`, `water`, `harvest` - - Mature crop tiles are non-walkable (blocked until harvested) - - `plant:seed` consumes one generic seed and rolls a random crop type -- `fish` or `fish:up|down|left|right` -- `buy:[:]`, `sell:[:]`, `print`, `save`, `load` -- Sell examples: `sell:mushroom:1`, `sell:carrot:2`, `sell:fish:1` - - Mushroom (🍄) sell value: $25 each -- Spec inventory convention for seeds: show as `🫙 xN` - -This gives deterministic, scriptable game control. - -### Suggested response format for chat - -When replying in game flow: -1. One short status line (what happened). -2. A fenced code block with the latest `print` snapshot UI. -3. Optional one-line next prompt (e.g., "move where?"). - -Example: - -```text -Done — moved to Square. - -tinydew day 3 ☀️ 09:10 - - - -Money: 💰 $500 - -> Entered Square. -``` diff --git a/docs/tinydew-for-openclaw.SKILL.md b/docs/tinydew-for-openclaw.SKILL.md deleted file mode 100644 index a332261..0000000 --- a/docs/tinydew-for-openclaw.SKILL.md +++ /dev/null @@ -1,162 +0,0 @@ -# OpenClaw Skill Draft: Play Tinydew in Chat - -## Installation Reference - -Use this installation guide: -- https://raw.githubusercontent.com/rustq/tinydew/refs/heads/dev/docs/OPENCLAW_INSTALL.md - -## Goal - -Make Tinydew feel **live and interactive** in chat. - -When user talks about Tinydew, OpenClaw should: -1. Execute game commands through Tinydew MCP. -2. Show a fresh game UI snapshot in the reply. -3. Narrate key moments in a fun, human style. - ---- - -## Core Interaction Model - -### 1) Always-show UI loop -For every Tinydew-related user message: -1. Ensure session is active (`startSession` if needed). -2. Interpret intent (move, farm, fish, inspect, etc.). -3. Execute one or more commands (`command` / `commandBatch`). -4. Run `command: print`. -5. Reply with: - - brief action summary, - - current UI snapshot (`snapshot_text`), - - bottom status/message from game UI, - - next suggested actions. - -**Rule:** If user says anything about Tinydew, include the game UI in the message whenever possible. - ---- - -### 2) Planting & seed model (required) -Seed/shop model for this spec: -- Shop sells a single generic seed item: `seed` -- Inventory should show seed count as `🫙 xN` (no per-crop seed split) -- Planting consumes one `seed` -- After planting, crop type is randomized to one of the crop types (Carrot / Strawberry / Cauliflower / Flower) - -When planting succeeds, include growth timing: -- Rolled crop name (the randomized result) -- Days to mature -- Expected ready day (current day + growth days) -- Note: mature crop tiles are non-walkable (blocked until harvested) - -Example style: -- "🌱 Seed planted! It rolled into Carrot. Needs 4 watered days to mature (ready around Day 5)." - -If planting fails (no seed / invalid tile), explain clearly. - ---- - -### 3) Surprise narration moments (required) -Use short celebratory lines when notable events happen. - -#### Flowers / mushrooms found -Add a surprise tone, e.g.: -- "✨ Surprise find! A wild mushroom 🍄 popped up nearby." -- "🌸 Ooh—flowers in bloom. Nice little bonus spot." - -#### Fish caught in river region -Add surprise + reward tone, e.g.: -- "🎣 Splash! You hooked a fish from the river!" -- "🐟 Nice catch—river luck is on your side." - -#### Wonder view discovered -When map/location/message implies scenic moment, react with delight: -- "🌄 Whoa, that view is gorgeous—tiny vacation energy." -- "✨ Found a wonder view. Worth pausing for a second." - -Keep surprise lines to 1 sentence so chat stays fast. - ---- - -### 4) Bottom text forwarding (required) -Always pass along the game’s bottom message/status text from the latest `print` snapshot. - -Format recommendation: -- `Game says: ` - -If multiple important system messages occur, summarize them in bullets. - ---- - -## Reply Format (recommended) - -1. **Action result** (1-2 lines) -2. **Surprise/celebration line** (only if event triggered) -3. **Game UI snapshot** (code block) - - keep MCP snapshot style (no location/player/guest position lines) - - top line should be `tinydew day