That night, the code was pushed to a public branch. Within days, players were running modded 1.12 worlds on school Chromebooks, fighting the Ender Dragon with zero lag spikes.
Here’s an informative story about and its experimental Wasm GC backend. In a dimly lit server room, a developer named Alex stared at a browser tab. Running Minecraft 1.12.2 — complete with Forge mods, redstone contraptions, and shaders — inside a vanilla browser. No plugins. No native code. Just JavaScript and WebAssembly. eaglercraft 1.12 wasm gc
Alex recompiled the 1.12 client using a custom TeaVM fork targeting Wasm GC. Instead of outputting JavaScript heap management, every object allocation, every new BlockPos() , every HashMap of entities — all became Wasm GC structs and arrays, traced and collected by the browser’s optimized garbage collector. That night, the code was pushed to a public branch
Eaglercraft had already pulled off the impossible: a full Java-to-JavaScript recompilation of the Minecraft client using TeaVM, plus a custom WebSocket-based multiplayer protocol. It ran in any modern browser, no installation needed. But version 1.12 was a beast — over 8 million lines of Minecraft code, plus the labyrinthine complexity of the 1.12.2 engine. Performance stuttered. Garbage collection froze the screen mid-PvP. In a dimly lit server room, a developer