Upload a Terraria world and verify the server connection

Match world format and server software

~~CloudExa~~Check ~~help~~whether ~~guide.~~the destination runs vanilla Terraria, TShock or tModLoader and record its exact supported game version. These are different software environments. A modded world may depend on companion data and installed mods; uploading its vanilla world file alone does not guarantee that mod content survives. Test a duplicate with the matching software rather than converting the only copy.

On your own computer, identify the intended world through the game’s world selection and storage settings. Steam Cloud and local storage can hold different copies. Make a local copy using the supported game controls if needed, and close the game before collecting files so synchronisation and saving are finished.

Keep the world and recovery data together

Terraria’s main world file uses .wld. Preserve its corresponding backup files where available and any companion files required by your modded environment. Player character files are separate from the world; moving the world does not automatically move personal inventories or character progress. TShock server-side characters add another database-backed case that needs a separate consistent backup.

Stop the hosted server normally before changing its files. Download the existing hosted world and relevant configuration first, even if you believe it is unused. Keep the source world untouched outside the service. Compare upload size with the original and confirm that an archive extraction has not produced an extra nested directory.

Select the imported file explicitly

Upload the complete copied dataset into the destination’s configured world location through the file manager or SFTP. Preserve the filename and case. The vanilla dedicated-server configuration supports a world= path selecting an existing file; hosting startup settings or TShock arguments may control that selection instead. Check the actual active startup configuration before editing a sample file.

Point selection to the uploaded world and avoid automatic new-world generation during an import. A displayed world name is not always its disk filename. If startup asks you to create a world or logs a different selection, stop and correct the path. Do not overwrite your source copy or remove the hosted backup to make the import appear cleaner.

Use the assigned TCP game endpoint

Terraria’s documented default game port is TCP 7777, but a shared host can assign another number. Configure the server to use the TCP port allocated to your service and give players that exact address and port. Do not choose a neighbouring number or assume an example default belongs to your server.

Home-router port forwarding does not control a rented server’s network. If the assigned port cannot be reached after the game reports it is listening, send support the server identifier, endpoint and timestamp. Keep administrative interfaces and SFTP private. A DNS name alone does not remove the need to enter the correct port in the client.

Test the world before normal play resumes

Join with a compatible client and visit a familiar structure, chest and progression landmark. Verify the expected difficulty and world size. Test an ordinary player as well as a TShock administrator because bypass permissions can hide access restrictions. Save normally, stop, restart and reconnect to confirm persistence.

If the map is wrong, stop immediately and compare the active world path, software version and uploaded filenames. Restore the previous configuration and untouched world copy when necessary. Keep any failed conversion separately; do not open it repeatedly in different server types. Invite everyone back only after the owner confirms the right world is running.