Terraria
Rehearse a tModLoader update before changing your world
Record your Terraria modpack, protect world data and test joining and saving before updating your live tModLoader server.

A Terraria modpack update needs a test join and a save check before you invite your group back. Downloading the newest files can leave you with a working server process and a world your players cannot use.
Write down the working combination
Record the tModLoader release, enabled mods and their versions before changing the server. Ask a player who can join to record the same details from their client. Store that record alongside your backup. If the update fails, “the version from last week” will be much harder to reconstruct than an exact list.
Choose one person to make changes during the maintenance window. Other administrators can help test, but simultaneous edits make it difficult to identify which change fixed or broke the pack.
Keep the world and mod data together
The tModLoader project’s dedicated-server layout includes both .wld and .twld world files. Preserve the complete world set, mod configuration and enabled-mod list before testing. Keep a separate downloaded copy that the update process cannot overwrite.
Stop the live server normally before taking your final copy. Label the backup with the pack version and date, then check that you can open the archive and see the expected files. Do that before you begin the update, while you still have time to correct an incomplete backup.
Use a separate test destination
Ask support about a separate test instance if your plan does not provide one. Confirm its storage location and network allocation before copying data. Leave the live server’s files untouched while the test instance loads its own copy.
Restrict access to your testers. A second public instance can confuse players and create competing world histories. Give the test server a clear temporary name and tell testers that you will discard its progress after the rehearsal.
Use the current documentation for your installed release. The project’s older setup wiki points readers to its Dedicated Server Utils documentation for newer installations. On a managed game plan, use the supported panel workflow instead of running an upstream Docker or installation script inside the game container.
Test the parts your group uses
Choose a short route through your world: spawn, shared storage, a modded crafting station and a place with modded tiles or entities. Ask a tester to connect using the intended client pack, follow that route, and note any missing items or errors. Compare the first relevant client and server errors before changing another setting.
Make a disposable change in the test world. Save, stop and restart the test instance, then check that it remains. A successful first join does not prove that saving and reloading works.
Approve the update or return to the backup
Keep a brief acceptance record: who joined, which features they checked, whether the restart test passed, and any unresolved errors. If the rehearsal fails, preserve the logs and keep the working live pack in place. Avoid removing a content mod from your live world as a quick experiment.
Once the test passes, schedule the live change and take a fresh backup after players disconnect. Keep the earlier working pack available until your group has played and saved through another restart. If you need help, send CloudExa support the release numbers, mod list and first error, with credentials removed.
Technical references: tModLoader’s server setup wiki and the project’s Dedicated Server Utils instructions. The rehearsal and approval process is CloudExa’s suggested workflow.