Amazing Xray Modpack: How to Set Up a Server

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Running a modpack with friends? Godlike.Host offers modded Minecraft server hosting with one-click modpacks (CurseForge, FTB, Technic) and free DDoS protection.

To run an Amazing Xray server, choose one exact pack release first, download its matching AmazingXray+Server archive, install the supplied Fabric server files in a clean directory, accept Minecraft’s EULA, and have every player use the identical Minecraft version, pack release, and Fabric profile. The current main release is AmazingXray-[3.0.3]+(26.2), released August 10, 2026, with a matching AmazingXray+Server-[3.0.3]+(26.2) pack.

This guide covers a local or rented Java server, first startup, memory and networking choices, player setup, and the connection failures that account for most failed installations.

#	Preview	Product	Price
1		Minecraft - Bedrock Edition PS4	$42.98	Buy on Amazon

What Amazing Xray is—and what its server compatibility means

Amazing Xray is a Fabric-based Minecraft modpack by kesselot. Its CurseForge description calls it an xray-based pack that is compatible with every vanilla server and includes shaders. That wording describes compatibility with the vanilla server protocol; it does not remove the need to match the Minecraft version and the pack release on every participating client.

The project page lists current game-version entries including 26.2, 26.1.2, 26.1.1, 26.1, and 1.21.11. At the time of this guide’s update, the project page showed 630,442 downloads. The project is marked All Rights Reserved. Its owner says that reuploading the pack or a modified version to CurseForge or another website is not allowed without explicit permission, so obtain both the client and server files from the official project listing rather than a mirror.

#1 Best Overall

Minecraft - Bedrock Edition PS4

• Play and share with friends on console, mobile and Windows 10
• discover community creations in the new in-game store
• access new mini games and game modes through servers

$42.98

Buy on Amazon

Pick the exact release before downloading anything

Version discipline prevents nearly every avoidable connection problem. Decide the Minecraft version first, then use the corresponding client and server entries. The server, the operator’s client, and every player’s client should all use the same Amazing Xray release and Minecraft version. Minecraft’s multiplayer guidance states that the version being played must be the same version the server is running.

Do not infer that the newest client can join an older server, or that two entries with similar names are interchangeable. Read the complete filename in the Files section and make the game-version suffix match exactly.

What you need before setup

• Minecraft: Java Edition. The official Minecraft download information identifies Java Edition as the PC edition that supports mods and custom servers. Bedrock clients cannot join this Java/Fabric setup.
• A launcher that can install or import a CurseForge modpack. Install the exact client entry selected above for the operator and for each player.
• A compatible Java runtime. Java server software requires a compatible runtime. The pack listing does not specify a Java major-version number, so use the runtime supported by the selected Minecraft server software and verify that the host actually invokes it.
• A machine or hosting plan with enough memory and CPU. The project does not publish a pack-specific RAM requirement. As starting guidance, general hosting guidance places medium modpacks around 8 GB and larger packs around 10–16 GB; treat those figures as a starting point, not a guarantee.
• Permission to accept Minecraft’s EULA and, for internet play, access to the host firewall and router or the controls supplied by your managed host.

Download the right server pack

1. Open the official Amazing Xray project and its Files page.
2. Confirm the Minecraft version and release number you selected. For the current release, choose AmazingXray+Server-[3.0.3]+(26.2).
3. Download the entry whose name contains +Server. The ordinary AmazingXray-[3.0.3]+(26.2) file is the client pack and should not be uploaded as the server installation.
4. Keep a copy of the exact filename. You will use it to check that the host, operator client, and player clients are aligned.

Uploading one archive and extracting it on the server is normally faster and less error-prone than transferring hundreds of individual files. Never obtain a reuploaded or modified archive: the project owner’s license note prohibits redistribution without permission.

Install the server in a clean directory

On a local computer or virtual machine

1. Create an empty directory dedicated to this server. Do not place it inside an existing vanilla, Forge, NeoForge, or unrelated Fabric server directory.
2. Copy the downloaded +Server archive into that directory and extract it there. If extraction creates a nested folder, make sure the startup files and server files are in the directory you intend to launch.
3. Install the compatible Java runtime, then verify it from a terminal with the Java version command supplied by your operating system. A message that Java is not found means the runtime is missing or its executable is not on the system path.
4. Identify the start script or server jar supplied by the archive. Use that supplied launcher rather than constructing a Forge or NeoForge command.

On a managed game host

1. Create a new Java server instance with the Minecraft version that matches the pack.
2. Upload the archive through the host’s file manager or SFTP, extract it into the server root, and remove any files from a previous installation that could be loaded accidentally.
3. Choose the supplied Fabric startup script or jar in the host panel. If the panel asks for a loader, select Fabric; do not select Forge or NeoForge.
4. Set the Java version and memory in the panel before the first full launch. Host labels vary, so check which runtime the panel associates with the server process rather than assuming the system default is used.

The official pack listing identifies Fabric. A server that starts with another loader is not an Amazing Xray server, even if the directory contains some of the same mods.

First boot: EULA, configuration, and memory

1. Start the supplied script or jar once and watch the console. The first run normally creates configuration files, including eula.txt, and may begin world generation.
2. Stop the process cleanly after it creates the files. Open eula.txt and change eula=false to eula=true only after reading and accepting Minecraft’s EULA.
3. Save the file and start the same supplied launcher again. Do not delete the generated configuration files unless you are intentionally resetting the server.
4. Allow the process to finish loading. A slow first launch can reflect configuration work, mod initialization, or world generation; use the console log to distinguish activity from a crash.
5. Set memory appropriate to the machine. A practical starting point for a medium-sized pack is about 8 GB; larger worlds or player counts may need 10–16 GB. Because Amazing Xray publishes no pack-specific requirement, watch memory use and garbage-collection pauses and adjust rather than treating those figures as fixed specifications.

Leave headroom for the operating system and other services. Assigning all physical memory to Java can cause swapping or make the machine unresponsive, which is slower than giving the server a slightly smaller but stable allocation.

Networking: local play versus internet play

Players on the same local network

For a household LAN, the operator can give players the server computer’s private IPv4 address and the configured server port. Test from another computer on the same network before changing router settings. A local test isolates mod and server configuration from internet routing problems.

Friends connecting over the internet

1. Give the server a stable private address on the local network, either through a router reservation or a fixed host configuration.
2. Allow the Java server process through the operating system firewall.
3. Forward the server’s TCP port from the router to the server’s private address. Java servers normally use 25565 by default; use a different port only if your server configuration or host requires it, and tell players the changed port.
4. Give friends the public address and port, not the private 192.168.x.x or 10.x.x.x address used inside your home network.
5. Test from a connection outside your home network, such as a phone hotspot. Testing only from inside the same router can produce misleading results because some routers do not support hairpin connections.

Internet exposure increases risk. Use an allowlist or equivalent access control when self-hosting, keep the operating system and Java runtime updated, and stop the server when it is not needed. A managed host can remove router configuration from your workload, but you still control who receives the address.

Install the identical client profile

1. Have every player install Minecraft Java Edition and the same launcher profile for the selected Amazing Xray release.
2. In the launcher or modpack manager, import the exact client entry, including its Minecraft version and Fabric loader version.
3. Start the profile once in single-player to let the launcher download dependencies and confirm that the game reaches the main menu.
4. In Multiplayer, add the server’s local or public address and the correct port. The default is 25565 unless you changed it.

Every player must match the server on three separate values: the Minecraft version, the Amazing Xray release, and the Fabric loader/profile used by that release. A player using a newer pack with an older server, or a manually assembled profile with one missing mod, can receive an incompatibility message even when the address and port are correct.

Can you run it on a vanilla server?

The project description explicitly says Amazing Xray is compatible with every vanilla server. That makes a plain vanilla server a possible target for the gameplay protocol, but it does not make the client and server files interchangeable. For a dedicated installation, use the published matching +Server pack because it supplies the intended Fabric startup files and server-side contents for that release.

Do not upload the ordinary client archive to a vanilla server and expect it to become a server installation. Client-only files can cause an immediate crash or leave the server missing required components. Compatibility also does not bypass Minecraft’s version rule: a 26.2 client still needs a server running the same Minecraft version.

Self-hosting or managed hosting?

Both approaches can run the pack. The choice is mainly about who handles hardware, backups, and network access.

Whichever option you choose, retain an offline copy of the world and the server configuration before upgrading the pack or Minecraft version.

Troubleshooting checklist

The server crashes immediately

• Confirm that you downloaded the +Server entry, not the ordinary client pack.
• Check that the directory is clean and that files from another loader or older release were not left behind.
• Verify that the host is launching the supplied Fabric script or jar.
• Read the first error and its cause in the console rather than focusing on the final shutdown line.

The client reports an incompatible version or refuses the connection

• Compare the complete client and server filenames, including the release number and Minecraft suffix.
• Check the Fabric loader/profile used by the launcher and the server pack.
• Make sure the server finished starting and is listening before testing the client.

The command says Java cannot be found

• Install a Java runtime compatible with the selected Minecraft server software.
• Run the operating system’s Java-version check in the same account that launches the server.
• On a managed host, select the runtime in the panel; the panel’s default may differ from the system shell.

Friends cannot connect from outside the house

• Confirm the server’s configured port; Java’s normal default is 25565.
• Allow the Java process through the host firewall.
• Forward that port to the server’s current private address.
• Give friends the public address, and test from an external network.
• If your internet provider uses carrier-grade NAT, ordinary router forwarding may not provide a public inbound address; use a host with a reachable address or another access method rather than repeatedly changing local rules.

The first launch appears frozen

Watch CPU, disk activity, and the console. Initial configuration and world generation can take time. If the log stops at a clear exception, fix that exception; if it continues printing progress, allow the startup to finish before restarting.

Only one player cannot join

Have that player reinstall or repair the exact profile and compare the Minecraft version, Amazing Xray release, and Fabric loader with a player who can connect. A single missing or extra client mod is more likely than a router problem when other players are already online.

Pre-launch checklist

• Chosen one Minecraft version and one Amazing Xray release.
• Downloaded the matching +Server archive from the official project page.
• Extracted it into a clean directory.
• Installed and verified a compatible Java runtime.
• Selected the supplied Fabric startup files.
• Accepted the EULA in eula.txt.
• Allocated memory with operating-system headroom.
• Tested local connectivity before internet forwarding.
• Configured firewall and, when required, port 25565 forwarding.
• Installed the identical client profile for every player.
• Created a backup before inviting players or changing versions.

Updating or changing Minecraft versions safely

Treat a version change as a separate installation task. Stop the server, back up the world and configuration, download the new matching client and server entries, and test the new server with a copy of the world before making it public. Do not overwrite a working directory with a different release while players are online. If the new release fails, restore the backup and return to the previously working server files and client profile.

Keep the old archive and its version notes until every player has confirmed that the new profile works. This makes a rollback possible without guessing which files changed.

The Bottom Line

The reliable setup is simple: match the release and Minecraft version exactly, use the official Fabric +Server pack in a clean directory, complete the Java and EULA first boot, then configure firewall or port 25565 only for players outside your network. Most failures come from using the client archive on the server or letting one player’s version drift from the server.

Quick Recap

Bestseller No. 1

Minecraft - Bedrock Edition PS4

Play and share with friends on console, mobile and Windows 10; discover community creations in the new in-game store

$42.98

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.