xmatic/pepa-pi-bot
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

fix(v0.3.1): sated bot stops chasing food + perf-leak + fuzzy improvement dedup

Browse Source 
Third day of "bot just walks back and forth burning tokens". Root
causes were mechanical, not the manifesto:

1. SATED BOT CHASING FOOD (the big one)
   Bot had food=17 (nearly full) but storyline first_food + manifesto
   L1 required 2+ food ITEMS in inventory, so it looped scout-food /
   acquire-food for hours instead of working. Now both treat a hunger
   bar >= 14 (SATED_FOOD) as satisfied even with empty food inventory —
   a full bot chops wood / makes tools and grabs food opportunistically,
   only hard-pursuing food when actually hungry (< 14).
   manifesto/needs.js foodDetect + goal/storyline.js first_food.completed.

2. perf_hooks MEMORY LEAK (overnight OOM suspect)
   "MaxPerformanceEntryBufferExceededWarning: 1,000,001 measure entries".
   mineflayer/pathfinder emit perf marks we never consume. Added a
   60s reaper in bot.js (performance.clearMeasures/clearMarks). unref'd.

3. IMPROVEMENT QUEUE SELF-DUPLICATING
   The LLM re-filed closed gaps with reworded titles (#5/#8/#9 were
   dupes of implemented #1/#2/#3). Exact-title dedup missed them.
   Replaced with token-set fuzzy match (isDuplicateTitle): jaccard>=0.75
   OR >=3 shared meaningful tokens with jaccard>=0.5. Also: a re-filed
   gap that's already implemented/rejected is NOT resurrected as a new
   open row. Cleared all 5 open requests (now genuinely implemented).

Also confirmed (no change needed):
- canDig=true is a DELIBERATE codebase-wide choice ("without it the bot
  gets permanently stuck", actions.js). The stale memory recommending
  canDig=false is updated. ViaBackwards dig works partially (dug:1
  moved:1.8 observed); false would trap the bot in every pit.
- scout-food already has blind/tunnel fallback + 12s step timeout
  (operator's earlier edits) so trapped-pathfinder degrades instead of
  hanging 30s.

Tests: 407 green (was 404). Updated needs/state/storyline tests for the
SATED_FOOD threshold; added fuzzy-dedup + tokenize/jaccard tests.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
mayatnikov
2026-05-28 09:34:42 +03:00
co-authored by Claude Opus 4.7
parent 1cf60f81e9
commit 502d7ebae4
7 changed files with 153 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
runtime/manifesto/needs.js
+10 -1
View File
@@ -122,9 +122,18 @@ function alivePursue(s) {
return null;
}
// SATED_FOOD — above this hunger level the bot is NOT hungry; chasing
// food (scout/acquire) is wasted motion. The bot should keep working
// toward wood/tools/shelter and pick up food opportunistically. It
// only becomes a hard need again when the bar drops below this.
const SATED_FOOD = 14;
function foodDetect(s) {
if (!s?.connected) return true;
if ((s.food ?? 20) >= 18 && countAny(s.inventory, FOOD_ITEMS) >= 1) return true;
// Comfortable hunger bar → treat L1 as satisfied even with an empty
// food inventory. (Was: required 6+ food items, which made a sated
// bot loop scout/acquire-food for hours doing nothing else.)
if ((s.food ?? 20) >= SATED_FOOD) return true;
return countAny(s.inventory, FOOD_ITEMS) >= 6;
}