Eaglercraft 112 - Wasm Gc

Eaglercraft 1.12 uses a with a WASM GC backend:

Warning: The WASM GC backend is still marked "experimental." Some rendering features (like translucent blocks) have minor graphical glitches compared to the JS version. eaglercraft 112 wasm gc

For an action game requiring 60 frames per second, these stutters are lethal. This is why early Eaglercraft versions capped out at 1.8. The Java Stop-The-World GC translated poorly into JavaScript. Eaglercraft 1

| Aspect | Without WASM GC | With WASM GC (Eaglercraft 1.12) | |--------|----------------|--------------------------------| | Memory usage | High (JS heap + WASM linear memory) | Lower (unified browser GC) | | GC pauses | Frequent, long | Browser-optimized, shorter | | Mod compatibility | Low (no reflection/GC interop) | Higher (supports more Java patterns) | | Binary size | Large (includes GC runtime) | Smaller (uses browser’s GC) | | FPS in 1.12 | 10–30 | 30–60+ (on modern machines) | The Java Stop-The-World GC translated poorly into JavaScript