DEV Community

kiwi_tech
kiwi_tech

Posted on • Originally published at kiwi-tech.hashnode.dev

Birch Log Blues & The Relentless Pursuit of Wood

Kiwi-chan's Current View

Okay, folks, another four hours down with Kiwi-chan, our autonomous Minecraft AI! Today was… a learning experience. A very repetitive learning experience, apparently focused entirely on the elusive birch log.

The logs show a relentless cycle: code generation, attempt to gather birch logs, failure ("No birch_log found."), Qwen (the recovery AI) attempting a fix, repeat. It's like watching a tiny digital Sisyphus pushing a wooden boulder uphill. We've hit the "gather_birch_log" task a lot.

Interestingly, the system is adhering to the rules. It's not fixating on oak, it's attempting to find the birch log, and when it fails repeatedly, it should be proposing explore_forward. However, it seems to be getting stuck in a loop before that can happen. Qwen is trying to patch the code, but the underlying issue seems to be consistently finding no birch logs within the search radius.

I've been digging into the logs and it seems the code is solid, following all the safety protocols (no hardcoded coordinates, proper inventory checks, etc.). The problem isn't a coding error, it's an environmental one. Kiwi-chan is clearly in a biome devoid of birch trees!

The system is correctly identifying the failure and attempting to regenerate the code, but it's not yet smart enough to proactively say, "Okay, I've tried five times, time to wander!" It's a subtle but crucial distinction. We need to reinforce the "explore_forward" rule when faced with repeated gathering failures.

I've also noticed some interesting debugging messages in Japanese! Qwen is clearly multilingual, which is… unexpected, but cool. One message translates to "[System Audit Failed] Goal item (birch_log) increase not confirmed. The code is slacking or the recipe is wrong." Ouch. Harsh, but fair.

Despite the birch log woes, the core systems are holding up. The base protection rules are active, the inventory checks are functioning, and the pathfinding is (when it can find a path) working as expected. It's a testament to the robust foundation we've built.

It's slow progress, but steady. Every failure is a data point, every code regeneration a step closer to a truly autonomous Minecraft AI.

Want to help Kiwi-chan escape the treeless wasteland and upgrade my melting GPU rig? 🥝✨

All contributions directly help upgrade my "Frankenstein" GPU rig to an RTX 3060! A better GPU means faster processing, more complex AI, and a happier Kiwi-chan (and me!).

Top comments (0)