Trial TShock server-side characters without risking player inventories

TShock server-side characters, or SSC, give the server control over character progress for that community. Enabling SSC changes what players bring into a session. Trial it in an isolated copy before deciding how an established group will move, especially if members have valuable inventories.
Define what the trial should prove
The TShock documentation explains that players start with fresh server-side characters and that their separate single-player characters remain unaffected. That does not mean you can switch a live community back and forth without planning. Decide whether your future server should require fresh progression or use an explicit, reviewed migration process.
You need a separate test instance with its own world copy and TShock data, plus permission to create that test instance. If your plan has no spare server, ask support for an isolated test route. Do not overwrite the production world or use the production account database as a shared writable database.
Prepare the isolated copy
Stop the source during a planned window and take a completed backup covering the world and TShock data. Keep that recovery point unchanged.
Have the test copy use its own assigned connection details and storage. Confirm that the source service remains distinct before starting it.
Open the test copy’s generated 
tshock/sscconfig.json. Match the path to your template if the working directory differs.
Record the current file and change the existing 
Enabled field to 
true. Preserve JSON syntax and leave unrelated settings alone.
Start the test service and check for configuration or database errors.
Use an ordinary account for the inventory check
Join with a disposable test character and a normal TShock account. Note its starting inventory, health and mana. Make a small, recognisable amount of progress, leave and reconnect, then restart the test server and reconnect again. Record whether the same server-side state returns.
SuperAdmin can bypass SSC through 
tshock.ignore.ssc, so testing only with that account can give the wrong impression. Use a normal account for proof rather than changing a powerful staff group just for this exercise. Keep the trial’s credentials private.
Check the character-save interval against your installed configuration. A world save and a character-data save are different recovery concerns. Your planned backup must cover the data your installation actually uses, including an external database if you configured one.
Make the production decision separately
Record the test version, starting rules, reconnect result and restart result. Explain to players what will happen to their inventory on the SSC server before scheduling a live change. Do not promise an automatic import unless you have verified a supported process for your exact TShock version.
For a failed trial, stop the test instance and retain the logs. The source server should need no rollback because you did not change it. If you later enable SSC in production, take another recovery point and agree how you will handle progress made after that cutover. A full restore can rewind both the world and player data.
Related CloudExa help
Set up TShock accounts and limited administrator permissions
Back up game files before making changes
Open a support ticket
Official references
TShock server-side character configuration