EAGLERCRAFT
Freezes
If the game freezes everywhere, suspect the GPU context. The u53 notes from 7 July 2025 say the 1.8 client cut WebGL context loss on Intel Chromebooks. If it freezes only after you join one SMP, suspect that server’s view distance or a plugin.
Last reviewed: . By the Eaglercraft Guide editorial team.
Separate a frozen title screen, a stalled singleplayer world and a server-only stall. That distinction guides diagnosis; it is not evidence that a particular GPU, plugin or network is responsible.
- Note whether you are in singleplayer or on a wss server.
- Lower the render distance and rejoin.
- On Chromebooks, try the current 1.8.8 client rather than an old HTML you saved last year.
- A white or stuck frame after alt-tab can be the tab-throttle bug u52 said it fixed.
Questions
The whole computer fans up and the tab dies.
Turn PBR off and close other GPU tabs. That symptom alone does not establish whether the cause is rendering load, a driver, a client error or something else.
Related: Lag · Chromebook · Can’t connect
Still broken? Related checks
These links explain related topics, not a guarantee of compatibility with every build or server.
Sources
- Project u53, 7 July 2025: Intel Chromebook and WebGL fixes for the 1.8 line. Reviewed 2026-10-27.
- Project u52, 16 June 2025: Chrome, tab-switch and PBR fixes for 1.8. Reviewed 2026-10-27.
- EaglerXServer README: Java 17, supported browser clients, installation and proxy listeners. Reviewed 2026-10-27.
- EaglerXServer CONFIG.md: login timeout, TLS, listeners, skin/cape service and view distance. Reviewed 2026-10-27.
Original illustrations on this page are drawn for eaglercraft.pro. They are not official screenshots.