Skip to Content

GregTech: New Horizons - Initial Setup

Get your GT:NH server up and running in minutes.

Step 1: Access Your Server

After your purchase is complete:

  1. Log in to the Reizor Panel 
  2. Navigate to your GT:NH server
  3. Click on “Console” to view server status

Step 2: Server Configuration

Basic Settings

The server comes pre-configured with optimal settings for GT:NH, but you can customize:

  1. Go to Files > server.properties
  2. Adjust settings like:
    • max-players - Maximum player count
    • difficulty - Server difficulty (recommend Hard for GT:NH)
    • view-distance - Render distance (8-12 recommended)

Step 3: Upload an Existing World (Optional)

If you have an existing GT:NH world you’d like to transfer to your new server, follow the instructions below based on your world folder size.

Before uploading a world, make sure your server is stopped. You can stop it from the Console tab in the panel.

For Worlds Under 1GB

If your world folder is under 1GB, you can use the panel’s file manager:

  1. Prepare your world folder

    • Locate your world folder on your local computer (usually named world or your custom world name)
    • Compress the entire world folder into a .zip file
    • Make sure the world folder itself is at the root of the zip (not inside another folder)
  2. Delete the default world

    • Go to the Files tab in the panel
    • Find the existing world folder (or whatever name is in your server.properties)
    • Click the ellipses (…) next to it and select Delete
    • Confirm the deletion
  3. Upload your world

    • In the Files tab, click the Upload button
    • Drag your world zip file or click to browse for it
    • Wait for the upload to complete (this may take several minutes depending on size)
  4. Extract the world

    • Once uploaded, find your zip file in the file list
    • Click the ellipses (…) next to the zip file
    • Select Unarchive
    • Wait for the extraction to complete
    • After extraction, you can delete the zip file to free up space
  5. Verify the world name

    • Open server.properties and check the level-name setting
    • Make sure it matches your world folder name exactly
    • If they don’t match, either rename your world folder or update the level-name in server.properties

For Worlds Over 1GB

For larger worlds, you’ll need to use an SFTP client like FileZilla:

  1. Get your SFTP credentials

    • Go to the Settings tab in the panel
    • Look for the SFTP Details section
    • Note down the following:
      • Server Address (Host)
      • Username
      • Port (usually 2022)
    • Your password is the same as your panel password
  2. Download and install FileZilla

  3. Connect to your server

    • In FileZilla, enter your credentials in the top bar:
      • Host: Your SFTP server address (e.g., sftp://node1.reizorhosting.com)
      • Username: Your SFTP username
      • Password: Your panel password
      • Port: 2022 (or the port shown in your SFTP details)
    • Click Quickconnect
    • If prompted about an unknown host key, verify the fingerprint and click OK
  4. Navigate to your server files

    • In the right pane (Remote site), you should see your server files
    • Navigate to the root directory (/home/container/)
  5. Delete the default world

    • Find the existing world folder on the remote side
    • Right-click it and select Delete
    • Confirm the deletion
  6. Upload your world folder

    • In the left pane (Local site), navigate to where your world folder is located
    • Select your entire world folder
    • Right-click and select Upload, or drag it to the right pane
    • Wait for the upload to complete (this may take a while for large worlds)

FileZilla will show upload progress at the bottom. Large worlds may take 30+ minutes to upload depending on your internet speed.

  1. Verify the upload
    • Once complete, check the remote pane to ensure all files transferred successfully
    • Verify the world name matches the level-name in your server.properties

Troubleshooting World Uploads

Upload keeps failing:

  • Check your internet connection
  • Try compressing the world into smaller chunks (for web uploads)
  • Use SFTP for large worlds instead of the web uploader

Server won’t start after uploading world:

  • Verify the world folder name matches level-name in server.properties
  • Check that all files extracted/uploaded correctly
  • Look at the console for error messages
  • Ensure the world was created with a compatible GT:NH version

SFTP connection refused:

  • Verify you’re using the correct port (usually 2022, not 22)
  • Make sure your server is active (not suspended)
  • Check that you’re using the correct SFTP address from the Settings tab
  • Ensure you’re using SFTP as the protocol

Step 4: Configure Server Utilities

Backups via Server Utilities

Server Utilities provides its own backup system on top of our panel. You are free to use this, but keep in mind it will contribute to your server’s disk space usage, and backups made via Server Utilities are not backed up via panel backups.

To configure backups, head over to serverutilities/serverutilities.cfg in the Files tab in the panel, and look under the backups category.

There’s a few things you can configure here, but we’ll touch on the most important ones:

  • backup_timer: This is the time, in hours, between backups.
    • 0.25 = Four times per hour
    • 0.5 = Twice per hour
    • 1 = Once per hour
    • 2 = Once every two hours
    • 3 = Once every 3 hours
  • backups_to_keep: This is the number of backups that will be kept. The way Server Utilities handles this is when it attempts to save a new backup and it sees that there are already as many backups as you have configured to be the limit, it will delete the oldest backup and save the new backup.
  • enable_backups: This has to be enabled for Server Utilities’ backups system to be enabled. This is independent to the B:backup=true line under the commands section. If this is disabled, even though the command may be enabled, the backups system will not function.

Homes, Ranks, and More

Server Utilities provides the ability for players to set homes, the amount of which is configurable. To configure homes beyond the default settings, follow the below guide.

Enable the /home command

In serverutilities/serverutilities.cfg, enable the /home command under the commands section on the line that says B:home=true (or false)

Enable Ranks

In serverutilities/serverutilities.cfg, enable ranks under the ranks section by changing the line that says B:enabled=false to B:enabled=true.

Configure Ranks

Under serverutilities/server/ranks.txt, you’ll need to configure the permissions for the default player rank (and optionally for elevated permission levels such as operators and VIPs)

The configuration for homes is as follows:

serverutilities.homes.max: 100 # Max amount of homes serverutilities.homes.warmup: 0s # Warmup time after entering the command before you will teleport serverutilities.homes.cooldown: 0s # Cooldown time between /home commands serverutilities.homes.cross_dim: true # Allows cross-dimension /home teleports

Some more configurations you may want to do, depending on how you like to play:

serverutilities.claims.max_chunks: 1000 # Maximum amount of chunks a player can claim serverutilities.chunkloader.max_chunks: 500 # Maximum amount of chunks a player can force load serverutilities.back.infinite: true # Whether you can keep going back and forth serverutilities.back.respawn: true # Whether you can /back to your death point serverutilities.back.rtp: true # Whether you can /back after rtp'ing serverutilities.back.spawn: true # Whether you can /back after using /spawn serverutilities.back.tpa: true # Whether you can /back after using /tpa serverutilities.back.warmup: 0s # Warmup period for a /back teleport serverutilities.back.cooldown: 0s # Cooldown period between /back commands serverutilities.back.back: true # Whether you can /back from a /back teleport serverutilities.rtp.cooldown: 0s # /rtp cooldown serverutilities.rtp.warmup: 0s # /rtp warmup serverutilities.tpa.cooldown: 0s # /tpa cooldown serverutilities.tpa.warmup: 0s # /tpa warmup serverutilities.spawn.cooldown: 0s # /spawn cooldown serverutilities.spawn.warmup: 0s # /spawn warmup

For a list of all permissions, click here.

Step 5: Whitelist Players

By default, whitelisting is enabled. To whitelist players, run the following command

whitelist add PlayerName

Step 6: First Launch

  1. Click Start in the panel
  2. Connect using your server IP shown in the panel

Connection Issues?

  • Verify the server is Running (green status)
  • Check your IP matches the one in the panel
  • Ensure you’re using the correct modpack version
  • Check your firewall settings
  • If you still have issues, reach out to our support

Next Steps

Need Help?

Join our Discord  or contact support.

Last updated on