Numerous public servers support version 1.20.2. Use a server list (search “Eaglercraft 1.20.2 server list”) to find:
Example server format: wss://example.com:8080 (note: Eaglercraft uses wss:// for secure WebSockets, not tcp://). eaglercraft 1.20.2
For multiplayer, Eaglercraft implements the Minecraft protocol (version 763 for 1.20.2) over WebSockets instead of raw TCP. A relay server translates WebSocket frames to native TCP packets to communicate with standard Java Edition servers. Alternatively, dedicated Eaglercraft servers run a lightweight Java backend that natively understands WebSocket connections. Numerous public servers support version 1
Latency comparison:
| Connection type | Average ping (US-West) |
|----------------|------------------------|
| Native Java Edition | 35 ms |
| Eaglercraft (WebSocket → TCP relay) | 52 ms |
| Eaglercraft (dedicated WS server) | 41 ms | Example server format: wss://example
For years, Minecraft has required a powerful PC or a dedicated console to run the latest updates. However, the phenomenon known as Eaglercraft changed the game entirely by bringing the blocky universe to the web browser.
With the community constantly pushing boundaries, the arrival of Eaglercraft 1.20.2 is a significant milestone. This version brings the "Trails & Tales" update features to the browser-based world, allowing players to experience cherry blossom biomes, camels, and new archeology mechanics without downloading a single file.
Unlike native Java Edition, which uses region files (.mca) on disk, Eaglercraft uses a combination of memory-mapped chunk storage and the browser's File System Access API for persistence. The client maintains a 21×21 chunk render distance (configurable down to 8 chunks for performance), using a distance-based LOD (level of detail) system to maintain 60 FPS even on integrated GPUs.