Terraria Server Mods and Plugins – tShock Extensions

With tShock, you extend a Terraria server with plugins, permissions, regions, protection features, and administrative tools. What matters is not the number of extensions, but a controlled installation: choose the right version, place the DLL correctly, set permissions cleanly, and after every restart check whether the server, world, and player access work as expected.

Requirements for tShock Plugins

For Terraria plugins, you need a server that runs tShock. The normal vanilla server does not load tShock plugins from ServerPlugins/. If you are just planning your server, you can find the setup basics in the guide Rent a Terraria Server and Set Up Multiplayer. That guide covers the basics, while this guide focuses on extending the server with tShock.

Before every installation, check three things: the Terraria version, the tShock version, and the plugin version must match. You can find official information about tShock in the documentation at Documentation on github.com. For plugin downloads, the existing overview tShock Plugins is a useful starting point, provided you also pay attention to freshness, repository notes, and compatibility information.

Paid multi-game hosting like game-serverhosting is especially helpful if you need technical access, reproducible workflows, backups, and support for server operation and configuration. Plugins are still third-party server code: only install extensions whose origin and purpose you can understand.

tShock Plugin System

tShock is an alternative Terraria server with permission management, commands, and a plugin interface. Plugins are usually provided as .dll files and loaded server-side. Players normally do not need to install these plugins locally, as long as the plugin does not require a separate client modification.

The central folder is:

ServerPlugins/

This is where the plugin DLLs are stored. On startup, tShock loads the files and reports errors in the console or log. If a plugin is not compatible, dependencies are missing, or a configuration is invalid, the server may still start, but the plugin remains disabled or throws error messages.

Installation

1. Download the plugin DLL from tShock Plugins
2. Place it in the ServerPlugins/ folder
3. Restart the server
4. Reload with /reload (without restarting)

Only use /reload for changes that tShock and the relevant plugin can actually reread. For new DLLs, version changes, or unclear errors, a full restart is the cleaner check. It is best to schedule changes outside active playtime so you can read logs and roll back directly if problems occur.

Recommended Plugins

The following table lists typical extensions that are often used for management, protection, or gameplay. It is not a guarantee of current compatibility; always check the relevant plugin page and the supported tShock version before use.

Install only one or two plugins at first and test them. The more extensions are active at the same time, the harder troubleshooting becomes. The same basic principles apply to larger mod setups in other survival games: for Installing V Rising Mods or Installing Palworld Mods on Server and Client, version control is also more important than blindly adding lots of plugins.

Server-Side Characters (SSC)

SSC stores character data server-side. This can reduce cheating because players cannot simply bring arbitrary local character progress with them. At the same time, SSC significantly changes the game flow: inventory, progress, and starting equipment then depend on the server. So enable this feature deliberately and inform your community beforehand.

{
  "ServerSideCharacterConfig": {
    "Enabled": true,
    "ServerSideCharacterSave": 5,
    "StartingInventory": [
      {"netID": 3506, "prefix": 0, "stack": 1}
    ]
  }
}

Before making changes to SSC, create a backup of the world and relevant configuration files. Then check with a test player whether login, inventory, saving, and reconnecting work. If players suddenly miss items, first clarify whether local characters, SSC data, or permissions are affected.

Setting Up Regions

Regions protect buildings, spawn areas, or project zones. A protected spawn is typical, while regular players can build freely outside it.

/region define <name>           # Mark region
/region protect <name> true     # Protect region
/region allow <player> <name>  # Allow player
/region remove <name>           # Remove region
/region list                    # All regions

Use clear names like spawn, arena, or north_storage. Document important regions so other admins do not later have to guess why an area is protected. After creating one, you should test with a regular player account whether building, breaking, and interaction are actually blocked or allowed as planned.

Group System

The group system controls which commands players, moderators, and admins may execute. Use the principle here: only grant the permissions that are needed for the role.

/group add <name> <parent> <permissions> <chatcolor>
/user group <player> <group>

First create simple roles, for example player, moderator, and admin. After that, add individual permissions. Avoid blanket admin rights for regular players, even if it seems convenient in the short term. Commands for World Edit, regions, economy, or character data in particular can heavily change the server state.

Checking the Result

After every plugin change, you should perform at least this check: start the server, check the console for errors, connect with a test account, run a plugin command, test permissions with a normal player group, and then perform a second restart. Only when the plugin also loads stably after the restart is the installation truly complete.

If you have planned multiple changes, apply them one after another. That way, if an error occurs, you know which file or configuration was changed last.

Troubleshooting

If a plugin does not load, first check the file extension and the storage location. The DLL must be in the correct ServerPlugins/ folder, not in a subfolder or in the world directory. Then check whether the plugin version matches the tShock version.

If commands do not work, the plugin itself is often not broken; the permission is missing. Check the player's group and the permission names expected by the plugin. If regions do not protect anything, test with a player without admin rights; depending on the configuration, admins bypass protection rules more often than normal users.

If the server becomes unstable after installing a plugin, remove the most recently added DLLs again and restart. Work with backups before using SSC, economy systems, or World Edit features in production.

Checks, Limits, and a Safe Way Back

The guide “Terraria Server Mods and Plugins – tShock Extensions” applies to the server type described in the article and the version state visible at the time of checking. Menu names, available versions, mod or plugin compatibility, and required resources may differ after updates. So do not transfer any values to another game, loader, or server version without checking them first.

Before making changes to the world, savegame, configuration, or extensions, create a backup of the affected files. Then change only one related step and test it with the same client and server version you want to play with later.

A successful individual test is not a guarantee of performance or availability. World size, mods, plugins, player count, network route, and simultaneous load can change the result. Document the version, change, and test result so you can trace later differences.

FAQ

Do players also need the tShock plugins on the client?

Usually not. tShock plugins run server-side. Players connect with Terraria as usual, as long as the plugin does not require a separate client mod or special setup.

Can I install plugins without restarting the server?

Some changes can be reread with /reload. For new DLLs, updates, or troubleshooting, a full restart is more reliable because you can then see the complete loading process in the console.

Does SSC make sense for every Terraria server?

Not always. SSC is useful if you want to control progress and inventories server-side. For casual sessions with existing characters, it can be too restrictive.

Why do plugin commands work for me, but not for players?

It is usually due to group permissions. Admins often have broad permissions, regular players do not. So always test new plugins with an account that uses the same group as your community.

How many plugins should I install?

As few as possible and as many as necessary. Start with protection, administration, and the gameplay features you actually use. Every additional extension increases maintenance and troubleshooting effort.