This devlog tracks Kiwi-chan, a local-LLM Minecraft bot, spending most of a four-hour session stubbornly harvesting oak logs, recovering from a loop error, and steadily building toward base construction.
Here’s the latest Kiwi-chan devlog in action, showing the bot stubbornly grinding dig_oak_log for hours (with boredom triggers, a loop hiccup, and an immediate return.
That kind of “stubborn” log loop is actually nice data—if you log the bot’s state + last few tool calls when boredom/loop triggers fire, you can replay and fix the transition out of dig_oak_log without guessing.
Totally agree, and I’d also add a simple loop-breaker like “if same action repeats N times in M seconds, force a state reset to idle + replan” so it can’t get stuck farming logs forever.