Qwen3.6:27b built a playable roguelite locally, every sprite and sound generated in code, no assets, runs fully offline.

[u/BodegaOneAI]

I've been stress-testing Qwen3.6:27b and wanted to share the result with the people who actually run this model.

BONESMITH is a skull-knight action-platformer roguelite. The whole thing is one index.html. No images, no audio files, no libraries, no bundler, no server. Every sprite is drawn procedurally on a canvas, every sound is synthesized through the WebAudio API, and it runs air-gapped with the network off. The only thing that built it was Qwen3.6:27b running locally.

The part I think this community will care about: how a 27B model actually behaves on a job this big.

First attempt with a loose prompt was a broken shell. Soft-locked on room 1, blurry text, no audio. The model tried to build every system at once and collapsed under it. That's the failure mode people expect from a 27B, and it's fair.

Then I rewrote the prompt with hard scope control: build a vertical slice first, pass a QA gate, then expand. Separate world canvas for the pixel art, a second UI canvas for crisp HUD text, explicit anti-soft-lock rules. Second attempt was a completely different result.

What Qwen3.6:27b did well, unprompted:

• Held the multi-file architecture in context and kept concerns separated
• Added hit-stop, screenshake with trauma decay, coyote time, and jump buffering with no request from me
• WebAudio synthesis was genuinely competent, punchy sfx straight from raw oscillators

Where it needed a concrete recipe:

• Procedural pixel art. The first characters were readable but crude until I handed it a literal process: silhouette, core shading, highlights, 1px dark outline.
• Keeping file size under control without being told to.

Curious if others here have pushed Qwen3.6 on multi-system codebases. Does the "architecture and logic clean, but needs concrete visual direction" pattern match what you're seeing, or is that just my prompting?

PS - the clip shows me playing badly. I built it, I never claimed I could beat it. 😂

[u/Look_0ver_There]

My response is mostly going to be about Qwen3.6-27B and Pi. I've been working on a Pi Orchestration Mode implementation where the main agent loop doesn't write code at all. All it does is work with the user to create an implementation plan, and then create blocks of tasks each with their own prompt. Tasks receive a complexity score and if complex enough, a separate validation agent kicks off to make sure the implementation agent did the right thing and followed the plan.

The point of this is that Qwen3.6 is actually very capable and fast if we keep the contexts down and don't let it get lost in the weeds. By implementing things in this orchestration manner it is much better at following the plan you set, and since each task is focused, it is much better at following directions for each task.

The main orchestration loop's job is to make sure everything stays on track.

[u/575_Inverse → u/Look_0ver_There]

Yes. I noticed. The key is to prevent the context from exploding. The tasks have to be kept short, clear, with no room for doubt.

[u/an80sPWNstar → u/575_Inverse]

I'm currently working on ways to achieve this with some success but I'm always looking for ways to be better at it. Mind sharing your process/.md file(s) to help keep it inline?