FTB Evolution 2 Server: Requirements and Setup (26.1.2)

Published on

FTB Evolution 2 server requirements and setup: Minecraft 26.1.2, NeoForge 26.1.2.126, Java 25, FTB's RAM figures, the installer and what 1.7.0 changed.

FTB Evolution 2 server setup

You want an FTB Evolution 2 server for your group and need to know what it takes. The pack came out on 8 October 2026 and runs on Minecraft 26.1.2, so it needs a newer Java than the FTB packs on 1.21.1, and a few server settings work differently from what older guides tell you. Everything below comes from FTB's API, the pack's own server files and the source code of FTB's server installer, all checked on 3 November 2026, when the current release was 1.7.0. For the other current FTB packs, see the table in our FTB server hosting guide.

Quick answer: An FTB Evolution 2 server on release 1.7.0 (2 November 2026) needs Minecraft 26.1.2, NeoForge 26.1.2.126 and Java 25. FTB asks for at least 6 GB of RAM and recommends 8 GB, and its installer sets that 8 GB as the Java heap, so give the server more memory than that in total. Get the installer from FTB's Server Files page (pack 135, release 100594), run it in an empty folder and start the server with the run.sh it writes. The installer downloads Java 25 for you.

FTB Evolution 2 server requirements

FTB Evolution 2Release 1.7.0
Released2 November 2026 (the pack launched on 8 October 2026)
Minecraft26.1.2
LoaderNeoForge 26.1.2.126
Java25 (the installer fetches 25.0.2)
RAM, FTB's figuresat least 6 GB, 8 GB recommended
Mod files426, of which 34 are client only
Pack ID / release ID135 / 100594

Java 25 is not an FTB quirk. Mojang's version file for 26.1.2 names Java 25 as the required major version, so the Java 21 runtime that runs StoneBlock 4 or the first FTB Evolution is too old for this pack. Our Minecraft Java version guide has the full list per version.

Plan the disk as well: the server side of FTB's 1.7.0 file list adds up to close to 700 MB before NeoForge, Minecraft and Java are added, and the world and its backups grow from there.

Install the FTB Evolution 2 server files

FTB does not ship a server zip. Each release has one installer that downloads the pack files, the loader and Java from FTB's servers (FTB's server guide). On the Evolution 2 server files page, pick the release. For 1.7.0 on a Linux server with an Intel or AMD CPU:

mkdir ~/evolution2 && cd ~/evolution2
curl -JLO "https://api.feed-the-beast.com/v1/modpacks/public/modpack/135/100594/server/linux"
chmod +x serverinstall_135_100594
./serverinstall_135_100594

On an Arm server, the same page gives https://api.feed-the-beast.com/v1/modpacks/public/modpack/135/100594/server/arm/linux, which saves a file with the same name. On Windows, use the Desktop download button and double-click the .exe.

A few things to know while it runs:

  • Keep the file name. FTB's guide warns against renaming it: the installer reads the pack ID and release ID from the name and asks you for both if it cannot.
  • Say yes to Java unless you bring your own Java 25. The installer puts it in a jre folder inside the server folder and points run.sh at it.
  • Accept the EULA yourself. Read Minecraft's EULA, then set eula=true in eula.txt, or start the installer with -accept-eula, which writes that line for you and counts as your agreement.

For an unattended install, the flags from the installer's README and source do the work:

./serverinstall_135_100594 -auto -accept-eula

-auto skips the questions and downloads Java unless you add -no-java. In a folder that is not empty and holds no earlier FTB install, it stops with a warning unless you add -force. When it finishes, start the server with ./run.sh (run.bat on Windows).

On a hosting panel that starts the server with its own Java, set that Java to 25. If you upload a folder you installed elsewhere, keep its structure and the start line from run.sh; NeoForge starts from argument files, not from one server jar you can point a panel at.

How much RAM an FTB Evolution 2 server needs

FTB's pack page lists at least 6 GB and 8 GB recommended. The installer turns the recommended figure into your heap: in its NeoForge code, when user_jvm_args.txt has no -Xmx line yet, it adds -Xmx8192M. FTB's memory guide explains that -Xmx is the maximum memory for the server. Java uses memory on top of the heap for class data, threads and garbage collection, so a server with exactly 8 GB in total is tight.

To change the heap, edit the -Xmx line in user_jvm_args.txt and check it again after every update. FTB's memory guide adds that on a hosting company you may not be able to change memory this way; your plan's limit decides. Our modpack hosting page lists 12 to 16 GB for packs whose server files set the same 8 GB heap, such as FTB StoneBlock 4 and All the Mods 11, and you can upload the server folder the installer built over SFTP.

More players, a bigger explored world and large factories need more, so watch memory use while your group plays before you change the plan or the flags.

Server settings the pack ships

Evolution 2 includes the Default Server Properties mod and a default-server.properties file. According to the mod's README, it feeds those values into the creation of server.properties on the first start. A server.properties you copy in from another server keeps its own values, so compare it with the pack's file for 1.7.0:

allow-flight=true
enable-command-block=true
max-tick-time=180000
sync-chunk-writes=false
spawn-protection=0
view-distance=10
simulation-distance=10
max-players=20
difficulty=normal
motd=A FTB Modpack Server

What the lines that differ from vanilla do, according to the Minecraft Wiki:

  • allow-flight=true lets players fly in Survival with mods. With false, the server kicks players who stay in the air for 5 seconds or more.
  • max-tick-time=180000 gives the watchdog three minutes before it treats one long tick as a crash and stops the server. Vanilla uses 60000, one minute.
  • sync-chunk-writes=false turns off synchronous chunk writes. They protect against data loss and corruption after a crash at some cost in disk speed, which is one more reason to keep backups.
  • spawn-protection=0 turns vanilla spawn protection off. The pack uses FTB Chunks claims instead; the 1.7.0 changelog names the claim on the spawn pyramid.

Stop the server before you edit the file; changes apply after a restart.

Command blocks are a game rule on 26.1.2

The enable-command-block=true line is a leftover from older versions. Mojang removed that property in Java Edition 1.21.9 in favour of a game rule that defaults to true, and 1.21.11 renamed the rule to minecraft:command_blocks_work. On a new 26.1.2 world, command blocks follow that rule, not the line in server.properties. To check it, type this in the server console:

gamerule minecraft:command_blocks_work

If it reports false, gamerule minecraft:command_blocks_work true switches command blocks back on.

What changed in Evolution 2 1.7.0

FTB published 1.7.0 on 2 November 2026. Its changelog and the version data hold three things a server owner should know:

  • New NeoForge. The loader moved from 26.1.2.121, used from 1.3.1 to 1.6.3, to 26.1.2.126. The installer brings it along; a panel that pins its own NeoForge build needs the new one.
  • Mods in and out. Added: ME Requester, and Applied Replicatics, which replaces Replication AE2 Bridge. Removed: Better Fishtanks, "along with its quests, its Fishmonger trade and the Raw Minishrimp fishing drop". The changelog does not say what happens to those mods' placed blocks in an existing world, so if your base uses them, test the update on a copy first.
  • Fixes your players notice. No more disconnects when someone opens a wireless pattern encoding terminal while holding an item such as an Ars Magica Infinity Orb, no more item duplication through the Paradox Machine, and no more client memory climbing while wearing Quantum Armor. That last one is a client fix, so players need 1.7.0 too.

Evolution 2 moves fast. FTB's version list holds 21 versions from 1.0.0-rc.1 on 7 October to 1.7.0, and a friend who installs the pack a week after you can land on a newer release than your server runs. Share the release number together with the address.

Update the server with the installer

Download the installer for the new release and run it in the existing server folder. From its source code: it reads the .manifest.json the previous install wrote, deletes the files the new release dropped, downloads the files that changed and leaves the rest alone. A config file you edited survives only if the new release did not change that file. It will not go back to an older release in -auto mode unless you add -force, and it asks first when you run it by hand.

Before you run it, stop the server and copy the world, config, server.properties and user_jvm_args.txt to a folder outside the server folder. After the update, check server.properties and user_jvm_args.txt again.

FTB Backups 3 on Evolution 2

The pack ships FTB Backups 3, set up in config/ftbbackups3-server.json5. Its 1.7.0 defaults: a ZIP backup every 120 minutes, only when a player has been online since the last one, the newest 12 kept and at most 50 GB in total. A backup covers the world folder; FTB's config docs show how to add config/, logs and ops.json through extra_files. The file's header warns that the pack's copy "may be overwritten on modpack update" and that a copy at world/serverconfig/ftbbackups3-server.json5 will not be, so make your changes there. For a backup right before an update, run /backup, an alias for /ftbbackups3 backup.

To restore, FTB's restore steps are: stop the server, rename the current world folder (for example to world_old), extract the backup you want, copy its world folder in as world and start again.

Before players join: Chunky and spark

Release 1.7.0 includes Chunky and spark on the server side. FTB describes Evolution 2's world generation as heavily customized around Tectonic and Terralith, and Chunky generates that terrain before anyone explores it, so the work is done before your group starts playing. From the console, with the commands from Chunky's wiki:

chunky spawn
chunky radius 1000
chunky start

chunky pause stops the job and saves its progress, and chunky continue picks it up again. Start small and raise the radius later.

If the server lags with players online, run spark profiler start, let it record during the slow moment, then spark profiler stop for a report link (spark's command docs). Keep that link and the log with any support question.

FAQ

How much RAM does an FTB Evolution 2 server need? FTB lists at least 6 GB and recommends 8 GB. Its installer writes that 8 GB as the Java heap (-Xmx8192M), and Java needs memory beyond the heap, so give the server more than 8 GB in total and add more for bigger groups and worlds.

Which Java version does FTB Evolution 2 need? Java 25, because Minecraft 26.1.2 requires it. FTB's installer downloads Java 25.0.2 into the server folder unless you pass -no-java. If your panel uses its own Java, set it to 25.

Where do I download the FTB Evolution 2 server files? From FTB's Server Files page: choose your operating system, FTB Evolution 2 and the release. For 1.7.0 the installer is serverinstall_135_100594. Keep that name, because the installer reads the pack and release from it.

Is FTB Evolution 2 an update for my FTB Evolution world? No, FTB lists them as two packs. FTB Evolution (pack 125, from 31 October 2024) is at 1.46.0 of 30 October 2026 on Minecraft 1.21.1, NeoForge 21.1.262 and Java 21. Evolution 2 (pack 135) is on 26.1.2. Start Evolution 2 as a new server in its own folder and keep the old one backed up.

Can I run an FTB Evolution 2 server on an Arm machine? Yes. The Evolution 2 server files page has an Arm download next to the Intel / AMD one, ending in /server/arm/linux, and FTB's installer releases include Linux, macOS and Windows builds for Arm.

Sources

All opened on 3 November 2026: