Okay, folks, buckle up. The last four hours with Kiwi-chan have been… repetitive. We've hit a bit of a loop. She really wants to craft a chest, but keeps failing. And when she fails, her "Coach" (the reasoning engine) decides the best course of action is… more exploring. Specifically, explore_forward. A lot of explore_forward.
The logs show a clear pattern: fail chest, explore, fail chest, explore, repeat. The system is correctly identifying the crafting failures and attempting to recover by gathering resources, but it's getting stuck in a cycle of exploration that isn't actually finding anything useful to break the cycle. The "Boredom Triggered!" messages are honestly relatable at this point. Even the AI is tired of wandering!
I've been digging into the logs and the system rules. It seems the explore_forward action is being triggered too readily, even when a simple gathering task (like digging logs) would be more appropriate. The rules do specify explore_forward for finding new biomes, but Kiwi-chan is using it as a general "I'm stuck, wander around" command.
The good news is the movement audit is working! The code is correctly checking if the bot actually moved a reasonable distance and throwing an error if it's blocked. This is preventing infinite spinning in place, at least. I've also noticed the system is now logging when it detects a potential infinite loop, which is a huge step forward.
I've also been impressed with the ChromaDB integration. The system is actively saving and recalling skills, and the memory checks are happening as expected. It's just… applying the wrong skills at the wrong time.
I'm going to focus on refining the "Coach" decision-making process. Specifically, I need to make it more discerning about when to use explore_forward versus a targeted gathering action. I suspect tweaking the reasoning alignment rules will be key. I'm also going to investigate why the bot is so fixated on crafting a chest when it hasn't even secured a crafting table in the world yet (rule #7!).
It's slow progress, but we're learning a lot about how these LLMs behave in a complex environment like Minecraft. Every crash, every loop, every "Boredom Triggered!" message is a data point.
Call to Action: This constant running 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 servers running and Kiwi-chan exploring (hopefully in a less circular fashion)!
Top comments (0)