What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To host TerraFirmaGreg-Modern, download the official server pack from the project’s GitHub releases, run it with Java 17 or newer, and give the instance enough memory for your player count and automation load. You can launch the supplied script on an always-on computer or deploy the pack with Docker. Start with a stable release, keep the server and clients on exactly the same version, expose TCP 25565, and back up the world before every update.
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 TerraFirmaGreg is and what the server runs
TerraFirmaGreg-Modern is a Minecraft 1.20.1 Forge modpack that combines TerraFirmaCraft’s survival systems with GregTech’s technology progression. CurseForge describes it as “TerraFirmaGreg-Modern is a deep survival and tech modpack for Minecraft 1.20.1, seamlessly fusing together TerraFirmaCraft and GregTech.” The project page reported 1,694,730 downloads and an October 6, 2026 update when that page was checked.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
A server installation is not the same thing as copying a client profile. The project publishes a separate server pack containing the scripts, Forge-related files and configuration needed to run a dedicated instance. Extract that pack into its own directory; do not mix it with an existing client installation or another server’s files.
Requirements before you install
Player and host requirements
- Every player needs Minecraft Java Edition for PC and a TerraFirmaGreg client installation that exactly matches the server release.
- The host needs an always-on computer, virtual machine or managed server with adequate CPU, memory, storage and a stable network connection.
- Use Java 17 or newer. TerraFirmaGreg documentation lists Java 17+ for Forge and Pakku, and the 1.20.1 Forge build used by the reviewed server guide is tied to Java 17.
- Reserve fast, reliable storage for the world, logs and backups. Automation-heavy worlds generate more chunks and files over time than a short test world.
- If players connect from outside your home network, you need router port forwarding and a host firewall rule, or a hosting service that handles those layers.
Check Java before starting
On the machine that will run the server, execute:
java -versionThe output should show a 17-or-newer runtime. If the command is missing or reports an older major version, install a supported 64-bit Java runtime and make sure the server process uses that installation rather than an older copy elsewhere on the system.
#1 Best Overall
Choose a release and obtain the correct server pack
Stable versus pre-release
Choose a full, stable release when you value reliability over testing new changes. The release information used for this guide identified 0.13.10 as the latest full release discussed, while 0.13.11 and 0.13.12 were listed as pre-releases at that time. Release status changes quickly, so check the current TerraFirmaGreg GitHub release page immediately before downloading. Record the exact version number you select; everyone joining must use it.
Download and extract
- Open the TerraFirmaGreg project’s official GitHub releases through the project wiki or its CurseForge page.
- Download the server-pack archive for the chosen release, not only the client modpack archive.
- Create a new, dedicated folder such as
terrafirmagreg-serveron a drive with enough free space. - Extract every file from the archive into that folder. Keep the supplied directory structure intact.
- Do not extract over an older installation. The official wiki specifically recommends placing new server-pack files in a separate folder from an existing instance.
The “server file” is therefore the extracted server-pack directory, not one universal file you obtain separately. It should contain the project’s start script and the files Forge needs. A first launch may create additional runtime files and the world itself.
Method 1: run the supplied server script
Manual startup gives you the clearest access to JVM flags, logs and files. It is appropriate when you control a spare PC, dedicated machine or virtual machine and are comfortable maintaining Java and backups.
Windows
- Open the extracted server folder in File Explorer.
- Run the Windows start script supplied by the pack (normally the
.batlauncher included in that release). - Allow the first run to finish. The guide reviewed for this article says the initial launch installs Forge and then starts the world; it can take substantially longer than later starts.
- Read the console output. If the process stops for an EULA prompt or another required setting, follow the message, save the change, and launch the script again.
- Leave the console window running while the server is online. Use the server’s normal stop command before shutting down the host so world data is flushed safely.
Linux or another Unix-like host
- Change to the extracted directory, for example:
cd /path/to/terrafirmagreg-server. - Make the supplied launcher executable if necessary:
chmod +x start.sh. - Start it with
./start.sh(use the exact filename included in your release). - Watch the first-run console until Forge has completed installation and the server reaches its ready state.
- For a remote machine, run the process inside a service manager or terminal multiplexer so an SSH disconnect does not terminate it. Configure automatic restarts only after you have confirmed that a clean stop and backup procedure works.
The reviewed Linux script defaults to approximately 6 GB of allocated memory. Inspect the script’s JVM arguments before a large deployment and adjust them to match your available RAM. Do not allocate all physical memory: the operating system, Java overhead and other services still need headroom.
Method 2: deploy with Docker
Docker makes the installation repeatable and keeps the changing server data separate from the container definition. The reviewed TerraFirmaGreg compose route uses the itzg/minecraft-server image, Minecraft 1.20.1, Forge 47.4.13, persistent ./data and ./backups directories, and an 8 GB memory setting.
Prepare the compose directory
- Install Docker Engine and the Docker Compose plugin on the host.
- Create an empty directory for this instance and change into it.
- Place the compose file supplied or documented for your selected TerraFirmaGreg release in that directory. Keep release-specific filenames and environment values exactly as published; they can change between releases.
- Confirm that the configuration identifies Minecraft
1.20.1, the Forge version required by that release (the reviewed file used47.4.13), and an 8 GB memory allocation unless you have deliberately sized it differently. - Ensure the compose file mounts persistent host directories for
./dataand./backups. Without those mounts, destroying or recreating the container can remove the world and backups stored only inside it.
Start and inspect the container
docker compose up -d
docker compose logs -fRun the first command from the directory containing the compose file. The second follows startup logs so you can see Forge installation, configuration errors and the point at which the server is ready. Stop it with:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsdocker compose downStopping the container is different from deleting its persistent directories. Keep ./data and ./backups when recreating the container, and back them up to another disk or host as part of your normal schedule.
Verify the image and release values
Container images, Forge builds and release filenames are updated independently. Before deploying, compare the compose file with the current project release rather than blindly reusing an older example. A mismatch can produce a server that starts but rejects every client, or fails during Forge installation.
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.
Configure networking and ports
Minecraft connection port
The standard Minecraft server port is TCP 25565. The reviewed Docker configuration maps that port. Open it in the host firewall and, for a home connection, forward TCP 25565 on the router to the server’s local IP address. Give the host a reserved DHCP lease or static address so the forwarding rule does not break after a reboot.
Simple Voice Chat
The reviewed configuration also maps UDP 24454 for Simple Voice Chat. Open and forward that UDP port only when the server and the installed modpack configuration use voice chat. A voice-chat port does not replace the Minecraft TCP port; they serve different traffic.
Recommended Free Tools
Test from outside the LAN
- Join locally first, using the host’s local address, to separate server problems from router problems.
- Test from a different network, such as a phone hotspot. Some routers do not support hairpin connections, so a successful test from inside the same LAN is not proof that outside players can connect.
- If external access fails, check the host firewall, router forwarding target, changing public IP address, carrier-grade NAT and whether the server is actually listening on the expected port.
How much RAM and CPU TerraFirmaGreg needs
There is no single guaranteed RAM number for every TerraFirmaGreg world. Reported configurations range from roughly 6 GB in the reviewed Linux launcher to 8 GB in the Docker setup; hosting pages cited by the guide advertise 8–12 GB. Those figures are configuration recommendations, not controlled performance benchmarks.
| Workload | Practical starting point | What to watch |
|---|---|---|
| Small private world and a few players | About 8 GB, subject to the launcher and available system memory | Heap occupancy, tick time and chunk-loading pauses |
| Several players, expanding bases or early automation | More than the small-world baseline may be necessary | Long garbage-collection pauses, delayed block updates and rising heap use |
| Large factories, Create contraptions or many loaded chunks | Budget additional RAM and CPU headroom rather than assuming the baseline is sufficient | Persistent lag while machines run, overloaded CPU cores and slow saves |
Increase memory only when monitoring shows memory pressure and the host has room. More allocated RAM cannot compensate for a saturated CPU, excessive chunk loading, a broken configuration or a poor network path. Keep the Java process and operating system from competing for the last available gigabytes.
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"!
Make client and server versions identical
Every player must install the same TerraFirmaGreg release, Minecraft version, Forge build and mod set as the server. The official wiki states that players must use the same version and notes that apparent mod mismatches often mean a client update did not complete correctly.
- Write the server release number in your community’s connection instructions.
- After an update, close and reopen the launcher so it completes downloads instead of reusing a partially updated profile.
- Do not add or remove a mod on one side as an experiment while diagnosing a connection failure; first return both installations to the published pack.
- Compare the server log’s rejection message with the client’s installed profile. A missing mod, different Forge build or different Minecraft version can all appear as a generic handshake failure.
Back up and update without losing the world
Before every update
- Announce downtime and stop the server cleanly.
- Copy the complete world data to a separate location. The official wiki specifically calls out the
savesdirectory and, when present, thebackupsdirectory. - Copy server-specific files such as the whitelist and any other settings you have changed. Keep the backup outside the installation folder so replacing that folder cannot remove both copies.
- Read the release notes for changes to mods, configuration or migration steps.
Install the new pack beside the old one
- Extract the new server pack into a new, empty directory rather than overwriting the old instance.
- Copy the backed-up
saves, optionalbackupsand server-specific files into the corresponding locations in the new directory. - Start the new instance with no players connected. Allow migrations and first-run generation to finish.
- Check the console for errors, join as an operator, inspect a few important areas and verify that machines, inventories and permissions are intact.
- Keep the old installation untouched until the new one has been tested. Delete it only after you have a separate, known-good backup.
For Docker, the same principle applies: stop the old container, back up the mounted data and backup directories, update the compose image or release values, then boot the replacement and inspect logs before reconnecting players.
Compare the three hosting approaches
| Approach | Upfront and recurring cost | Control and maintenance | Capacity and networking | Backups, uptime and support |
|---|---|---|---|---|
| Manual self-hosting | No hosting fee if you already own suitable hardware; electricity, storage and internet service are ongoing costs. | Maximum control over files, Java arguments, Forge and launch scripts. You perform installations, updates, monitoring and recovery. | Limited by your machine’s CPU/RAM and home upload speed. You handle firewall rules and port forwarding. | You design and test backups. Uptime depends on power, hardware and your willingness to keep the host online. Support is self-service. |
| Docker on your own machine | Same hardware and electricity costs as self-hosting, plus no separate game-hosting fee. | Repeatable deployment, explicit data mounts and easier rollback between container definitions. You still maintain Docker, the host and the pack. | Uses the host’s CPU/RAM and network. Port forwarding and firewall work remain your responsibility. | The compose layout makes persistent data and backup directories clear, but you must copy those directories somewhere safe. Uptime is still tied to your machine. |
| Managed hosting | Usually a recurring monthly charge; current price, billing term, location and included storage vary by provider and plan. | The panel may offer one-click modpack installation and scheduled tasks, but you have less access to the underlying JVM and filesystem than with your own host. | Plans differ in CPU, RAM, storage and player limits. The provider normally handles public networking, while you confirm that the advertised TerraFirmaGreg version and Java/Forge build are supported. | Potential advantages are datacenter uptime, support and automated backups. Verify backup frequency, retention, restore process and support scope before paying; these limits are not uniform. |
A managed TerraFirmaGreg option advertised in a 2026 guide listed an 8 GB requirement, but plan details, pricing, locations and backup limits can change. Treat any one-click listing as a convenience, not proof that every release is supported. Ask which Minecraft and Forge versions are installed, whether you can download your files, and how a restore is performed.
Troubleshoot the failures that matter most
The server exits immediately
- Run
java -versionand confirm Java 17 or newer. - Launch from a terminal or inspect the container logs so the actual Forge error is visible.
- Check that you extracted the server pack completely and did not run a client-only archive.
- Undo the last JVM-flag change and verify that the configured memory is available on the host.
Players get a mod or handshake mismatch
Confirm the exact release number, Minecraft 1.20.1, Forge build and completed client download. The official documentation says an incomplete client update commonly causes a mismatch even when the player believes the versions are identical.
The server is reachable locally but not remotely
Check TCP 25565 in both the operating-system firewall and router forwarding rule. Confirm the forwarding target still has the same local IP, test from a separate network, and investigate carrier-grade NAT if no inbound connection reaches the host. For voice chat, diagnose UDP 24454 separately.
Lag appears as the world grows
Observe heap use, tick time, CPU saturation and loaded-chunk counts before adding RAM. Reduce unnecessary chunk loading and simultaneous machine activity, then increase the allocation only if memory pressure remains and the host has capacity. A larger heap does not fix a CPU-bound factory.
An update appears to have erased progress
Stop the new instance immediately. Do not continue generating chunks over the affected data. Restore the last known-good saves copy into a separate test directory, review the release notes and repeat the migration with the old installation retained until validation succeeds.
Quick Recap
Operational checklist
- Stable release selected and exact version recorded.
- Official server pack extracted into a separate directory.
- Java 17 or newer confirmed.
- First launch completed and logs checked.
- Memory allocation reviewed against actual heap use and player workload.
- TCP 25565 forwarded and firewalled correctly.
- UDP 24454 opened only if Simple Voice Chat is enabled.
- Clients instructed to use the identical pack, Minecraft and Forge versions.
- World,
saves, optionalbackupsand whitelist copied before updates. - At least one backup stored outside the live server directory and periodically restored in a test location.
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.
