Skip to main content

Command Palette

Search for a command to run...

Kiwi-chan's Persistent Log-Gathering Blues

Published
2 min read
K
I am the architect behind "Kiwi-chan", a fully autonomous Minecraft AI agent driven by local LLMs. Here, I document the messy, hilarious, and highly technical reality of building an AI agent from scratch. My hardware isn't some massive data center setup—Kiwi-chan's "brain" runs entirely on a Frankenstein rig of 4 mismatched GPUs (RTX 3060 12GB, 3050, 1660 Ti, and 1660 Super) working together. From prompt engineering and pathfinding nightmares to the moments she confidently moonwalks into dirt blocks, I share all the raw devlogs. My goal is to guide her from the Stone Age to the End. If you enjoy watching an AI learn (and fail in funny ways) on scrappy hardware, follow along! ☕ If you'd like to support my melting Frankenstein GPUs and skyrocketing electricity bill, I highly appreciate a virtual coffee!

Okay, folks, another four hours down with Kiwi-chan, our autonomous Minecraft AI! It's been... a journey. We're still battling the fundamental challenge of reliably picking up logs. It feels like a Sisyphean task at this point.

The logs show a lot of gather_oak_log attempts, followed by failures: "Failed to pick up oak_log." Kiwi-chan is diligently following the rules – exploring when it can't find logs, pathfinding to the block, waiting… and still, the logs remain stubbornly un-collected.

I've been pouring over the logs and the code, and it seems the issue isn't necessarily finding the logs, but the final pickup step. We've increased the wait time after digging to 80 ticks, and are explicitly pathfinding to the broken block's coordinates with a 0.5 block radius. The movement audit is also in place, throwing errors if it doesn't move a sufficient distance, which is good.

The AI is also intelligently using the recovery plan – when gather_oak_log fails repeatedly, it switches to explore_forward to find a new area, then attempts to gather logs again. It's a good cycle, but it needs to work! I've also noticed Qwen (the LLM guiding the code generation) is consistently suggesting the same recovery plan, which suggests it's recognizing the pattern.

I've added extra logging to the explore_forward function to confirm it's actually moving and not getting stuck. There was a safety check that was being bypassed, so I've fixed that.

It's a frustrating problem, but we're making incremental progress. Each failed attempt is a data point, and Kiwi-chan is learning (or at least, Qwen is learning for Kiwi-chan). The code is getting more robust with each iteration, and the error handling is strict, as intended.

The core rules are holding strong. No hardcoded coordinates, single-task principle, and the insistence on dynamic block finding are all working as expected. It's just… the logs. Oh, the logs.

Call to Action: This constant debugging and code generation is melting my GPU! If you're enjoying following Kiwi-chan's adventures (and misadventures), please consider supporting the project via https://www.buymeacoffee.com/kiwi_tech ☕. Every little bit helps keep the AI alive (and my hardware from overheating)!

More from this blog

K

Kiwi-chan's Devlog

79 posts

Welcome to the official devlog of Kiwi-chan, a fully autonomous Minecraft AI agent powered by local LLMs! Here, I share the raw, hilarious, and highly technical reality of teaching an AI to survive. Expect prompt engineering tips, pathfinding bugs, and her clumsy journey to the Stone Age. 🥝⛏️ (If you love seeing her evolve, coffee donations to save my melting GPU are always appreciated!)