/
EaglercraftXServer
An industrial-grade Eaglercraft server
Adds support for various browser ports of Minecraft Java Edition to your Spigot, BungeeCord, or Velocity server.
a.k.a. "EaglerXServer"
Key Features
- EaglercraftX 1.8, Eaglercraft 1.12.2, and Eaglercraft 1.5.2 clients are supported
- Install on Spigot, BungeeCord, or Velocity from only a single JAR file
- Access dozens of exclusive Eaglercraft features through a cross-platform API
- Install packet translator modules for legacy protocol versions (1.5, 1.6, beta, etc)
- Native RPC protocol to access the API of a BungeeCord/Velocity server from Spigot
- Synchronize multi-proxy setups seamlessly using EaglerXSupervisor
Installation
EaglerXServer works best when installed on a reverse proxy (BungeeCord, Velocity), you can also install the plugin on your Bukkit/Spigot/Paper server, but we do not currently maintain Bukkit plugin support for versions above 1.17.
To get started, place the EaglerXServer JAR in the "plugins" folder of your Spigot, BungeeCord, or Velocity server. In most cases you will also need to use ViaVersion, ViaBackwards, and ViaRewind to make your Spigot servers compatible with 1.8. If you would like to support 1.5, add the EaglerXRewind JAR to the "plugins" folder as well. Add EaglerMOTD for animated MOTDs and EaglerWeb if you want to host a website from your server.
To connect to your server, use the same IP address and port as you would on Java edition, EaglerXServer adds a translation layer that converts any Eaglercraft connections on your server to a regular Java edition connection.
Please keep in mind that on BungeeCord and Velocity you must edit the EaglercraftXServer listeners config file to change the inject_address to match the address of one of the listeners configured on the underlying BungeeCord/Velocity server. This is different from how EaglercraftXBungee and EaglercraftXVelocity worked, where you could put any address and allow the plugin to open the port, this change was made to allow EaglercraftXServer to be better compatible with other plugins like ViaVersion and ProtocolLib.
Velocity Note: You may have issues if you attempt to use EaglercraftXServer with other plugins that also register plugin message event handlers, because Velocity's event bus will cause the plugin messages to be observed in an undefined order if an async handler is given higher priority than EaglercraftXServer.
xCord Note: You will probably have issues if you attempt to install EaglercraftXServer on xCord (premium fork of BungeeCord) depending what additional xCord configuration options you enable. If you have issues, reset the xCord configuration files to their defaults, EaglercraftXServer has been confirmed to work (or at least connects) on xCord if you use the default configuration files.
Configuration
On BungeeCord and Velocity, EaglercraftXServer should generate detailed comments in the config files, describing each property in detail. However this does not work on most Spigot versions (like 1.12) due to the YAML parser/serializer bundled with it not supporting comments. Please see the CONFIG.md file for documentation if your platform does not support comments.
Large server view distances are known to cause problems on the low bandwidth connections most people find themselves playing Eaglercraft on, consider reducing your server's view distance if you experience intermittent "End of stream" errors.
Plugin Development
The API is available through a "maven repository" at https://repo.lax1dude.net/repository/releases/
Please see the GitHub for more information on the EaglercraftXServer API
