Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/lDEVinux/eaglercraft/llms.txt

Use this file to discover all available pages before exploring further.

An Eaglercraft server requires two components running simultaneously: a standard CraftBukkit 1.5.2 backend that handles all game logic, and EaglercraftBungee, a modified BungeeCord proxy that translates WebSocket connections from browser clients into raw TCP that Bukkit understands. Neither component alone is sufficient — both must be running for players to connect.

Architecture

Browser clients never connect directly to Bukkit. Instead, they open a WebSocket connection to EaglercraftBungee, which proxies each connection over TCP to the Bukkit backend:
Browser  ──WebSocket──▶  EaglercraftBungee (:25565)  ──TCP──▶  Bukkit (:25569)
Both the Bukkit server and EaglercraftBungee processes must be running at the same time. If either one is stopped, players will be unable to connect.

Components

Bukkit 1.5.2

Standard CraftBukkit 1.5.2 server. Handles all game logic, world data, and plugin execution. Players and plugins interact with it exactly as they would on a normal Minecraft 1.5.2 server. Listens on localhost:25569 by default (TCP only — not exposed to the internet directly).

EaglercraftBungee

A fork of BungeeCord that adds WebSocket transport. Accepts WebSocket connections from browser clients and proxies them as raw TCP to Bukkit. Listens on 0.0.0.0:25565 by default. Vanilla BungeeCord will not work — you must use the EaglercraftBungee JAR included in the stable-download package.

Quick Setup

Follow these two guides in order to get a server running:
  1. Bukkit Setup →
    Download the stable-download package, launch the CraftBukkit 1.5.2 backend, configure plugins, and secure op permissions.
  2. EaglercraftBungee Setup →
    Start the WebSocket proxy, verify the connection from a browser client, and review key configuration options.

Optional Components

ComponentPurpose
NGINX reverse proxyEnables IP forwarding for bans and rate limiting, TLS termination for wss:// connections, and domain-based routing. See the NGINX Reverse Proxy guide.
Replit auto-setupAutomatically provisions both server components in a hosted environment. Use this Replit template if you want a quick cloud-hosted setup without managing your own machine.

Port Defaults

These defaults come directly from java/bungee_command/config.yml in the stable-download package:
ProcessProtocolAddressPurpose
EaglercraftBungeeWebSocket0.0.0.0:25565Accepts browser client connections
BukkitTCPlocalhost:25569Receives proxied connections from EaglercraftBungee
The host field in the listeners block controls what EaglercraftBungee binds to (0.0.0.0:25565), and the address field in the servers.lobby block is where it forwards connections (localhost:25569).

Build docs developers (and LLMs) love