Installing and Migrating

This page discusses how to install GTNH by using Technic or MultiMC launchers, and how to migrate GTNH from one launcher to another in singleplayer. Please refer to Server Setup if you want to host a server for multiplayer.

= Installing =

Technic

 * 1) Download, install and start the Technic launcher
 * 2) 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/or the installation path. By default, the latest recommended release will be installed, but some servers may use other versions.
 * 4) Click the Install button on the lower right to install the pack.
 * 5) Before launching the game, you may need to adjust your Java settings. Go to the Launcher settings at the top right corner, and the Java tab of that dialog. At least 4 GB is recommended. Make sure you are using an up to date, 64-bit Java 8 (!) version.
 * 6) Click Play to start the game.

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
Recommended releases are pushed to Technic at a slower rate, once they have completed testing. Sometimes releases can be pushed to Technic for testing, to see those look in the Technic configuration window.

ATLauncher
For the client:


 * 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 ,  ,   and   (if it exist) folders from.
 * 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   to load quest book changes, or do   on a server.

MultiMC
For the client:


 * 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 ,  ,   and   (if it exist) folders from.
 * 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   to load quest book changes, or do   on a server.

For the server:
 * 1) Download a new server version of GTNH with.
 * 2) Backup your server folder.
 * 3) Delete the ,  ,   and   folders from your server folder.
 * 4) Replace the deleted folders with the ones from the downloaded archive.
 * 5) Port over any customized config settings. Use your backup as a reference.

= Migrating to a different installer = This guide will go over migrating your installation to a new launcher.

Files to backup

 * 1) If playing in single-player, backup your  folder.
 * 2) The   folder - if you use a different map/waypoint tool find its data.
 * 3) The  folder.
 * 4) The  folder
 * 5) Any custom resources/resourcepacks you are using.
 * 6)   (also   if you use optifine).
 * 7) Your   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   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