Skip to main content

Documentation Index

Fetch the complete documentation index at: https://support.zonely.gen.tr/llms.txt

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

​
Minecraft Web Client

Minecraft Web Client allows players to join your Minecraft server directly from their browser without installing the Minecraft launcher. Players open the web join page, enter their username, and connect to the server. The required connection settings are prepared through the panel on the server side.
For setup, you only need to enable the Minecraft Web Client extension from the admin panel.

​
Things to Know Before Setup

The Web Client usually uses a connection address that starts with wss:// instead of a normal Minecraft server IP. Normal Minecraft address: 
play.yourserver.com
Web Client address: 
wss://play.yourserver.com
With a port: 
wss://play.yourserver.com:8081
If your site opens with https://, the Web Client connection address should also usually start with wss://. ws:// connections may not work on secure websites.

​
Enable the Web Client Extension

1

Open the admin panel

Log in to your site or server admin panel.
2

Open the extensions section

Go to Settings > Extensions.
3

Find the Minecraft Web Client extension

Open the Minecraft Web Client extension from the list.
4

Enable the extension

Enable the extension and open its settings page.
5

Copy the Web Client connection

Copy the wss:// connection shown in the panel exactly as it is.
The connection shown in the panel is usually in one of these formats: 
wss://your-server-address
or: 
wss://your-server-address:port
For the most reliable setup, use the address provided by the panel without changing it.

​
Which Address Should Players Use?

You can share the Web Client page link with your players. Example: 
https://yourwebsite.com/web-join
When the player opens the page, they enter their username and join the server directly if the connection information is already configured. If the Web Client asks for a server address, the player should enter the wss:// address provided in the panel instead of the normal Minecraft IP. Correct: 
wss://play.yourserver.com
Incorrect: 
play.yourserver.com

​
Server-Side Setup

For the Web Client connection to work, EaglerXServer is used on the server side. EaglerXServer is a server-side plugin that allows browser-based Minecraft clients to connect to Spigot, Paper, BungeeCord, or Velocity servers.
For a normal setup, EaglerXServer.jar is usually enough. The other jar files are for extra features.

GitHub Releases

You can download all EaglerXServer versions and jar files from this page.

EaglerXServer.jar

Main plugin. This is the first file to download for a normal setup.

EaglerXRewind.jar

Used when support for older 1.5.2 clients is needed.

EaglerXBackendRPC.jar

Used to access BungeeCord or Velocity API features from backend Spigot/Paper servers.

EaglerMOTD.jar

Adds MOTD-related features for Web Client players.

EaglerWeb.jar

Used to serve HTTP files through the server address.

EaglerXPlan.jar

Used to track Eagler players with the Plan player analytics plugin.

EaglerXSupervisor.jar

Standalone supervisor service used in multi-proxy setups.

​
Which File Do You Need?

For most servers, this file is enough:
EaglerXServer.jar
You do not need to install every jar file randomly. It is better to start with only EaglerXServer.jar.

​
EaglerXServer Setup

1

Check the Java version

Java 17 or newer is recommended.
java -version
2

Download the main plugin file

Download the EaglerXServer.jar file.
3

Put it in the plugins folder

Upload the file to your server’s plugins folder.
/plugins/EaglerXServer.jar
4

Restart the server

Restart the server. On first startup, the plugin will create its own configuration files.
5

Check the settings

If the connection does not work, check the plugin config files, ports, and listener settings.
If you are using BungeeCord or Velocity, you may also need to check the listener and inject_address settings.

​
EaglerXServer Extra Modules

The EaglerXServer release page includes multiple jar files. You do not need to install all of them.

EaglerXServer

Main connection plugin. It allows Web Client players to connect to the server.

EaglerXRewind

Used to support older Eaglercraft 1.5.2 clients.

EaglerXBackendRPC

Used to access the Eagler API on the proxy side from backend Spigot/Paper servers.

EaglerMOTD

Provides extra MOTD-related features for Web Client players.

EaglerWeb

Used to serve HTTP files or web content through the server address.

EaglerXPlan

Used to track Eagler players with the Plan analytics plugin.

EaglerXSupervisor

Standalone service used to synchronize proxies in multi-proxy setups.

​
What Is RPC?

RPC is used to access EaglerXServer features on the proxy side from backend Spigot/Paper servers. This is especially useful for BungeeCord or Velocity setups. Example structure: 
Player
  -> BungeeCord / Velocity
  -> Backend Spigot / Paper server
In this setup, if EaglerXServer is running on the proxy side, custom plugins on the backend Spigot server may need to detect Eagler players or access information from the Eagler API. EaglerXBackendRPC.jar is used for that.

​
When Is RPC Needed?

If you only want players to join through the Web Client, you do not need RPC.For a normal setup, EaglerXServer.jar is enough.

​
RPC Setup

1

Make sure EaglerXServer is installed on the proxy

EaglerXServer.jar must be running on the BungeeCord or Velocity side.
2

Add the RPC jar to the backend server

Add this file to the backend Spigot/Paper server’s plugins folder:
EaglerXBackendRPC.jar
3

Enable the RPC setting

Enable backend RPC support in the EaglerXServer settings.
enable_backend_rpc_api: true
4

Restart the servers

Restart both the proxy and the backend servers.
RPC is an advanced-use feature. It is not required for normal Web Client login.

​
Voice Chat Settings

EaglerXServer includes voice chat service settings for Eagler players. This feature is disabled by default. 
enable_voice_service: false
If you want to use the voice feature, you can enable the voice service in the configuration file: 
enable_voice_service: true
Voice chat should be used carefully on large public servers. Before enabling it, it is recommended to check rate limit, performance, and security settings.

​
Voice Settings You Should Know

enable_voice_service

Enables or disables the voice system. It is disabled by default.

enable_voice_all_servers

Controls voice usage on all servers on the BungeeCord or Velocity side.

enable_voice_all_worlds

Controls voice usage in all worlds on the Bukkit side.

separate_server_voice_channels

Controls whether each server uses a separate voice channel.

separate_world_voice_channels

Controls whether each world uses a separate voice channel.

voice_backend_relayed_mode

Allows voice packets to be managed through the backend Spigot server. RPC is required for this mode.

​
STUN / TURN Servers

The voice system uses WebRTC-style networking, so STUN/TURN servers can be used. Some STUN servers are included by default: 
stun:stun.l.google.com:19302
stun:stun1.l.google.com:19302
stun:stun2.l.google.com:19302
stun:stun3.l.google.com:19302
stun:stun4.l.google.com:19302
STUN may not be enough on some networks. For a more reliable voice connection, you may need your own TURN server.

​
Cloudflare and WSS Settings

If you want to use a custom subdomain for the Web Client connection, you can create a wss record through Cloudflare. Example WSS address: 
wss://wss.yourdomain.com
Cloudflare DNS record: 
Type: A
Name: wss
IPv4 address: Your server IP address
Proxy status: Proxied
For easier setup, the Cloudflare proxy status can stay as Proxied.
For a simple setup, you can use this mode in Cloudflare SSL/TLS: 
SSL/TLS encryption mode: Flexible
For more secure setups, Full strict can be used. This requires an SSL certificate on the server side.

​
Alternative: XAMPP / Apache Proxy

This section is only needed if you are using a separate WebSocket proxy. If the connection provided by the panel and the EaglerXServer setup are enough for your case, you can skip this section.

​
Apache Configuration

The following modules should be enabled in the httpd.conf file: 
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so
The following configuration can be added to httpd-vhosts.conf: 
<VirtualHost *:80>
    ServerName wss.yourdomain.com

    ProxyRequests Off
    ProxyPreserveHost On

    ProxyPass / ws://127.0.0.1:8081/
    ProxyPassReverse / ws://127.0.0.1:8081/
</VirtualHost>
Replace wss.yourdomain.com with your own domain. 8081 is the port where the WebSocket proxy is running.

​
Version Compatibility

If players will join with different Minecraft versions, version compatibility plugins may be required. Possible plugins:
  • ViaVersion
  • ViaBackwards
  • ViaRewind
  • EaglerXRewind
If the server and players use the same version, these plugins may not always be required.

​
Testing

After setup, you can test it like this:
1

Open the Web Client page

Open the web join page that players will use.
2

Enter a username

Enter a username for testing.
3

Enter the WSS address

Enter the wss:// address from the panel or the one you prepared into the server address field.
4

Try to connect

Click the Connect button and test joining the server.
If the login works, the setup is complete.

​
Common Issues

Make sure the wss:// address from the panel is written correctly. The Web Client connection should be used instead of the normal Minecraft IP.
The server may be offline, the Web Client extension may not be enabled, or the plugin may not be installed correctly.
If your site opens with https://, the connection address must also start with wss://. ws:// connections may not work on secure websites.
The Java version, server version, port, or listener settings may be incompatible.
Backend RPC support may not be enabled on the proxy side, or EaglerXBackendRPC.jar may not be installed on the backend Spigot/Paper server.
enable_voice_service may be disabled, STUN/TURN settings may be missing, or the player’s browser microphone permission may be blocked.
Compatibility plugins such as ViaVersion, ViaBackwards, ViaRewind, or EaglerXRewind may be required.

​
Setup Complete

Minecraft Web Client setup is complete. You can now share the web join link with your players. Players can join your server directly from the browser without installing the launcher.

Summary

Enable the Minecraft Web Client extension from the panel and use the wss:// address provided there. If manual server-side setup is required, place EaglerXServer.jar into the plugins folder. RPC and voice features are not required for normal login; enable them only if needed.