Before renting an FTB server, choose the pack and release your group will play. That gives you something specific to check against the hosting plan: server files, Java version, memory guidance and an installation route.
Our modded Minecraft server hosting includes a panel installer for the CurseForge and Modrinth packs it lists, plus SFTP uploads for server files. Check whether your exact FTB release is listed before ordering. A pack appearing on FTB's website does not confirm that its newest version is already in our installer.
Choose the pack and release first
Start with the pack's official FTB page. Record its full name, release number, Minecraft version and modloader. Keep that information with your server notes so everyone installs the same release.
For an existing world, record the version currently running before choosing an update. Read the destination release's changelog for removed mods, configuration changes and migration instructions. Avoid changing the pack, loader and custom mods together: keeping changes separate makes problems easier to trace.
Treat published memory requirements as guidance for that pack. A table based only on mod counts or player counts is not enough to choose a plan. If the pack does not publish a server requirement, ask about the specific release and your existing world before paying.
Use StoneBlock 4 as a version-specific example
On 12 October 2026, FTB's official server-files page lists StoneBlock 4 1.23.0, release ID 100554. Its version manifest specifies Minecraft 1.21.1, NeoForge 21.1.250 and a Java 21 runtime. These details apply to this release, not to every FTB pack.
The official pack page lists a 6 GB minimum and 8 GB recommendation. Those figures do not promise capacity for a particular number of players. It also requires enable-command-block=true; check that setting when preparing the server.
The 1.23.0 changelog includes fixes involving machine outputs and Ars Nouveau breaking controller blocks. Use the matching official server installer, rather than carrying over a download or mod count recorded for 1.22.0. Keep client and server on the selected release together.
Obtain and install the matching server files
FTB's server installation guide directs you to select the operating system, pack and release before downloading its installer. Preserve the installer filename because it identifies the pack and version.
Install into an empty working folder. FTB says its installer downloads the required Java runtime and generates run.bat for Windows or run.sh for Linux and macOS. Use those generated instructions as your reference instead of substituting a generic forge-server.jar command.
On a hosted server, check how the panel starts that installation. For a pack absent from the panel's index, prepare its server distribution and use SFTP, keeping its folder structure. Ask support to confirm the runtime and startup configuration before uploading an existing world. Read any licence prompts before deciding whether to accept them.
Set memory from the pack's instructions
FTB's memory allocation guide explains that -Xmx controls maximum Java heap memory and -Xms controls its initial allocation. Editing those values does not increase the memory allowance purchased from a hosting provider.
Check the generated launch configuration and the plan's limit together. Keep the pack's other startup arguments unless its documentation or a specific diagnosis calls for a change. An argument copied from an unrelated pack can point to the wrong loader files or runtime.
After setup, inspect the console and memory usage while your group uses the world. Save useful logs before changing settings. Investigate recurring errors instead of treating a fixed restart schedule as a repair. Make one adjustment at a time and check its effect.
Verify a connection before inviting everyone
Start with an unmodified client installation of the selected pack release. Wait for server startup to complete, then use the address and port shown for your service. Check that the intended world loads before sharing the connection details.
If a connection fails, compare the pack release, Minecraft version and loader first. Keep the full error message and the corresponding server log. Avoid removing mods at random or assuming that every client addition is compatible.
Once that baseline works, introduce any optional client changes separately. For an existing world, check the features your group relies on, such as quests, machines and inventories, before reopening normal play. These are acceptance checks, not a promise that every update preserves every feature.
Back up before updating and prepare a rollback
Before an update, stop the server cleanly and preserve a dated copy of the world, configuration, scripts and current server distribution. Keep a separate copy outside the working server folder. Check that the archive opens and contains the files you expect.
If your pack includes FTB Backups 3, inspect its backup configuration. Its extra-files setting controls additions beyond the world folder, so a world backup should not be assumed to contain the complete server installation.
Test the new release against a copy of the world before replacing the working server. For rollback, retain both the earlier software and its matching pre-update save. FTB's server restore instructions start with stopping the server and preserving the current world separately before restoring the backup. Do not make an upgraded save your only recovery copy.
Check the order and support arrangements
Compare the selected region, hardware line, RAM, storage and monthly price in the order summary. Space-Node game server plans use shared CPU, including Premium. A RAM tier is not a guarantee of performance for a particular pack or group.
On 12 October 2026, the modpack page shows its Netherlands Premium 8 GB selection at EUR 13.99 per month. This is a dated price example, not a sizing recommendation for all FTB packs. Recheck your own selection before payment; checkout bills in EUR.
Support is available daily from 08:00 to 20:00 UTC. For setup questions, provide the official pack link, exact release, intended region and any startup error. Confirm the installation route and configuration you need before ordering, especially when the release is absent from the panel's pack list.