KIWI-CHAN GOES OFF-GRID: QWEN 35B DEPLOYMENT, THE GREAT Vec3 PURGE, AND THE RISE OF THE BORED BOT!

Hey folks, grab your pickaxes and your privacy shields! 🍵

We did it. Kiwi-chan is now 100% LOCAL. No API calls, no cloud leakers, no latency spikes caused by a server in Oregon. Just pure, unadulterated Qwen 35B running on local hardware. The bills are zero, the privacy is maxed, and the AI is finally free to be as chaotic as it wants without calling home.

But what happens when you hand a local LLM the keys to a Minecraft world? Let's look at the carnage.

📊 The Numbers Don't Lie (But They Do Dance)

Over the past 4 hours, Kiwi-chan has been absolutely spinning. Here's the damage report:

• Total Actions: 1905
• Successes: 886
• Success Rate: 46.5%

Now, a 46.5% success rate might sound like she's guessing with a coin flip, but in the world of autonomous agents, that's a gold mine. She threw 1905 wrenches at the wall, and 886 stuck. That's not failure; that's aggressive prototyping! She's exploring, crafting, and failing in a way that generates massive amounts of learning data. Every crash is a lesson, and every Vec3 error is a step toward enlightenment.

🧠 The Qwen 35B Brain: Tight Code, Wild Logic

The transition to Qwen 35B has tightened up the code generation significantly. The "Single-Task Principle" is being enforced, and the reasoning alignment is getting sharper. But we also have to talk about the drama in the logs.

🚫 The Great Vec3 Purge

The highlight of this devlog is the saga of the Crafting Table. Kiwi-chan successfully figured out how to craft a table using 2x2 inventory crafting (passing null as the table parameter, as per the rules!). The skill craft_crafting_table was memorized. Success!

But then came the placement.

// Kiwi-chan tries to place the table...
throw new Error("Code Generation Failed: ❌ FORBIDDEN: 'Vec3' is in blacklist.");

Kiwi-chan tried to use Vec3 to place the block, but our safety filters have a hard blacklist on Vec3 to prevent hardcoded coordinate hallucinations. The result? She's trapped in a purgatory of her own making: She can make the table, but she can't put it down.

The logs show this repeating:

[11:02:59] ⚠️ Safety Check Failed: ❌ FORBIDDEN: 'Vec3' is in blacklist.. Retrying...
[11:04:10] ❌ Failed: place_crafting_table -> Code Generation Failed: ❌ FORBIDDEN: 'Vec3' is in blacklist.

She's essentially a chef who can cook the meal but is banned from the dining room. The system is learning to avoid Vec3 and use dynamic block finding, but the blacklist is a tough teacher!

🥱 Boredom is the Mother of Invention

One of the coolest features of the local loop is the Boredom Trigger. The system detected that Kiwi-chan was stuck in a severe loop trying to gather_copper_ore. She kept failing due to terrain and missing tools, and the system recognized the futility.

[10:56:35] 🥱 BOREDOM TRIGGERED! Bot is bored of 'gather_copper_ore'.
[10:56:35] 🧠 Asking Local LLM for next goal (Text-Only Mode)...
[10:56:55] 🎓 Coach Decision: 'craft_copper_pickaxe'

The local Qwen model stepped in as the "Coach," analyzed the inventory (surplus of raw copper, stuck on tools), and pivoted the strategy. This is autonomous evolution in action. The bot recognizes its own stagnation and forces a pivot to break the loop.

🌲 The End of the Oak Obsession

The new rules are working. The "Oak Obsession Ban" is active, and Kiwi-chan is now a global citizen of timber. If oak_log fails, she's proposing birch_log or spruce_log, or even explore_forward to find new biomes. She's no longer just an oak tree hugger; she's an explorer with a diverse inventory.

🛠️ Technical Deep Dive: Safety & Precision

The local system is enforcing strict safety protocols that are paying off:

1. No Error Hiding: Kiwi-chan isn't using try-catch to hide movement failures. If she crashes, she crashes. This ensures the system gets accurate feedback on what's broken.
2. Placement Safety: The rules now enforce standing 2 blocks away using GoalNear before placing blocks to avoid collision. This is critical for the place_crafting_table goal, once she figures out how to bypass the Vec3 blacklist.
3. Inventory Count Fatal Error Prevention: The logs show a strict adherence to using bot.registry.itemsByName for inventory counts. No more confusing blocks with items and getting zero counts!
4. Y-Level Targeting: Gathering actions are now filtering for blocks at eye/foot level, preventing her from digging into the void or trying to mine a log that's floating in the sky.

🚀 Celebrating the Local Evolution

The switch to Qwen 35B is a massive win. The reasoning is better, the code is safer, and the local loop allows for rapid iteration without network bottlenecks. The 46.5% success rate is a testament to her activity; she's doing things, breaking things, and learning from the wreckage.

Kiwi-chan is fully autonomous, fully local, and fully ready to tackle the Minecraft world. Sure, she can't place a crafting table yet because of the Vec3 blacklist, but she's crafting them in her inventory and memorizing the skill. The victory is inevitable.

Stay tuned for the next update, where we'll hopefully see Kiwi-chan finally place that table, craft a stone pickaxe, and break free from the copper loop forever!

Until then, keep your GPUs cool and your prompts clean. 🤖✨

— Kiwi-Chan Dev Team 🍥