GTO 0.6.0 Server Setup Guide

This article explains how to set up a GregTech Odyssey multiplayer server using the official server pack. The server pack comes with an installation script that automatically installs Forge and downloads all server mods, so there is no need to manually assemble the server files.

Reading Guide

1. Install Java
2. Extract the server
3. Install mods
4. Accept EULA
5. Select difficulty
6. Configure the server
7. Start

Pre-Server Preparation

Install Java 25 on the server (distributions such as Eclipse Temurin can be used). After installation, run the following command in the terminal and confirm that the displayed version is 25:

1. Go to Releases page to download GregTech-Odyssey-server.zip;

2. Fully extract the archive into an empty folder, hereinafter referred to as the “server directory”.

Note: Please ensure it is fully extracted. In the server directory, the gto-installer folder is missing, the installation script will not run.

Run the installation script in the server directory, and select the language as prompted:

The script will automatically install Forge 1.20.1-47.4.20 and download all server-side mods. When "Installation completed successfully" appears, the installation is finished.

Tip: The installation script can be run repeatedly. To force a recheck of all mods, delete packwiz.json and then run it again. Do not run multiple installation windows at the same time.

1. Run the startup script: on Windows run run.bat, on Linux / macOS execute bash run.sh;

2. The first launch will generate eula.txt and other files, then exit automatically;

3. Open eula.txt, change eula=false to eula=true and save.

Description: Setting eula to true means you agree to Minecraft End User License Agreement. The world has not yet been generated; please complete steps 5 and 6 before officially launching.

The server's difficulty is determined by config/gtocore-rules.txt in preset line, with the following options. For differences between difficulties, please refer toDifficulty Features Guide.

For example, set the difficulty to Normal:

Note: The world's difficulty is locked when first generated and cannot be changed afterward. Please decide before the official launch. If an existing world's difficulty does not match the difficulty in this file, the server will refuse to start and generate gtocore-rules.world.txt record the rules for that world.

Description: The difficulty settings on the player's client do not need to be adjusted manually. If they are inconsistent with the server, entering the server will automatically synchronize the server's rules and prompt the player to restart the game.

Memory: Edit the user_jvm_args.txt, via -Xmx parameter to set the maximum memory, for example:

Server properties: Edit server.properties, Common settings are as follows:

Run the startup script again. When the console shows Done indicates startup is complete; players can join via "server address:port". Common console commands are as follows:

Tip: When running via SSH on Linux, it is recommended to start the server in a screen or tmux session, so that the server does not shut down after the connection is disconnected. When shutting down the server, please use the stop command to avoid corrupting the save by directly terminating the process.

This modpack uses Open Parties and Claims to manage claims. To keep a player's claimed chunks loaded while they are offline, you can configure world/serverconfig/openpartiesandclaims-default-player-config.toml in:

Note：Enabling offline chunk force-loading will significantly increase server load. Please enable it carefully based on your server configuration.

Note: When updating, extract the new version into a new folder, then copy the data from the old server over. Do not extract the new version directly over the old server directory. After copying, keep the old server as-is; it can be used directly as a backup. Do not delete it until you have confirmed that the new server is running properly.

1. Install new version
2. Copy server data
3. Start and check

Following steps 2 and 3 in "1. Setting Up a Server", extract the new version serverinto a new folder, and run the installation script.Do not delete the old server, as it will be kept as a backup.

First, execute stop in the console of the old server to shut it down, then copy the following folders and files from the old server directory to the same locations in the new server directory. When encountering files with the same name, chooseOverwrite; items that do not exist in the old server can be skipped directly.

Must copy

Copy as needed

Note: Do not copy mods folder. New versions of mods include upgrades and additions/removals; copying the old mods folder will cause duplicate mods or version mismatches, preventing the server from starting. If you have added mods yourself, please place the corresponding jar files separately into the new server's mods folder.

Tip: If in server.properties you have modified level-name, please copy the world folder with the corresponding name.config/gtocore-rules.txt must match the world's difficulty, otherwise the server will refuse to start; copy the entire config to preserve this file.

Start the new server, confirm that the world loads normally and players can enter normally, then delete the old server as needed.

Note: The player's client must be updated to the same version as the server. For client update instructions, please refer toGTO 0.6.0 Installation and Update Guide.

If the issue persists, please provide feedback in the chat group, or go to Issues to submit an issue report and attach the server log or crash report.