tModLoader v1.4.4

资源内容介绍

tModLoader v1.4.4 是一个广泛使用的模组加载器，专门用于Terraria这款游戏。它允许玩家安装各种模组，这些模组可以为游戏添加新的物品、敌人、机制甚至是改变游戏的原有特性。在本文中，我们将详细探讨与tModLoader v1.4.4版本相关的各种知识点。要了解tModLoader的概念，我们需要认识到它不是一个独立的游戏，而是一个第三方工具，它必须在已经安装好的Terraria游戏基础上才能运行。通过tModLoader安装的模组可以大大增强游戏的可玩性和重复可玩性。例如，模组可以添加新的建筑和装饰，也可以添加复杂的机械装置、新的游戏机制，甚至可以创造出全新的世界。这些改动不仅限于表面的游戏体验，还可以改变核心游戏的平衡性和玩法。在tModLoader的版本历史中，v1.4.4是一个重要的更新。根据提供的描述，这一版本号为1.4.4-refs/heads/stable Version Update: v2025.04.3.0，显示出该版本属于稳定分支的更新。这意味着相对于之前可能存在的测试版和不稳定版本，v1.4.4版本具有更高的稳定性和可靠性。玩家可以预期游戏在运行时出现的错误将被大大减少，游戏体验更加顺畅。从文件名称列表中，我们可以看到有关该工具的一些执行文件和配置文件。例如，start-tModLoader.bat和start-tModLoaderServer.bat文件，分别用于在Windows操作系统的环境下启动tModLoader和启动tModLoader服务器。这表明tModLoader不仅可以用于个人游戏体验，还可以用于多人游戏，让玩家们共享模组体验。此外，start-tModLoader-FamilyShare.bat文件的存在表明，tModLoader还支持Steam的家族共享功能，这为想要体验同一套游戏模组的玩家提供了一个便利的渠道。另一个重要文件是tModPorter.dll.config，它是一个配置文件，用于设置tModPorter。tModPorter是一个独立的工具，专门用于从TShock模组向tModLoader模组迁移。通过这个工具，旧有的TShock模组作者和玩家可以平滑过渡到tModLoader平台。tModLoader.dll文件则是tModLoader的主要执行文件，它包含了加载和运行模组所需的所有代码。而tModLoader.deps.json、tModLoader.runtimeconfig.json以及tModLoader.runtimeconfig.dev.json文件则包含了与运行时环境相关的信息，它们决定了tModLoader如何在不同的环境下运行，比如开发环境和生产环境。.tModLoader.pdb文件是符号文件，它包含了调试信息，对开发者来说，在进行程序调试或者错误追踪时非常有用。这些符号文件允许开发者通过调试器更清晰地了解程序的运行情况，对于定位程序中的错误和性能瓶颈至关重要。start-tModLoaderServer.sh文件则是一个shell脚本，它是用于Linux操作系统中，启动tModLoader服务器的脚本。这个文件的存在表明tModLoader不仅支持Windows平台，同时也提供了对Linux平台的支持，让更多的用户能够使用tModLoader。总结而言，tModLoader v1.4.4是一个强大的模组加载器，它通过增加游戏模组来拓展Terraria的游戏体验。它在不同操作系统上都提供了良好的支持，无论是在个人电脑还是服务器上，都能保证玩家能够享受到高品质的游戏体验。通过它，玩家们可以在原有的游戏基础上创造出全新的游戏内容，极大地增加了游戏的重复可玩性。

# Dedicated Server UtilsThis 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)](#using-the-docker-container)[Management Script Installation](#using-the-management-script)[Installing Mods](#mod-installation)[Example Folder Structure](#folder-structure)[Server Configuration](#server-configuration)[Updating the Management Script](#updating-the-management-script)## 1.4.4 MigrationThe 1.4.4 script is a **backwards-incompatible update** that introduces a new [folder structure](#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 ContainerTo install and run the container:1. Install `docker` from your package manager or [Docker's Official Page](https://docs.docker.com/engine/install/) * **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](https://github.com/tModLoader/tModLoader/tree/1.4.4/patches/tModLoader/Terraria/release_extras/DedicatedServerUtils/docker-compose.yml) and the [Dockerfile](https://github.com/tModLoader/tModLoader/tree/1.4.4/patches/tModLoader/Terraria/release_extras/DedicatedServerUtils/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](#folder-structure) in that directory4. 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](https://docs.docker.com/compose/compose-file/build/#args) * Uncomment the `restart` line to have the server automatically restart if it crashes5. Run `docker compose up` * If [serverconfig.txt](#server-configuration) 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### UpdatingTo 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 ScriptThe `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](https://developer.valvesoftware.com/wiki/SteamCMD). If your distribution cannot install SteamCMD the standard way, download it manually and pass in `steamcmdpath` to the management script2. 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#### GitHub1. 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 ModsMods 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**. ### LaunchingTo 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 StructureBoth 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.txtBecause 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 Workshop2. Go to Mod Packs3. Click `Save Enabled as New Mod Pack`4. Click `Open Mod Pack Folder`5. Enter the folder with the name of your modpack6. Make a `Mods` folder and copy `install.txt` and `enabled.json` file into it7. 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 ConfigurationIf you want to run tModLoader without needing any input on startup (such as from an init system), copy the example [serverconfig.txt](https://github.com/tModLoader/tModLoader/tree/1.4.4/patches/tModLoader/Terraria/release_extras/serverconfig.txt) and change the settings how you like. Key options are defined below, and other options can be found [on the Terraria wiki](https://terraria.wiki.gg/wiki/Server#Server_config_file)* `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/Wor