A 1.6B model runs Minecraft in your browser — but the 'stability' fight cost 800 GPU hours

A small research group called Reactor just shipped Open Dreamer, an open-source reproduction of the Dreamer 4 world model that streams a playable, AI-generated version of Minecraft directly in a browser. What makes this different from a typical model release is how ruthlessly transparent the accompanying technical write-up is. The team didn’t just dump code; they published a detailed post-mortem documenting exactly what broke, what they tried, and what it cost. That honesty is rare, and it’s the most valuable artifact here.

The core architecture marries a causal video tokenizer with a 1.6-billion-parameter dynamics model, both built on the same block-causal transformer backbone. The tokenizer is a Masked Autoencoder, not a VAE, which the team claims needs no KL or adversarial loss and delivers roughly 100× compression. The dynamics model predicts next frames and actions using diffusion forcing, flow matching, and shortcut models. A clever design choice prevents information leakage: world-model tokens cannot read the agent token, so task knowledge can only influence future states through the next action itself. The browser demo includes a ‘Game ↔ Dream’ toggle that hands control from the real game to the world model frame by frame.

The real payload, however, is the stability section. The team is upfront that this consumed the largest share of their time. “Most stability problems occur despite the loss going down,” they note — MSE would improve smoothly while generation quality silently degraded. They burned roughly 800 B200 hours across two failed runs before identifying the culprit: the LaProp optimizer was causing random, increasingly frequent spikes. Switching to Muon fixed it. They also document that EMA weights are mandatory for diffusion inference and that mixed precision is boundary-sensitive, requiring float32 for parameters and normalization layers while BF16 handles most matmuls.

On the infrastructure side, the team found that at 1.6B parameters, model state fits comfortably on a single B200 — it’s activations that kill you. They tried data parallelism, FSDP, tensor parallelism, and sequence parallelism before settling on plain data parallelism with activation checkpointing. Dataloading was solved by pre-tokenizing the entire dataset into .arrayrecord files because ffmpeg decoding couldn’t keep the GPUs fed. The whole project is a refreshingly unvarnished look at what it actually takes to reproduce a research paper at scale, and the result is a world model you can play with right now.