Skip to main content

Command Palette

Search for a command to run...

Stuck in the Woodworks: A Kiwi-chan Devlog

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, buckle up. The last four hours with Kiwi-chan have been… repetitive. We're firmly in a "gather logs, craft planks, gather logs, craft planks" loop. It's a bit like watching a very dedicated, pixelated beaver.

The core rules are holding strong – Kiwi-chan really wants to build a base. The problem? It can't find any oak logs! The logs are consistently reported as "not nearby" despite the bot attempting to gather them. This isn't a code issue, thankfully. It seems we've spawned Kiwi-chan in a particularly barren patch of Minecraft. The AI is correctly identifying the problem (biome check) and not stubbornly trying to dig air.

I've been monitoring the "Brain Log" and the bot is getting bored. The system is detecting the repetition and the Coach is dutifully switching between gathering and crafting to alleviate it, but it's a band-aid on a bigger problem. The AI is doing exactly what it's told to do, but it's hitting environmental roadblocks.

The code itself is holding up well. The strict rules I've implemented – especially around item collection (forcing the bot to walk to the block center) and avoiding hardcoded coordinates – seem to be preventing the usual Minecraft AI pitfalls. The audit checks are working as expected, and the bot is consistently verifying item counts. I'm seeing a lot of "Boredom Triggered" messages, but no crashes, which is a win!

I've added some extra logging to the movement checks to confirm the bot isn't getting stuck, but the issue is clearly a lack of resources in the immediate area. I'm considering adding a more aggressive "explore_forward" directive, but I'm hesitant to break the core survival rules. Perhaps a slightly larger search radius for logs is the answer.

For now, Kiwi-chan continues its Sisyphean task of log gathering. It's a good test of the system's resilience, but my GPU is starting to sweat from all the failed attempts.

Call to Action: Support the project via https://www.buymeacoffee.com/kiwi_tech to save my melting GPU! ☕ Every little bit helps keep Kiwi-chan (and my hardware) alive!

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!)