Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →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 host MC Eternal 2, install 64-bit Java 17, download the matching [MCE2]-Server-Pack-1.3.zip from the pack’s CurseForge Files page, extract it to a dedicated machine, accept the EULA, and run the included start file. Every player must use the same MC Eternal 2 release on Minecraft 1.20.1 with Forge. For friends outside your home, forward TCP port 25565 (or use a tunnel), then keep authentication and whitelist settings configured deliberately.
What MC Eternal 2 hosting requires
MC Eternal 2 is a large Forge modpack for Minecraft 1.20.1. It combines quests, exploration, magic and technology, so a server handles substantially more work than a lightly modded or vanilla world. CurseForge lists multiplayer support and recommends using a server when a local computer cannot run the pack comfortably. The current server-pack release listed for this version is [MCE2]-Server-Pack-1.3.zip, released September 22, 2026.
- Game and loader: Minecraft Java Edition 1.20.1 with Forge, matching the pack release.
- Java: a 64-bit Java 17 distribution. The compatibility guidance places Java 17 with Minecraft 1.18 through 1.20.4, which includes 1.20.1.
- Server files: the official MC Eternal 2 server pack, not a folder assembled by copying every client mod.
- Hardware: a machine that can stay powered on, with fast storage and enough memory for Forge, the world, chunk generation and all connected players.
- Networking: local-IP access on a home network, or port forwarding/tunneling for players on the internet.
- Account security: authenticated accounts in online mode and a whitelist if access should be limited.
CurseForge’s files page records 1,884,580 downloads for the project in 2026. That figure indicates broad use, not a performance guarantee or a server capacity test.
Choose self-hosting or managed hosting
Self-hosting on your own computer
Self-hosting gives you control over files, backups, configuration and upgrades. It has no separate hosting fee, but the computer must remain on while people play. You are also responsible for Java installation, firewall rules, router configuration, crash recovery and backups. A desktop with an SSD and a modern CPU is preferable to an older laptop or a hard disk, especially while new terrain is being generated.
#1 Best Overall
Managed MC Eternal 2 server hosting
A managed service is simpler when you do not want to expose a home network or maintain Forge files yourself. The documented CurseForge workflow deploys a matching server-pack file, supplies a control panel for console, files, restarts and backups, and removes manual uploads and router port forwarding. Provisioning is performed by Shockbyte and billing by Tebex in that workflow.
| Documented tier | Memory | Shared CPUs | Documented player range | Listed monthly price |
|---|---|---|---|---|
| Iron | 4 GB | 2 | 1–5 players | $12 |
| Gold | 8 GB | 3 | 6–15 players | $24 |
| Diamond | 12 GB | 4 | 16–25 players | $36 |
These are provider plan descriptions, not guaranteed MC Eternal 2 performance thresholds. Heavy modpacks can need a larger tier even with fewer players because memory use depends on the mod count, loaded chunks and what players are doing. Prices, regions and availability can change, so check the current panel before purchasing. For MC Eternal 2, leave headroom rather than choosing only by the nominal player count.
Plan RAM, CPU and storage realistically
Client memory is not the server minimum
The pack author describes MC Eternal 2 as heavy and suggests at least 16 GB of total system RAM, with 8–10 GB allocated to the client. That guidance is for a player’s computer, not an official server minimum. A dedicated server needs memory for Forge, loaded chunks, entity and machine data, world generation and concurrent players in addition to the operating system.
No official server-only RAM minimum is established. Start with a conservative allocation, watch actual memory and tick performance, and increase the server’s tier or allocation if it repeatedly approaches its limit. Giving Java every byte of physical memory is counterproductive: the operating system and background services still need room.
CPU and disk considerations
- Use a modern CPU with strong per-core performance. Modded Minecraft’s simulation and world generation can become tick-bound even when total CPU utilization looks moderate.
- Use an SSD. It reduces startup, region-file access and save delays compared with a mechanical disk.
- Keep several gigabytes free for the operating system, backups and future world growth.
- Pre-generate terrain with the Chunky mod included in the pack. Generating a planned area before players explore it moves the expensive work out of peak play sessions and reduces sudden world-generation lag.
Match resources to how your group plays
Five players spread across unexplored terrain can create more load than ten players staying in one base because each distant area adds chunk loading and generation. Automation-heavy bases, machines, farms, dimensions and large numbers of entities also increase simulation work. Treat player count as one input, not a promise that a plan will perform identically for every world.
Install Java 17 and verify it
- Install a 64-bit Java 17 distribution on the future server machine. Do not rely on a 32-bit runtime; a large modpack needs a 64-bit process.
- Open a terminal or command prompt.
- Run
java -version. - Confirm that the reported major version is 17. If the command is missing or reports another major version, correct the Java installation or PATH before unpacking the server.
Java 17 is the compatibility target for this pack’s Minecraft 1.20.1 base. Installing several Java versions is possible, but the start file must resolve to Java 17 rather than an older or newer runtime.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
Install the official MC Eternal 2 server pack
- Create a dedicated directory on a machine that can remain powered on. Avoid putting server files inside a temporary downloads folder or a client installation directory.
- Open the MC Eternal 2 project’s Files page in CurseForge.
- Download [MCE2]-Server-Pack-1.3.zip, or the exact server-pack release that matches the clients who will connect. Do not silently mix releases.
- Extract the ZIP directly into the dedicated server directory. The modded-server guidance expects you to unzip the server pack and use its included start file.
- Start the server once with that included start file. The first launch creates configuration, world and agreement files, then stops because the EULA has not been accepted.
- Open
eula.txtin the server directory. Changeeula=falsetoeula=true, save the file and close the editor. - Run the included start file again. Watch the console until Forge finishes loading and the server reports that it is ready for connections.
The exact start-file name and Java memory arguments are supplied by the server pack. Use those files as provided rather than inventing a different launcher command. If you later change memory arguments, retain the pack’s loader and classpath settings.
Keep clients and server on one exact release
Every connecting player must use Minecraft 1.20.1, Forge and the same MC Eternal 2 release as the server. A client on a newer or older pack revision can fail during the handshake, report missing or extra mods, or disconnect while loading.
When updating, schedule the change for everyone:
- Stop the server cleanly and make a backup of the world and configuration.
- Download the corresponding newer server pack from the MC Eternal 2 Files page.
- Update each player’s client to that exact release.
- Apply the server-pack files according to the pack’s upgrade instructions, preserving the world and intentional configuration changes.
- Start the server and have one test player connect before announcing the update to the whole group.
Do not add client-only mods to the server’s mods directory. The modded-server guidance warns that client-only additions can stop the server from working. If a player has added a performance or visual mod, verify that it is server-safe before distributing it to everyone.
Rank #4
Configure the server before inviting anyone
Authentication and whitelist
Keep online-mode=true in server.properties so Minecraft accounts are authenticated. Players should sign in with legitimate Java accounts. Turning online mode off can allow unauthenticated names and creates identity and security problems; it is not a fix for a normal login error.
If only selected people should join, set white-list=true. Add approved usernames through the server’s whitelist controls, then leave the whitelist enabled. Review the list whenever someone leaves the group or changes account names.
Backups and shutdowns
Use the hosting panel’s backup controls when managed hosting provides them, or copy the world and configuration while the self-hosted server is stopped. A live copy can capture partially written region files. Keep at least one backup away from the server machine so a disk failure does not destroy both the world and its backup.
Performance preparation
- Choose a world-generation area and pre-generate it with Chunky before a busy play session.
- Set expectations with players: exploring many new chunks at once is the most demanding activity.
- Monitor console warnings, memory use and tick-delay messages after adding machines, dimensions or large farms.
Make a self-hosted server reachable
Players on the same home network
Give a local player the host computer’s private IP address and the server port. The standard Minecraft port is 25565. A local connection does not require exposing the server to the public internet, but the host firewall must allow the Java server process or its listening port.
Players outside your home
- Assign the host computer a stable private address on the home network, preferably through a router DHCP reservation.
- In the router’s port-forwarding section, forward TCP port 25565 to that private address and the same destination port.
- Allow the server through the host operating system’s firewall. Restrict the rule to the required port rather than disabling the firewall.
- Give friends your public address and port only after testing from a network outside your home.
- If your internet service uses carrier-grade NAT or blocks inbound forwarding, use a tunnel instead. Tunnels avoid router changes but can be less stable, and their setup and limits vary.
Do not publish a home IP address casually. Share connection details only with intended players, keep the whitelist enabled for a private group, and change access settings when the membership changes.
What players enter
On the Minecraft multiplayer screen, a local player enters the host’s private IP; an internet player enters the public address. Include :25565 when the connection uses a non-default port. All players still need the exact same pack and Forge release; networking cannot correct a mod mismatch.
Use managed hosting when you want fewer network tasks
- Open the CurseForge app’s Minecraft area and select Servers.
- Choose MC Eternal 2.
- Select the exact server-pack file that matches the clients, including the release number.
- Choose a plan and a region, set the server name and complete the purchase.
- Use the resulting control panel for console access, file management, restarts and backups.
This workflow is useful when you cannot configure a router, do not want a home machine running continuously, or prefer provider-managed hardware. It does not remove the need to coordinate pack versions, manage player permissions or monitor a heavy world. Select a plan with memory headroom; the 4 GB entry tier may be insufficient for a busy or exploration-heavy MC Eternal 2 world even when the listed player range appears suitable.
Troubleshoot the problems that appear most often
| Symptom | Likely cause | Fix |
|---|---|---|
| The server stops immediately on first launch. | The EULA is still false. | Open eula.txt, change eula=false to eula=true, save and start again. |
| A player receives a mod-list or handshake error. | Minecraft, Forge or MC Eternal 2 releases differ. | Compare the server-pack filename and every client’s profile; install the same 1.20.1 Forge pack release everywhere. |
| Friends on the internet time out, but local players connect. | Port forwarding, firewall or public-address problem. | Check TCP 25565 forwarding to the correct private IP, confirm the firewall rule and test the current public address from outside the home. |
| The server crashes after a mod was added. | A client-only mod or incompatible modification is in the server folder. | Remove the added mod from the server, restore the matching pack files and start again. Distribute only server-safe additions. |
| Exploration causes long pauses or severe tick lag. | New chunks are being generated under load. | Pre-generate the intended area with the included Chunky mod, use an SSD and consider more CPU or memory headroom. |
| Players see authentication errors. | Account login or online-mode configuration problem. | Keep online-mode=true, have players sign in with legitimate Java accounts and avoid using offline mode as a workaround. |
When diagnosing a crash, change one thing at a time and keep the console log. A clean stop followed by a backup is safer than repeatedly launching a damaged world with experimental files.
A practical launch checklist
- Java 17 is installed as a 64-bit runtime and
java -versionreports major version 17. - The server directory contains the official MC Eternal 2 server-pack files.
- The server and every client use Minecraft 1.20.1, Forge and one identical MC Eternal 2 release.
- The first launch completed,
eula=trueis saved and the server reaches its ready state. - Client-only mods are not in the server’s
modsfolder. - Memory is reserved for Forge, the world, players and the operating system; the machine uses an SSD where possible.
- Chunky has pre-generated the area you expect players to explore early.
- For internet play, TCP 25565 is forwarded to the host, the firewall permits it and an outside-network test succeeds.
online-mode=trueis retained, andwhite-list=trueis enabled when the server is private.- Backups exist before inviting players and before every pack update.
Bottom line for MC Eternal 2
The reliable path is to run the official server pack on Java 17, not to reconstruct a client profile manually. Use Forge 1.20.1 and one exact pack release on both sides, allocate resources for a heavy modded world, pre-generate chunks, and expose only the networking you actually need. Self-hosting offers control; managed hosting removes router and deployment work but charges monthly and may require more than its entry plan. With authentication, a whitelist, tested port forwarding and current backups, your group can join without turning every connection problem into a modpack reinstallation.
Quick Recap
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.
