Minecraft clone 'vibecoded' with a local Qwen 27B — then 4 mechanics that probably aren't in the training data

On August 30, r/LocalLLaMA user u/liright posted a 133-second video of a Minecraft clone that, by his account, was fully "vibecoded" with a locally run Qwen3.8-27B quantized to Q4 — specifically the Q4_K_S build from Unsloth. The thread drew roughly 1,500 upvotes and more than 240 comments, and its title carried the rebuttal in advance: because skeptics called the clone unimpressive, since Minecraft is heavily represented in the model's training data, the poster had the model add four things that are probably not.

What the Video Shows

The game runs in the browser on three.js: procedural terrain, block building and breaking, an inventory, survival vitals and creatures, with sound generated at runtime. The poster says the model's total runtime was seven to eight hours spread over three days of sessions. To answer the training-data objection, he asked the model to bolt on four mechanics unlikely to appear in any corpus of Minecraft code:

• Skateboard: ride it, ollie, mid-air tricks, break it back into your hand
• MLRS truck: climb into the cockpit for a top-down view and fire a 12-rocket salvo
• FPV drone: betaflight-style cockpit OSD with attitude, altitude and throttle readouts
• In-game computer: a little desktop OS running two mini-apps

The drone is the tell: the poster is a drone pilot, and said he "tweaked the controls quite a bit, it's basically acro mode with stabilized yaw."

The Training-Data Debate

The rebuttal did not end the argument. "But all that IS in the training data," replied u/mister2d. "I'll wait for the Minecraftest, thanks," wrote u/yoburg. "It cannot do things it was not trained on," another added. Others noted the demo is a video, not shipped code — one commenter quipped about the 286K-line "god file" and the separate sounds.js — and no reproducibility claim was made. A GitHub mirror of the game, qwen27craft, appeared the next day and confirmed the four extras. The objection cuts both ways: reconstructing a well-known game from memorized patterns is not the same as understanding, yet a Q4 27B holding a coherent codebase across enough turns to bolt new mechanics onto its own earlier code remains the notable part.

What It Means for Vibecoding

The thread lands in the middle of the vibecoding debate, the same week OpenAI cut off Cursor and Amodei predicted 90 percent of code would be machine-written. It is the same model at the center of last week's 100K-context benchmark thread. A playable browser game produced with a local quant is a long way from "it cannot do things it was not trained on." It is also not evidence of understanding. What would settle the argument: published code and prompts, and someone reproducing the loop on commodity hardware.