mayatnikovandClaude Opus 4.7
d960db4819
Closes a structural gap: the bot now actually REMEMBERS what it
discovered and what it tried. Two stores live under state/<host>/ and
are wired in automatically.
runtime/world-journal.js
- Append-only JSONL of discovered points (chopped, placed, base,
shelter, farm, dead_end). Indexed by 16-block spatial grid; O(neighbors)
nearest() lookups; 6 h age prune; 10k line ceiling with trim.
- leanestQuadrant({x,z}) reports the quadrant the bot has the FEWEST
markers in — used by explore.far to circle rather than retread.
- summary() exposed for the stuck-incident proposal body.
runtime/scenario-memory.js
- Sliding window of (skillId, situationHash, code, ok, detail) tuples.
- situationHash() is a coarse fingerprint (16x8x16 cell + day/night +
food/hp bucket + inv key set + closest hostile). So "same kind of
place + same kind of state" matches.
- shouldSkip({skillId, situation}) → true after ≥3 failures within 30
min UNLESS a more-recent success in the same situation un-locks it.
- recentTailFor() exposed for the stuck-incident body.
Wiring (runtime/bot.js):
- dispatchAction captures situationHash BEFORE the action runs and
records (skillId, situation, code, ok) after — failures are attributed
to the dispatch-time state, not the partial-effect state.
- worldDelta fields (choppedAt, minedAt, placedAt, baseAt, shelterAt,
plantedAt, harvestedAt, tilledAt) auto-flow into the journal.
- no_target + silent_dig_failure also write dead_end markers.
Scheduler / skills now consume memory:
- reflex.js curriculum reflex calls memory.shouldSkip — if the same
(skill, situation) failed 3+ times recently, auto-converts to a
wander hint so the bot leaves and tries elsewhere.
- explore.far calls journal.leanestQuadrant when multiple cardinal
directions are walkable and prefers the less-explored one.
- gather.logs walks to the nearest known "chopped" bucket within 96
blocks before falling through to findBlock — chunks with confirmed
trees are more likely to yield another.
stuck-incident body now includes journal byKind + last 12 scenario
entries so Pi can write a structural fix, not just a guard clause.
Architecturally: this is the foundation for "bot rewrites itself".
The proposals Pi now receives carry real signal about what was tried
and what's around, instead of a single snapshot in isolation.
10 new tests (world-journal × 5, scenario-memory × 5). npm test 134/134.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
50 lines
1.7 KiB
JSON
50 lines
1.7 KiB
JSON
{
|
|
"name": "pepa-pi-bot",
|
|
"version": "0.0.1",
|
|
"private": true,
|
|
"description": "An autonomous, self-extending Minecraft player powered by Pi and Mineflayer.",
|
|
"license": "MIT",
|
|
"type": "module",
|
|
"engines": {
|
|
"node": ">=20"
|
|
},
|
|
"scripts": {
|
|
"agent": "pi",
|
|
"agent:resume": "pi -c",
|
|
"bot": "node runtime/supervisor.js",
|
|
"bot:bare": "node runtime/bot.js",
|
|
"tui": "tsx tui/tui.tsx",
|
|
"propose:apply": "node scripts/propose-apply.js",
|
|
"stop": "bash scripts/stop.sh",
|
|
"test": "node --test runtime/skills/contract.test.js runtime/skills/groups.test.js runtime/skills/compat.test.js runtime/curriculum.test.js runtime/social/social.test.js runtime/stuck-incident.test.js runtime/compat.test.js runtime/reflex.test.js runtime/base-site.test.js runtime/locations.test.js runtime/watch-filter.test.js runtime/world-journal.test.js runtime/scenario-memory.test.js scripts/edit-scope.test.js"
|
|
},
|
|
"dependencies": {
|
|
"dotenv": "^16.4.5",
|
|
"ink": "^7.0.4",
|
|
"ink-text-input": "^6.0.0",
|
|
"minecraft-data": "^3.110.2",
|
|
"mineflayer": "^4.37.1",
|
|
"mineflayer-armor-manager": "^2.0.1",
|
|
"mineflayer-auto-eat": "^5.0.3",
|
|
"mineflayer-collectblock": "^1.6.0",
|
|
"mineflayer-pathfinder": "^2.4.5",
|
|
"mineflayer-pvp": "^1.3.2",
|
|
"mineflayer-tool": "^1.2.0",
|
|
"prismarine-item": "^1.18.0",
|
|
"react": "^19.2.6",
|
|
"vec3": "^0.2.0"
|
|
},
|
|
"repository": {
|
|
"type": "git",
|
|
"url": "git+https://github.com/xmatic-squad/pepa-pi-bot.git"
|
|
},
|
|
"bugs": {
|
|
"url": "https://github.com/xmatic-squad/pepa-pi-bot/issues"
|
|
},
|
|
"homepage": "https://github.com/xmatic-squad/pepa-pi-bot#readme",
|
|
"devDependencies": {
|
|
"@types/react": "^19.2.15",
|
|
"tsx": "^4.22.3"
|
|
}
|
|
}
|