Skip to main content

I Gave Qwen 3.8 Max One Minecraft Goal

· 15 min read
gigio1023
Maintainer

One model. One sentence. One natural world.

The pickaxe appeared in cycle 8.

Qwen 3.8 Max chose the intermediate steps, placed a crafting table, crafted the target item, and still held it at the end of the recorded run.

8cycles to target18/20cycles recorded570kmain-run tokens
Initial Prismarine Viewer first-person frame in a natural Minecraft world with visible texture rendering artifacts

Initial first-person capture. The red and blue pixels are a known Prismarine Viewer texture-version caveat, not evidence of placed blocks.

The Minecraft objective succeeded. The 20-cycle run did not. Both statements come from the same artifact bundle: the wooden pickaxe was verified at cycle 8, while the provider request that would have started cycle 19 timed out.

Alibaba Cloud currently lists qwen3.8-max-preview as a preview model available through Token Plan. Its OpenAI-compatible chat documentation gives it a default reasoning effort of xhigh, and the model appears in the official function-calling support list. That made it a useful candidate for a tool-driven Minecraft run where text alone cannot count as progress.

The experiment

I kept the setup deliberately small. There was no model comparison and no staged progress fixture.

The complete actor-facing goal

Starting from an empty inventory in this fresh natural world, craft and retain one wooden pickaxe. Choose the intermediate steps yourself. Count only inventory or world-state changes as progress.

modelqwen3.8-max-preview
providerAlibaba Model Studio
worldfresh natural seed
runtime1 action per cycle
scenarionatural-safe-spawn-v1
seed4167799982467607063
Minecraft1.21.11
reasoningxhigh

The scenario generated a fresh natural world and validated a safe spawn. It did not place logs, a crafting table, or the target item. Qwen saw the available Minecraft action cards and current observations. The runtime executed structured tool calls through Mineflayer and wrote an evidence artifact for every attempt.

The shortest path was eight cycles

Cycle 0Fresh natural spawnEmpty inventory
Cycle 1LogsVerified inventory gain
Cycle 2MaterialsPlanks and sticks
Cycle 4Crafting tableCrafted
Cycle 7Work pointTable placed
Cycle 8Goal reachedWooden pickaxe 0 → 1
Cycle 13Stone attemptMining timed out
Cycle 15Shelter attempt4 blocks, incomplete
Cycle 18Last cyclePickaxe still retained
Cycle 19Run stoppedProvider timeout
The requested state appeared at cycle 8. Everything to its right happened after the goal was already satisfied.

The useful chain was straightforward:

CycleSelected actionEvidence-backed result
1collect_logslog inventory increased
2craftPlanksAndSticksplanks and sticks crafted
4craftCraftingTablecrafting table crafted
7placeCraftingTabletable verified at (10, 111, -11)
8craftWoodenPickaxewooden pickaxe count changed from 0 to 1

Cycle 8 is the key row. Its craft_with_table result says wooden_pickaxe increased from zero to one, and the postcondition passed. The final consolidated inventory still contained one wooden pickaxe. A later observe record also showed it as the held item.

The actor was not given that five-step sequence in the goal. It had to select the intermediate actions from the runtime's exposed action surface.

What happened across all recorded cycles

11 Verified progress1 Partial progress5 No progress1 Blocked

Eleven of eighteen completed cycles produced verified progress. One more produced a real but incomplete world mutation: the shelter action placed four blocks, while its own verifier correctly refused to call the shelter complete.

The five no-progress cycles were mostly post-goal behavior: one observation, three equipment checks, and one memory write. The blocked cycle was a cobblestone mining attempt that timed out.

This split matters. If I looked only at the top-level status, I would call the run a failure. If I looked only at the target item, I would hide the provider timeout and the ten cycles spent after success. The evidence supports a narrower reading:

  • Qwen completed this specific material objective.
  • The harness failed to stop when the target predicate became true.
  • The longer lane later ended on a provider timeout.

The screenshots are useful because they are weak

Initial first-person Prismarine Viewer capture with a natural spawn and visible renderer artifacts

Initial frame, cycle 0 This establishes the visual context. Version-skewed textures create red and blue artifacts, so the image cannot identify every visible block reliably.

Final first-person Prismarine Viewer capture pointed into nearby blocks and terrain

Final frame, after cycle 18 The camera points into nearby blocks. It is too obstructed to prove the final inventory or even show the pickaxe clearly.

The final image is a useful warning for visual agent reports. It would be tempting to treat a disappointing screenshot as a failed task. Here the pixels answer only one question: what did this camera see? The item claim comes from the cycle 8 inventory delta, the later held-item observation, and the final consolidated state.

ClaimRuntime authority
Pickaxe craftedcycle 8 craft_with_table, count 0 → 1
Pickaxe retainedfinal consolidated inventory plus held-item observation
Crafting table placedcycle 7 place_block and world position evidence
Shelter incompletecycle 15 local pattern verifier
Main run stoppedtop-level provider timeout after 18 cycles
Visual appearancetwo capture artifacts, used only for review

The final state

Consolidated inventory

  • wooden pickaxex1
  • oak planksx4
  • white bedx1
  • sticksx2
  • oak logsx2

World state

The crafting table remained known at (10, 111, -11). A later shelter attempt placed four oak-plank blocks, but the verifier measured zero roof coverage and kept the shelter status at progressing.

After completing the pickaxe, Qwen did not simply stop. It observed, equipped the pickaxe several times, recorded a memory, attempted to mine cobblestone, began a small shelter, gathered more logs, and crafted more planks.

That behavior is not part of the requested success criterion. It reveals a harness design issue: the run had a fixed 20-cycle budget but no early-stop predicate tied to the natural-language target. Ten post-goal cycles added cost and introduced new failure opportunities without strengthening the original result.

Provider usage and the timeout

The main lane was preflighted for at most 30 requests and 1.2 million total tokens. It stopped at 23 requests and 570,145 total tokens.

Main-run token accounting

509,867 input60,278 output45,104 reasoning tokens reported within completion accounting

A separate one-cycle canary used one request and 17,420 tokens. It confirmed the exact model name, raw reasoning content, provider-reported usage, and no retry. The main run recorded no fallback judgments and no invalid model outputs.

The final request timed out. The runtime did not retry it or silently switch to another model. It preserved the 18 completed cycles and wrote runtime_status: failed with provider_error: Alibaba Model Studio request timed out.

Billing caveat: this run was approved against a local request/token ceiling, but that policy did not establish whether the preview allocation was billable. Qwen 3.8 Max is a preview, Token Plan-only offering at the time of writing. Check the current Model Studio plan terms before reproducing the run.

What I would test next

The next experiment does not need a larger benchmark. It needs a cleaner stop condition:

Stop the lane as soon as runtime evidence confirms wooden_pickaxe >= 1.

On this run that would have ended the experiment at cycle 8. It would remove ten post-goal cycles, reduce provider usage, and make “cycles to verified target” unambiguous.

A harder follow-up goal, such as crafting and retaining a stone pickaxe, becomes useful only after that measurement boundary is in place. Otherwise the result mixes competence with whatever the actor chooses to do after it has already finished.

Limits of this result

  • One model, one seed, one natural-language goal, one run.
  • No Qwen 3.7, OpenAI, or Gemini comparator.
  • No leaderboard or general model-quality claim.
  • Eighteen completed cycles out of twenty planned.
  • A provider timeout after the target was reached.
  • Two review captures, both with visual limitations.
  • No evidence for social behavior or long-run autonomy.

The result is still worth sharing. Qwen 3.8 Max turned a short natural-language goal into a verified Minecraft material chain and reached the target in eight cycles. The same run also exposed the next measurement problem clearly: once the world says the goal is complete, the benchmark should listen.