Installing and Migrating

This page shows how to install, update, or migrate a GTNH client installation.

For instructions about how to install or update servers, please see Server Setup.

Installing

Technic

1. Install the Technic launcher,
2. In the launcher, go to the Modpacks tab and enter "GT New Horizons" in the search box. Make sure the pack named "GT New Horizons" is selected in the results list.
3. Optionally, click the Modpack settings link in the upper-right to select a specific version and the installation path. By default, the latest stable release will be installed, but some servers may need a different version.
4. Click the Install button on the lower right to install the pack.
5. Go to the Launcher settings at the top-right corner, and the Java tab of that dialog. At least 4 GB of memory is recommended for GTNH. Make sure you are using an up to date, 64-bit Java 8 (!) version.

MultiMC

Recent builds

1. Intall MultiMC,
2. Add a new instance in MultiMC. Select the From Zip option on the left.
3. Import the ZIP archive of GTNH from http://downloads.gtnewhorizons.com/Multi_mc_downloads/

Curseforge Launcher

The Curseforge launcher is not recommended because:

• it usually is out-of-date,
• it constantly messes up recipes,
• its new license requirements on mods make things even worse.

Please do not use a Curseforge launcher for GTNH.

Upgrading

Technic

The releases are pushed to Technic at a slower rate, once they have completed testing. Sometimes a release can be pushed to Technic for testing. To see them, please refer to the Technic configuration window.

ATLauncher

1. Backup your GTNH instance. In ATLauncher, click on the Edit Instance drop-down and select Clone Instance. Click the Open Folder button for the new instance.
2. Delete the config, mods, scripts and resources (if it exist) folders from Java/instances/instance_name/.
3. Replace the deleted folders with the ones from the downloaded archive. They are contained in a .minecraft folder after unpacking. If you are on Mac or Linux, you may have to show hidden files for your OS.
4. Port over any customized config settings. Use your backup as a reference.
5. The questbook should be updated automatically. If it was not updated, you can either use the default load block, go to cheat mode and do /bq_admin default load to load quest book changes, or do bq_admin default load on a server.

MultiMC

1. Backup your GTNH instance. In MultiMC, Right Click on the instance and select Copy Instance. With the backup, you retain access to settings and configs that are later needed on the new version, also to screenshots and keybinds.
2. Delete the config, mods, scripts and resources (if it exist) folders from instances/instance_name/.minecraft/.
3. Replace the deleted folders with the ones from the downloaded archive. They are contained in a .minecraft folder after unpacking. If you are on Mac or Linux, you may have to show hidden files for your OS.
4. Port over any customized config settings. Use your backup as a reference.
5. The questbook should be updated automatically. If it was not updated, you can either use the default load block, go to cheat mode and do /bq_admin default load to load quest book changes, or do bq_admin default load on a server.

Migrating to a different installer

This part describes how to migrate the installation to a new launcher.

Files to backup

1. If playing in single-player, backup your savesfolder.
2. The journeymap folder - if you use a different map/waypoint tool find its data.
3. The visualprospecting folder.
4. The TCNodeTrackerfolder
5. Any custom resources/resourcepacks you are using.
6. options.txt (also optionsof.txt if you use optifine).
7. Your screenshots folder, if you want to keep them
8. Any custom (client-side or not) mods such as InGameInfoXML and its configuration file.
9. Your backups in the backups folder (feel free to only grab 1 or 2 if you aren't deleting it)
10. Any custom changes to the config files or script files
11. Consider keeping the logs folder if you crash a lot