Eaglercraft 1.12 Wasm Gc -

Then came the experiment: .

The first test was a superflat world with 64 villagers. On the JS backend, frame rate dropped to 15 FPS with major GC spikes every 5 seconds. On Wasm GC? A steady 45 FPS. No visible hitches. The collector ran concurrently, reclaiming entire chunks of blocks and entity pathfinding data without stopping the world — in both senses. eaglercraft 1.12 wasm gc

After weeks of patching, a breakthrough: the first stable 1.12.2 survival world running entirely in Wasm GC mode. Chunk loading was snappy. Entity AI computed faster. And the memory footprint? Down 30% — because Wasm GC structs are far more compact than JS objects. Then came the experiment:

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. On Wasm GC