GT New Horizons at a glance
| Type | tech modpack with GregTech as its backbone, maintained by the GTNH team |
|---|---|
| Minecraft version | 1.7.10 |
| Mod loader | Forge - the modpack browser sets the matching version itself |
| Java | two server packs: one for Java 8, one for Java 17 and newer |
| Version | 2.8.4 as the stable release, 2.9.0 in testing (as of October 2026) |
| Source | CurseForge - installable in the panel via the modpack browser; also the official download page and Technic |
| RAM per wiki | 6 GB plus 0.5 GB per extra player, from the UV tier plus 1 GB per player |
| World generator | level-type=RWG in server.properties |
| Recommended plan | plan L for small groups, plan XL for larger groups and the late game |
Published on
GT New Horizons server hosting
Prepaid from €2.99 / month, unlimited slots, no minimum term. The right plan is listed in the RAM table below.
Plans & pricesWhy GTNH needs a dedicated server
In most modpacks, a server is a convenience. In GT New Horizons, it is part of the game. Progression runs through clearly separated voltage tiers, and each tier needs machines that process resources for hours. If the world only runs while the host is playing, the whole production stops as soon as they go offline - and the group waits for them.
On a dedicated server, loaded areas keep running, everyone can join at their own time, and large shared projects are spread across several people. The developers also note that a separate server can improve the tick rate even when playing solo on the same machine. If you take GTNH seriously, plan the server from the start instead of moving later.
The official guide puts the hardware focus on single-core performance, because Minecraft on 1.7.10 hardly spreads its work across several cores. Many cores help little, one fast core helps a lot. Then there is storage: an early-game world takes about 1 to 2 GB, the pack files the same again, and each backup roughly the size of the world.
Java 8 or Java 17+: two server packs
In the panel, you install GTNH like the other packs via the modpack browser, which sets the Minecraft and Forge versions itself. If you set up the pack by hand or want to understand the Java question, it still helps to know: GTNH ships two editions for the server. The file ending in _Server.zip is for Java 8. The file with _Server_Java_17 in its name is for Java 17 and newer. The developers explicitly recommend the newer Java edition; the older one remains for special cases. What matters is that the server pack and the configured Java version match - otherwise, according to the official guide, the server won't start.
The Java 8 edition starts like a classic Forge server and runs with Java 8 set under Startup in the Docker Image field, as described in Change Java version. The edition for Java 17 and newer starts with its own start arguments from the bundled java9args.txt file. If you want to use it, contact support before setting it up.
For players, the choice is independent: each client may run on Java 8 or on Java 17 and newer, whichever edition the server uses. What has to match exactly is the GTNH version itself. A client on 2.8.4 can't join a server on 2.9.0.
Updates without losing the world
A GTNH update isn't a file swap you do on the side. The official guide describes a fixed procedure: first back up the complete server folder, then delete the config, libraries and mods folders, plus resources and scripts if present, and replace them with the versions from the new server pack. You then re-enter your own adjustments by hand - the wiki explicitly warns against simply copying the old config files back.
There is one exception: the JourneyMapServer folder under config. Restore it from the backup. If it is missing, the server creates a new ID for the map, and players lose their saved map data. The route via SFTP and the file manager is described in Create backups.
The pack brings its own backups via ServerUtilities, which are active by default. You set the interval and the number kept in serverutilities/serverutilities.cfg. Keep an eye on storage: according to the wiki, the save can get corrupted if it runs full.
Which plan for GT New Horizons?
The thresholds below apply to this pack - a light Vanilla+ pack and a kitchen-sink pack with a hundred running machines behave completely differently. You can upgrade at any time without losing data and only pay the difference.
| Group | Plan | RAM | Price | Why | Order |
|---|---|---|---|---|---|
| 1-3 players, early game | Plan L | 8 GB | €11.99 / month | Per the wiki, 6 GB base plus 0.5 GB per extra player - 8 GB cover that with headroom. | Order L |
| 4-10 players | Plan XL | 16 GB | €21.99 / month | More players and more machine chains running in parallel - 16 GB leave room to grow. | Order XL |
| From the UV tier | Plan XL | 16 GB | €21.99 / month | In the late game, the wiki counts 1 GB per extra player, plus large permanently loaded setups. | Order XL |
| Solo | Plan L | 8 GB | €11.99 / month | Even alone, the official minimum is 6 GB - the 8 GB tier is the starting point. | Order L |
The memory is taken proportionally from the plan via -XX:MaxRAMPercentage - you don't need to maintain a fixed -Xmx. The basics are covered in the RAM guide.
Setting up GT New Horizons on the server
- Stop the server in the web interface. Setup and version changes only apply while the server is stopped.
- Search for GT New Horizons in the panel's modpack browser and install the version you want. The installer sets Minecraft 1.7.10 and the matching Forge version itself.
- Under Startup, check in the Docker Image field that the Java version matches the installed edition.
- Check
level-type=RWGinserver.propertiesbefore the world is generated for the first time. - Start the server. The first start takes several minutes because Forge registers the pack's mods - don't cancel it.
- Wait for
Donein the console. Players install exactly the same GTNH version and connect via IP and port.
Common pitfalls with GT New Horizons
Server doesn't start
Cause: Server pack and Java version don't match - for example the Java 17 edition on Java 8 or the other way round.
Fix: Choose the edition for the configured Java version. Other start errors are covered in Server not starting.
Players are rejected when connecting
Cause: Client and server run different GTNH versions. The version has to match exactly.
Fix: Bring everyone to the same version. The players' Java version doesn't matter here. Other causes in Fix connection errors.
After an update, the players' map is empty
Cause: The JourneyMapServer folder wasn't taken over from the backup during the update. The server created a new map ID.
Fix: Put the folder from the backup back into config/ and restart the server.
Storage runs full
Cause: The built-in ServerUtilities backups pile up, each roughly the size of the world.
Fix: Lower the number of backups kept in serverutilities/serverutilities.cfg, and download and remove old backups.