Free tools Windows power users keep installed
One-click scans. No signup required.
To host an FTB Evolution server, download the official server installer for one specific Evolution release, run it in a dedicated folder, accept the EULA, and start the generated launcher. The current official listing calls for Java 21, at least 6 GB of RAM, and 8 GB recommended. The installer can download the required Java runtime automatically, so you do not need to assemble a server by copying your client instance.
Godlike.Host offers modded Minecraft server hosting with one-click modpacks, a built-in mod installer and up to three free backups a day.
What you need before installing
FTB Evolution is distributed as a versioned modpack. A reliable server starts with a deliberate choice of release, matching client files, and enough resources on the host machine. Prepare these items before downloading anything:
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →| Requirement | What the official FTB listing establishes | Why it matters |
|---|---|---|
| Java | Java 21 | The pack’s current NeoForge 1.21-based releases expect this Java generation. |
| Memory | At least 6 GB of RAM | This is the minimum stated for running the server. |
| Recommended memory | 8 GB of RAM | Use the recommendation as your starting allocation, while leaving memory for the operating system and other applications. |
| Server files | The official FTB Evolution server installer for the selected release | The installer retrieves the correct libraries, loader files, scripts and configuration instead of relying on a manually copied client instance. |
| Network access | A local network for initial testing; firewall and router/NAT access for remote players | Local testing separates installation problems from internet connectivity problems. |
The listing contains multiple Evolution releases, release IDs and a server-files browser. Record the release ID you choose. “Latest” is not a permanent target: a new release can change mod versions or configuration and make an existing world incompatible with an unplanned upgrade.
Choose and record one Evolution release
Use the official versions and server-files page
Open the official FTB Evolution versions/server-files page and select the release your group intends to play. Confirm that the page offers server files for that release, then download the installer associated with it. The page exposes release history and NeoForge 1.21 tags, so check the release identifier rather than relying only on a displayed date or the word “latest.”
#1 Best Overall
Keep the release ID as a deployment record
Write the identifier in a small text file beside the server, in your group chat, or in your password manager. Use the same identifier when installing every player’s client. This simple record prevents a common failure mode: one person updates the client while the server remains on an older pack.
Do not build a server by copying a client
A client instance contains files that are not a complete dedicated server installation. Copying it can omit server libraries, generate incorrect launch arguments, or leave client-only mods in the server directory. The official installer is designed to download and arrange the server components for the selected release.
Install the server with the official installer
- Create a dedicated folder. Make a short, easy-to-find path used only for this server. Examples are
C:GamesFTB-Evolution-Serveron Windows,~/servers/ftb-evolutionon Linux, or~/Games/FTB-Evolution-Serveron macOS. Avoid placing the world in a temporary downloads folder. - Download the installer for the host architecture. On the official server-files page, choose the download or command shown for your operating system and CPU architecture. The macOS instructions display a
curldownload followed bychmod +x; copy those commands exactly as presented for the selected release rather than substituting a client download. - Put the installer in the dedicated folder. If the browser saved it elsewhere, move it before running it. Keeping the installer and generated files together makes backups and later reinstalls easier.
- Run the installer. Start the downloaded executable or script from that folder. FTB’s guide says the installer downloads the required server files and Java runtime. Allow the process to finish; stopping it part-way through can leave an incomplete directory that looks installed but cannot launch.
- Inspect what was generated. Look for the generated server launcher or start script, the configuration files, the libraries directory and the world directory after the installer completes. The exact filenames can vary by release and operating system, so use the launcher generated for your chosen release instead of inventing a new command.
- Start the generated launcher once. Run the script from the server folder. The first start normally creates configuration files and pauses for the Minecraft EULA. Read the EULA, set the required acceptance value in the generated file, save it, and start the launcher again.
- Wait for a completed startup. A usable server reports that it has finished loading and is ready for connections. Do not close the terminal while it is running unless you use the server’s normal stop command or console action; abruptly terminating it risks world corruption.
- Stop and review before inviting anyone. Use the server console’s stop command, then open the generated configuration files. Set an appropriate message of the day, difficulty, whitelist policy and other options before the first public connection.
Java 21: what to install and what not to troubleshoot first
The current FTB Evolution listing specifies Java 21. You can install that version yourself, but the official installer is intended to obtain the required runtime automatically. FTB’s server FAQ states: “No, the server installer will download the correct version of Java for you.”
That means a missing system-wide Java command is not automatically a blocker. First run the generated launcher and read its output. If the installer completed but the launcher reports that Java cannot be found, verify that the download was allowed to finish, that security software did not quarantine the runtime, and that you are starting the launcher from the directory where the installer generated it. Only then consider configuring a system Java 21 installation and pointing the launcher to it according to your operating system’s instructions.
Do not force an older Java executable just because another Minecraft installation uses it. A launcher that starts with the wrong Java generation can fail before NeoForge loads, report unsupported class versions, or behave unpredictably during mod initialization.
Configure the first run safely
Accept the EULA once, deliberately
The first start creates the EULA file. Open it in a plain-text editor, change only the acceptance setting required by the document, save it, and restart. If the server still stops immediately, check that the file was saved with the expected name and extension rather than as a second text extension.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteReview server.properties
Before opening the server to friends, inspect the generated server.properties file. Useful settings include:
- motd: identify the world and release so players know which server they joined.
- difficulty: choose the setting that matches your group; changing it later can affect gameplay.
- gamemode and related permission settings: decide whether the world is intended for survival, creative building or a controlled test.
- white-list: enable it when only named friends should connect, then add players through the server console.
- server-port: keep the generated value unless you have a specific reason to change it; any changed value must also be reflected in firewall and router rules.
- online-mode and authentication-related options: leave them at their secure defaults unless you understand the consequences of changing them.
Make changes while the server is stopped, then start it again and verify that the console accepts the file without errors.
Protect the world directory
Do not edit world files while the server is running. Stop the server cleanly before copying its world directory or changing mod configuration. Keep the server folder’s permissions limited to the account that runs the service, particularly on a machine shared with other users.
Install the matching client for every player
- Have each player install the exact FTB Evolution release ID selected for the server.
- Launch that profile once so the client downloads its files and completes any first-run setup.
- Do not add or remove mods, resource dependencies or configuration files casually. A server can reject a client whose mod list or versions differ even when both installations are called FTB Evolution.
- Give players the server address only after the host has passed a local-network test.
When a connection fails with a missing-mod, mismatched-version or registry error, compare the release ID first. Reinstalling the client with the exact server release is usually more productive than changing network settings.
Rank #3
- The classic UNO card game builds fun on game night with a Minecraft theme.
- UNO Minecraft features a deck and storage tin decorated with graphics from the popular video game.
- Players match colors and numbers to the card on top of the discard pile as in the classic game.
- The Creeper card unique to this deck forces other players to draw 3 cards.
- Makes a great gift for kid, teen, adult and family game nights with 2 to 10 players ages 7 years and older, especially Minecraft and video game fans.
Test locally before exposing the server
Test on the host computer
With the server running, connect from the same computer using the local address offered by the game. This confirms that Java, NeoForge, the pack files and the world can load without involving the router.
Test from another device on the same LAN
Connect a second computer on the same home network using the host machine’s private LAN address and the configured server port. If this works, the server process and local firewall are broadly functional. If it fails, keep the server private and check the host firewall rule, the address used, and whether both devices are actually on the same network rather than an isolated guest Wi-Fi.
Check the console while connecting
Watch for a player-login line, a rejected authentication message, a missing-mod error or a timeout. The console tells you whether the request reached the server. A timeout with no console activity usually points to firewall, address or routing trouble; a detailed disconnect after the login reaches the console is more likely a client or pack mismatch.
Let friends join from outside your home
Allow the server through the host firewall
Create an inbound rule for the server program or its configured port, limited to the network profiles you actually use. Apply the rule to the Java executable or generated launcher identified by your operating system, not to an unrelated client installation. After creating it, repeat the LAN test.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteConfigure router/NAT forwarding
Remote players need the router to forward the server’s configured port to the host computer’s private LAN address. Reserve that private address in the router or operating system so it does not change after a reboot. Enter the same port in the forwarding rule and in any host-firewall rule.
Rank #4
- Now Minecraft lovers can play a special version of UNO!
- Same as Basic UNO but features Minecraft characters and includes special Creeper rule card. Draw this card and the other players have to draw three more cards from the pile!
- The goal is to get rid of all the cards in your hand.
- First player or team to 500 wins.
- When you're down to one card, don't forget to yell "UNO"!
Give players the correct address
People on your LAN use the host’s private address. People on the internet use the public address presented by your router, together with the configured port when the game requires it. Do not post your public address in a public forum; share it only with the people you intend to invite.
Recognize networks that cannot accept inbound connections
Some internet services place customers behind carrier-grade NAT, and some university, apartment or mobile networks block inbound forwarding. In that situation, a correctly configured home router may still be unreachable from outside. Ask the internet provider whether you have a publicly reachable address, or use managed FTB server hosting instead of repeatedly changing local settings.
Self-hosting versus managed hosting
Self-hosting gives you direct control over files and network access, while a managed service moves routine infrastructure work to a provider. FTB’s official pages establish the pack’s Java and memory requirements but do not endorse a particular commercial host.
| Decision factor | Self-hosting at home or on your own virtual machine | Managed FTB server hosting |
|---|---|---|
| Monthly cost | No FTB hosting fee is stated; you provide the computer, electricity or virtual-machine budget and internet service. | Price varies by provider and plan; verify the current price directly. |
| RAM and CPU | You must supply the official memory requirement and enough CPU capacity for your players and other workloads. FTB does not state a universal CPU model or player limit. | Choose a plan that explicitly offers at least the official memory requirement, with headroom for your world and operating system. |
| Java and installer support | You run the official installer and maintain its generated Java runtime and scripts. | Confirm that the host supports the exact Evolution release, Java 21 and the official server-files workflow. |
| Backups and restore | You design, schedule and test your own backups. | Check whether automated backups, retention and one-click restores are included; these features are not guaranteed by the term “managed.” |
| Network accessibility | You configure the firewall, router/NAT and public address, and you may face carrier-grade NAT. | The provider normally supplies a reachable server address, subject to its network policy. |
| Monitoring and uptime | You monitor the process, disk space, memory and reboots yourself. | Ask what monitoring, restart behavior and support response are included. |
| Upgrades | You back up, update the server and update every client together. | Check whether upgrades are manual, assisted or automatic, and whether you can choose the release. |
Choose self-hosting when you are comfortable with router administration and backups and want complete file control. Choose a managed service when inbound networking, uptime or maintenance is more important than running the infrastructure yourself. In either case, verify support for the specific Evolution release rather than assuming that support for another FTB pack is equivalent.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Memory allocation and performance checks
Start with the official recommended allocation rather than assigning every available gigabyte. The operating system, Java process, disk cache and any simultaneous game client need memory outside the server allocation. A machine that appears to have enough total RAM can still swap or become unstable if the server is given all of it.
After several normal play sessions, watch the server console and operating-system monitor:
- Repeated out-of-memory errors indicate that the allocation or workload needs attention.
- Long pauses during garbage collection can indicate memory pressure, a busy world or an overloaded machine.
- Consistently low memory use with lag suggests that CPU, disk or network limits may be the real bottleneck.
- A full disk can stop world saves even when RAM is sufficient, so monitor free space as the world grows.
Change one variable at a time, keep a note of the old setting, and test with the same player activity. Avoid copying generic JVM flags from unrelated packs; the generated launcher is the safest baseline for this release.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Backups, updates and release changes
Make a restorable backup
Stop the server cleanly, copy the world and relevant configuration files to a different disk or storage account, and label the backup with the Evolution release ID and date. A backup that has never been restored is only a copy, so periodically test it by opening it in a separate server directory.
Update server and clients together
When FTB publishes a new Evolution release, read its release information, make a backup, and decide whether the group wants the change. Update the server and every client to the same release as one maintenance event. Keep the previous server directory until the new version has loaded the world successfully and players have confirmed that important machines, quests and inventories behave normally.
Recover from a failed update
- Stop the failed server and preserve its logs and world directory.
- Do not overwrite the backup or delete the previous release.
- Restore the last known-good server directory or world backup.
- Return all clients to the matching previous release.
- Investigate the failed release separately, then retry only after confirming compatibility.
Troubleshooting by symptom
| Symptom | Most likely checks |
|---|---|
| Launcher exits immediately | Read the console output; verify the installer completed, the generated launcher is being used, Java 21 is available to it, and the EULA setting has been accepted. |
| “Java version” or class-version error | Remove the older Java path from the launch command and use the runtime supplied by the installer or a confirmed Java 21 installation. |
| Client says missing mods or incompatible registry | Compare the server’s recorded release ID with the client’s profile and remove unapproved client-side changes. |
| LAN connection times out | Confirm the host’s private address, configured port, firewall rule and that the second device is not on guest Wi-Fi. |
| LAN works but remote friends cannot connect | Check router forwarding, the host’s reserved private address, the public address, carrier-grade NAT and the ISP’s inbound policy. |
| Players connect but the world lags | Check memory pressure, CPU load, disk space and simultaneous workloads before changing Java flags or adding hardware. |
| World changes disappear after a crash | Restore the most recent clean backup, then investigate abrupt shutdowns, full storage and operating-system power events. |
Pre-invite checklist
- The server and every client use the same recorded Evolution release ID.
- The official installer completed and generated the launcher and configuration files.
- Java 21 is available through the installer-managed runtime or a verified system installation.
- The EULA is accepted and the server reaches a completed startup.
- Whitelist, authentication and gameplay settings match your group.
- A clean backup exists outside the live server folder.
- The host passes a same-machine and same-LAN connection test.
- Firewall and router rules use the actual configured port.
- Remote players receive only the appropriate address and release instructions.
- You know how to stop the server cleanly and where the backups are stored.
Final decision
The dependable route is consistent: select one official Evolution release, run its server installer in a dedicated directory, let it obtain the required Java runtime, accept the EULA, and test locally before configuring internet access. Keep the server and clients on the same release, start with the official recommended memory allocation, and preserve a tested backup before every upgrade. If your network cannot accept inbound connections or you do not want to maintain Java, firewalls, backups and updates, a managed FTB host is the practical alternative—provided it explicitly supports Evolution, Java 21 and your chosen release.
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.
