tModLoader v2025.10
A mod to make and play Terraria mods
Dedicated Server Utils

This directory contains utilities for a dedicated server on Linux or Docker

Installation Options

Currently ARM support does not exist for TML. While both the Docker container and the management script can install and update tModLoader and any mods, there are a few key differences. Docker isolates tModLoader from your host system, allowing for less manual management and increased security. The management script allows for direct access to your server and increased control as a result

Quick Links

Docker Installation (recommended)

Management Script Installation

Installing Mods

Example Folder Structure

Server Configuration

Updating the Management Script

1.4.4 Migration

The 1.4.4 script is a backwards-incompatible update that introduces a new folder structure that both the management script and the Docker container need to conform to. Additionally, the management script has moved from flags to commands for installing, updating and starting the server. Run ./manage-tModLoaderServer.sh -h to see a list of available commands and flags

Using The Docker Container

To install and run the container:

  1. Install docker from your package manager or Docker's Official Page
    • To check if Compose V2 is installed in this package, run docker compose version. If the command errors, your manager still uses V1 and will need to additionally install the docker-compose package. All commands below assume Compose V2 is installed, so if you have V1 replace any docker compose commands with docker-compose
  2. Download docker-compose.yml and the Dockerfile
  3. Create an empty folder named tModLoader. This is required. If you would like to install mods or use existing worlds then setup a proper folder structure in that directory
  4. Edit docker-compose.yml with your GID and UID. These can be found by running id, and generally default to 1000
    • You can also add the TML_VERSION arg to your compose file to set a specific tModLoader version. Read about how to set build arguments here
    • Uncomment the restart line to have the server automatically restart if it crashes
  5. Run docker compose up
    • If serverconfig.txt exists in the tModLoader directory add -d to the end to run without interactivity. To attach to the server console run docker attach tml. To detach from the console press Ctrl-P Ctrl-Q to avoid shutting down or Ctrl-C to detach and shutdown the server
    • This will create the Mods and Worlds directories if they don't already exist

Updating

To update, download the newest container and rebuild it using docker compose build to update tModLoader. Mods will be updated as well. If the container doesn't rebuild you can force rebuilding by running docker compose build --no-cache

Using The Management Script

The manage-tModLoaderServer.sh script can be used to install tModLoader either directly from the GitHub release or from SteamCMD. The script is made to run fully standalone, so just download it to your server and run it. No other files from the repo are needed

Installing tModLoader

SteamCMD (recommended)

  1. Ensure SteamCMD is installed and on your PATH. You can install SteamCMD from your package manager or Valve's Wiki. If your distribution cannot install SteamCMD the standard way, download it manually and pass in steamcmdpath to the management script
  2. Run ./manage-tModLoaderServer.sh install-tml --username your_steam_username and enter any password/2fa if necessary. tModLoader will install to the server directory in your installation folder

GitHub

  1. Run ./manage-tModLoaderServer.sh install-tml --github. This will install the latest GitHub release, which is the same version as released on Steam.
    • If you wish to use a specific/legacy tModLoader version from Github, provide either a tmlversion.txt file from a modpack or pass the --tml-version flag with a specified version, ex. v2022.06.96.4

Installing Mods

Mods will be automatically installed during the tModLoader installation step, but can also be installed separately by running ./manage-tModLoaderServer.sh install-mods. No mods will be installed if install.txt is missing, and no mods will be enabled if enabled.json is missing. You will need a Mods/enabled.json to contain all Mods that you want enabled.

Launching

To start a server, run ./manage-tModLoaderServer.sh start. Be sure to pass in --folder again if you used a custom location during installation

Updating

./manage-tModLoaderServer.sh install will update both TML and your mods. To update just mods, run the install-mods command. To only update TML, run the install-tml command

Folder Structure

Both the Docker and Management script use the same folder structure, so make sure it's setup properly before installing. Here is an example:

├── Mods
│   ├── localmod1.tmod
│   ├── localmod2.tmod
│   ├── enabled.json
│   └── install.txt
├── Worlds
│   ├── world1.twld
│   ├── world1.wld
│   ├── world2.twld
│   └── world2.wld
├── server
│   └── * contains tModLoader installation *
├── steamapps
│   └── * contains Steam workshop mods *
├── logs
│   └── * contains tModLoader logs *
├── manage-tModLoaderServer.sh
├── serverconfig.txt
└── tmlversion.txt

The server, steamapps and logs folders are created by the management script and do not need to be edited unless you want to clear your installation. manage-tModLoaderServer.sh is not necessary in the Docker version

Obtaining install.txt

Because the steam workshop does not use mod names to identify mods, you must create a modpack to install mods from the workshop. To get an install.txt file and its accompanying enabled.json

  1. Go to Workshop
  2. Go to Mod Packs
  3. Click Save Enabled as New Mod Pack
  4. Click Open Mod Pack Folder
  5. Enter the folder with the name of your modpack
  6. Make a Mods folder and copy install.txt and enabled.json file into it
  7. Run ./manage-tModLoaderServer.sh install-mods to install the mods on your server. This is not necessary if you are using Docker, it will be done automatically

Server Configuration

If you want to run tModLoader without needing any input on startup (such as from an init system), copy the example serverconfig.txt and change the settings how you like. Key options are defined below, and other options can be found on the Terraria wiki

  • worldname changes the default world name when creating a new world using autocreate You do not need to include .wld in your world name. This setting will not work with an existing world, see the world option for an existing world
  • world sets the exact path to an existing or new terraria world, ex. worldpath/to/your/world.wld. For Docker installations, the world path must follow /home/tml/.local/share/Terraria/tModLoader/Worlds/your_world.wld
  • autocreate=1 will enable autocreating, which creates a new world at your provided location if one does not already exist

Updating the Management Script

If an update for manage-tModLoaderServer.sh is available, a message will be printed letting you know one is available. It can be updated using ./manage-tModLoaderServer.sh update-script. An outdated script may contain bugs or lack features, so it is usually a good idea to update