Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
TShock is the best starting point for most modded Terraria servers. It supplies the server-side foundation that plugin additions depend on: anti-cheat controls, server-side characters, groups, granular permissions, item bans and a broad command set. Install the release that matches your Terraria build, extract it into a persistent directory, complete the first-run owner setup, and then add only plugins whose permissions and progression effects you understand.
What TShock provides before you add any plugin
TShock is described by its Pryaxis documentation as “a toolbox for Terraria servers and communities.” That description is useful because TShock is not just one feature or a cosmetic extension. It is a server layer that changes how players authenticate, how staff powers are delegated, how cheating is controlled and how administrative actions are recorded and performed.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitches| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
505 Games Terraria 71501866 | $17.37 | Buy on Amazon |
| 2 |
|
Terraria Boss Rush: Hardmode Edition T-Shirt | $19.99 | Buy on Amazon |
| 3 |
|
Terraria Bunny Plush | $17.78 | Buy on Amazon |
| 4 |
|
Terraria PS Vita Game | $40.99 | Buy on Amazon |
| 5 |
|
CyberPowerPC Gamer Xtreme VR Gaming PC, Intel Core i5-13400F 2.5GHz, GeForce RTX 5060 8GB, 16GB... | $1,285.00 | Buy on Amazon |
Its core scope includes anti-cheat tools, server-side characters, groups, permissions, item bans and many commands. Those built-in systems often solve the problems that lead administrators to install several small plugins. A plugin should therefore fill a genuine gap rather than duplicate a TShock permission or command.
For a private world, you may use only a small part of this stack. A public or semi-public server normally needs all of it: a protected owner account, carefully scoped moderator groups, progression rules, a recovery plan and a safe way to perform routine administration without giving every helper unrestricted control.
#1 Best Overall
- In Terraria, every world is unique-from the floating islands in the sky to the deepest level of The Underworld. Adventure to the ends of the earth, and defeat villainous bosses along the way. The world is your canvas!
Check compatibility before installing
Version matching is the first decision. The current release information in the supplied Pryaxis material lists TShock 6.2.1 for Terraria 1.4.5.8. Treat that as a compatibility pairing, not as a promise that every older or newer Terraria build will work unchanged. Check the release page for the exact Terraria version installed on the server before copying files or enabling plugins.
| Component | Current compatibility fact | Required action |
|---|---|---|
| TShock | 6.2.1 | Use the release archive that matches the server’s Terraria version. |
| Terraria | 1.4.5.8 | Confirm the server is running this build, or select the corresponding TShock release instead. |
| Upgrade data | tshock.sqlite and the tshock folder are specifically called out for backup. |
Preserve the database and configuration data before replacing installation files. |
Do not assume that a plugin compiled for one TShock or Terraria build will load on another. A version mismatch can appear as a startup error, a missing command, broken permissions or behavior that is worse than a clean failure. Record the exact Terraria and TShock versions in your server change log so that every plugin decision can be checked against them.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Install TShock in a persistent server directory
The official getting-started guidance warns against running TShock directly inside the compressed archive. That approach can leave settings in a temporary location or discard them when the process ends. Extract the complete release into the directory that will hold the live server and launch the TShock server executable from there.
- Back up the existing installation. Copy the world files and the TShock data before an initial installation or upgrade. For an existing server, include
tshock.sqliteand the entiretshockfolder, as well as your normal world backup. - Verify the release pairing. Confirm that the archive is intended for the Terraria version you plan to run. If the release page identifies a different pairing, stop and resolve that mismatch first.
- Create or choose the permanent server directory. Use a location that will remain available to the operating-system account running the server and that is included in your backup schedule.
- Extract the archive completely. Do not launch the executable from inside the compressed file and do not leave configuration files in a downloads or temporary folder.
- Start the TShock server executable from the extracted directory. Allow the first-run process to create its data and configuration files. Keep the server process attached to the directory you intend to back up.
- Complete first-run setup. Create the owner account when prompted, record its credentials securely and use it only for tasks that require owner-level authority.
- Stop and restart once. A controlled restart confirms that settings survive the end of the process and that the server is reading the persistent files rather than a temporary archive location.
- Test with a non-owner account. Join with an ordinary player account and verify that login, building and the normal gameplay loop work before installing optional plugins.
The restart test is especially important on a new installation. If a setting disappears after shutdown, the server is not using the persistent directory correctly; fix that before you trust the world or install additional extensions.
Set up ownership and groups around least privilege
TShock’s permission reference is granular enough to separate routine moderation from destructive administration. Start with the owner account, then create ordinary player and moderator groups based on actual duties. Do not give a helper an unrestricted group merely because it is convenient.
Owner account
Reserve the owner account for installation, upgrades, permission changes, configuration and emergency recovery. Keep its credentials out of chat, scripts and shared staff documents. Use a separate moderator identity for everyday play so that a compromised session does not automatically expose every administrative capability.
Recommended Free Tools
Player group
The default player experience should contain only the commands needed for normal participation. Decide explicitly whether players may use warps, teleport controls, whispers, party chat or other convenience commands. Convenience is not automatically harmless: teleportation can bypass exploration, and item-spawn powers can undermine a survival economy.
Rank #2
- Gaming Boss Battles design. Boss Rush: Hardfashion Edition items are perfect for fans of Terraria or anyone who likes cool video game clothes! These Terraria items feature the hardmode bosses and is a great way to show your enthusiasm for Terraria!
- Part of the official Terraria merchandise line from Re-Logic, the creators of Terraria! If you are a terraria fan or should know one, get this design to give yourself or others who play terraria a great gift.
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
Moderator group
Build moderator permissions from a checklist of duties. A moderator who handles chat and routine player disputes may need communication, kick or mute powers but not world modification, item spawning or configuration access. A builder may need protected build areas without ban or shutdown authority. Review every node before assigning it.
Must-have capability categories
The following categories are the practical baseline for a public or semi-public server. Some are already part of TShock; a third-party plugin is worthwhile only when it adds a needed behavior without weakening these controls.
Moderation and anti-cheat
Anti-cheat tools, item bans, groups, permissions and administrative commands form the first safety layer. Use them to define what can enter the server, who can act against disruptive players and which items or projectiles are prohibited. Moderation policy should be written before launch: identify offenses, the staff action available for each offense and the person allowed to reverse that action.
Item bans deserve special attention on progression-focused worlds. A ban is not merely a technical setting; it changes what players can obtain and trade. Test banned items and projectiles with an ordinary account, then check that trusted staff can still perform legitimate maintenance without granting those powers to everyone.
Granular permissions and groups
Permissions are the control plane for TShock. The reference includes nodes covering bans, broadcasts, building protection, world modification, teleports, spawning, server-side characters, saves and other actions. Use those nodes to create narrow roles rather than a single “staff” group with every command.
- Communication: broadcast, whisper and party-chat functions can be assigned separately from punishment powers.
- Player actions: kick, mute and ban authority should be separated where possible, with permanent or high-impact actions limited to trusted operators.
- World actions: building protection and world modification are different responsibilities. A person who protects a region does not necessarily need the ability to alter the whole world.
- Progression actions: teleport and spawning permissions can change the economy and exploration rules; enable them only where the server policy allows it.
- Data actions: save, server-side-character management and configuration-related permissions should stay with operators who understand recovery procedures.
Player convenience
Warps, spawn and teleport controls, whispers and party chat can make a survival community easier to use. They also create policy choices. A server that promises earned progression may allow communication and spawn access while withholding teleport or item-spawn powers. A creative or event server may make the opposite choice.
Write the rule beside the permission. For example, “teleport is available after a player reaches the community milestone” is more enforceable than “teleport is allowed for regulars.” When a plugin adds a convenience command, map it to the same progression rule instead of creating an unreviewed exception.
Rank #3
- Product Type:Toy Figure
- Item Package Dimension:11.6 cm L X 14.4 cm W X 15.8 cm H
- Item Package Weight:0.1 kg
- Country Of Origin: China
Server-side characters and progression controls
Server-side character upload and management controls help a server enforce a consistent progression model. They matter most when players would otherwise bring items or characters from outside the world. Combine these controls with banned-item and banned-projectile permissions, and explain to players what is retained on the server and what behavior is prohibited.
Do not treat server-side characters as a substitute for backups. They regulate how characters are used; they do not protect the world or database from deletion, corruption or an incorrect upgrade.
REST automation
TShock’s REST documentation describes authenticated routes for raw command execution, MOTD access, server shutdown and other management functions. REST permissions include tshock.rest.command and tshock.rest.maintenance, along with separate nodes for configuration, broadcasts, kicks, bans, mutes, kills, events and player information.
REST is useful for a dashboard, scheduled maintenance or an alerting bot, but it is equivalent to granting an administrative control surface. Store the token as a secret, never paste it into public code or chat, and grant an automation client only the routes it actually calls. A status bot should not receive shutdown, ban or raw-command permission.
Permission design worksheet
Use this worksheet when creating groups. It keeps the decision tied to a job instead of to a person’s seniority.
| Capability area | Typical decision | Risk to review |
|---|---|---|
| Bans and mutes | Assign to trusted moderators; separate temporary discipline from permanent action. | Abuse or an irreversible punishment applied without review. |
| Broadcasts and chat | Allow staff who announce events or handle player communication. | Spam, impersonation or announcements that disrupt play. |
| Building protection | Give region managers protection tools without granting global world powers. | Protected areas that cannot be repaired or recovered by anyone except the owner. |
| World modification | Restrict to operators responsible for maintenance and event preparation. | Accidental destruction or a progression-changing edit. |
| Teleport and warps | Enable according to the server’s exploration and economy policy. | Bypassed travel, inaccessible loot or unfair event access. |
| Spawning | Reserve for approved events, testing or creative worlds. | Items and enemies entering the economy without oversight. |
| Server-side characters | Keep upload and management with operators who enforce progression rules. | Imported items or characters invalidating the world’s rules. |
| Saves and maintenance | Assign to the smallest group that performs backups, saves and recovery. | Interrupted saves or changes made without a rollback plan. |
After assigning a group, test it with a disposable account. Exercise each allowed action and attempt one prohibited action. A permission design is not complete until both tests produce the expected result.
How to judge an additional plugin
There is no universal list of “best” third-party plugins because compatibility and server policy determine whether an extension is beneficial. Compare every candidate on five axes.
Rank #4
- 14 Different environments (including dungeons, floating islands, jungles) that go to the extremities of the earth, up in the sky and all the way down to the very deepest depths of the world.
- Hundreds of weapons, armour and other items to craft, with character advancement.
- Explore to find different materials and make exotic potions, laser guns, magic wands, flamethrower, diving gear, speed boots, grappling hooks, chainsaws, magic mirrors, etc.
- 29 Different block types to build whatever you imagine!
- NPCs and a swarm of enemies (over 150 types) including goblins, wyverns, unicorns, and-GASP-clowns!
1. Exact build compatibility
Check the plugin against the precise Terraria and TShock versions running on the server. A plugin that worked on an earlier release may fail after an upgrade even if its feature description has not changed. Keep the plugin package and its version in the same change record as the TShock release.
2. Permission granularity
Prefer extensions that expose separate permissions for separate actions. If a plugin grants a single broad permission for configuration, spawning and moderation, it is harder to fit into a least-privilege design than one with narrowly scoped nodes.
3. Effect on progression and economy
Classify the feature before enabling it. Does it create items, move players, alter world state, bypass character restrictions or change what a player can obtain? Compare that effect with your written rules. A quality-of-life feature may be excellent for a community server and wrong for a strict survival server.
4. Operational overhead and recovery
Identify every file the plugin creates, whether it writes to the database, how it stores configuration and what happens when it is removed. Include those files in backups and test a restore. A small feature is not low-risk if it can corrupt the database or leave irreversible world changes.
5. Whether TShock already covers the need
Check the built-in command and permission references first. Duplicating a native feature adds another update dependency and another place for permissions to drift. Install an extension when it provides a distinct capability, not merely a second interface for an existing command.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Remote administration without exposing the server
REST can reduce the need to log in to the host, but convenience should not expand authority. Design the integration in this order:
- List the required operations. A monitoring client may need player information and MOTD access; a maintenance tool may need a narrowly scoped maintenance route.
- Create a dedicated automation identity or permission set. Do not reuse the owner account’s token.
- Grant only the relevant REST nodes. Keep
tshock.rest.commandandtshock.rest.maintenancedisabled unless the client genuinely requires raw commands or maintenance operations. - Store the token outside source code. Treat it like a password. Rotate it if it appears in a log, screenshot, repository or chat message.
- Test harmless reads first. Confirm that the client can retrieve the intended information and receives a denial for an operation it should not perform.
- Log and review actions. Record who or what invoked bans, shutdowns, configuration changes or raw commands, and remove the integration if it is no longer maintained.
Do not expose a broad REST interface merely to support a simple status page. Narrow permissions reduce the damage a stolen token can cause.
Best Value
- System: Intel Core i5-13400F 2.5GHz 10 Cores | Intel B760 Chipset | 16GB DDR5 | 1TB PCIe 4.0 NVMe SSD | Windows 11 Home
- Graphics: NVIDIA GeForce RTX 5060 8GB Graphics | 1x HDMI | 2x DisplayPort
- Connectivity: 1 x USB-C 3.2 | 2 x USB-A 3.2 | 6 x USB-A 2.0 | 1 x LAN | WiFi 6 | Bluetooth 5.3 | 7.1 Channel Audio
- Tempered Side Case Panel | Custom RGB Lighting | Keyboard and Mouse
- 1 Year Parts & Labor Warranty, Free Lifetime Tech Support
Upgrade, backup and recovery procedure
The release notes call for a complete backup before replacing files with a new archive. At minimum, preserve the world, tshock.sqlite and the tshock folder. Keep a dated copy outside the live installation so that replacing files cannot destroy the only backup.
- Stop the server cleanly and confirm that the process has ended.
- Copy the world files,
tshock.sqliteand thetshockfolder to a dated backup location. - Record the old Terraria and TShock versions and the list of enabled plugins.
- Extract the new release into the live server directory, preserving the backed-up data until the upgrade is proven.
- Start the server and watch for plugin-load, database or permission errors.
- Join with an ordinary account and test login, building, communication and any progression-critical behavior.
- Test a moderator account and the REST client, including a denied operation that should remain unavailable.
- If the upgrade fails, stop the server, restore the previous installation and data, and investigate one change at a time.
Never delete the old backup immediately after a successful boot. A problem may appear only when a player uses a less common command or when a scheduled automation task runs.
Troubleshooting the common failures
Settings disappear after shutdown
The most likely cause is launching from inside the archive or from a temporary extraction path. Move the complete installation to the persistent server directory, launch the executable there and repeat the stop-and-restart test.
The server will not start after an upgrade
Recheck the Terraria/TShock pairing, restore the pre-upgrade backup if necessary and start without newly added plugins. If the base server starts, add extensions back one at a time so that the incompatible component is identifiable.
A moderator has too much power
Review the group’s permission nodes rather than adding exceptions blindly. Remove world modification, spawning, teleport, save or REST permissions that are not part of the moderator’s job, then retest with a disposable account.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteA player can bypass progression
Audit teleport, spawning, server-side-character and banned-item permissions together. A single convenience permission may be harmless in isolation but undermine the policy when combined with another command or plugin.
A REST integration can perform unexpected actions
Revoke or rotate its token, remove broad REST nodes and rebuild the permission set from the client’s actual operation list. Test both an allowed request and a deliberately denied request before restoring automation.
A practical launch checklist
- Terraria and TShock versions are a documented compatible pair.
- The archive was extracted into the permanent server directory.
- A clean backup contains the world,
tshock.sqliteand thetshockfolder. - The owner account is separate from everyday moderator accounts.
- Player, moderator and operator groups have explicit, tested permissions.
- Teleport, spawning, item bans and server-side characters match the written progression policy.
- Every additional plugin has a compatibility check, permission review and recovery plan.
- REST tokens are secret, scoped and tested against denied operations.
- A restart confirms that settings persist and the server can be restored if the upgrade fails.
The Bottom Line
For most Terraria communities, the best plugin strategy is to install the matching TShock release, use its built-in anti-cheat and permission systems as the baseline, and add only narrowly scoped extensions that survive compatibility, progression and recovery checks.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →
