Run Multiple Terraria Worlds: Ports, Saves & Player Transfers

How to Run Multiple Terraria Worlds Safely

Terraria's official dedicated server runs one active world per process. It does not provide native seamless “world clustering,” cross-server portals, or a shared SQL inventory layer. To offer a main world, event world, and build world, run separate server processes with separate folders, world files, and TCP ports, then let players connect to the intended address and port.

A supported multi-world layout

The ports are examples. The official Terraria Wiki server reference documents TCP 7777 as the default, while the command-line parameter reference documents selecting a world, port, maximum players, password, and configuration file.

Keep each process isolated

• Give each server a unique TCP port and configuration file.
• Store each active world in a clearly named directory and never point two running processes at the same .wld.
• Use separate log and backup destinations so one instance cannot overwrite another's files.
• For tModLoader, keep the matching .wld and .twld together and preserve the exact mod list.
• For TShock, isolate its database and plugin data. Do not assume two processes can safely write the same database file.
• Allocate CPU and memory from observed combined load; two idle instances are different from two simultaneous boss events.

Player characters and inventories

Terraria commonly stores normal player characters on the player's device. A player can therefore select the same character before joining another compatible world, subject to the server's mode and administration rules. That is not transactional cross-server inventory synchronization: the character is not teleported live between processes, and server-side character systems can replace the normal client-character model.

Mixing vanilla, TShock server-side characters, and tModLoader is especially sensitive. A modded item may not exist in vanilla. A TShock server may enforce its own character state. Publish a clear rule for which character belongs on each instance, and test transfers with a disposable character before opening the network.

World switching without fake portals

The dependable method is a visible server list: publish each world name, address, port, version, server type, and reset policy. Players disconnect from one instance and join another. A website, Discord channel, or in-game message can show those details without pretending that an unsupported portal preserves inventory atomically.

Community plugins may advertise portal or transfer features, but compatibility changes with Terraria, TShock, and tModLoader releases. Before using one, find a current release for the exact server version, read open issues, back up every affected world and character store, and test disconnects during transfer. Do not expose a shared database to the public network or grant a plugin broader credentials than it needs.

Backup and update routine

1. Stop one instance at a time and wait for its save to complete.
2. Copy its world, configuration, extension data, and logs to an off-instance backup.
3. Update a cloned process first when TShock, tModLoader, or plugins are involved.
4. Join the cloned world and test save, restart, permissions, and player-character behavior.
5. Update production during a scheduled window and keep the old instance files for rollback.

Related Terraria guides

• Set up a Terraria dedicated server
• Update and roll back Terraria 1.4.5 safely
• Configure TShock administration
• Set up a tModLoader server
• Download and verify a world backup

Compare Supercraft Terraria plans if you need a managed instance for one of the worlds. Confirm the number of separate servers, ports, backups, and supported software before designing a multi-world setup.