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 glitchesTShock permissions are node-based, not title-based: a player can run a command only when the player’s account belongs to a group that has the required permission, directly or through a parent group. This lets you create a moderator who can kick and mute without granting group-management or world-editing powers.
Playing with friends? Godlike.Host runs hosted Terraria servers from 10 data-center locations, with free DDoS protection.
This guide covers first-time setup, everyday command syntax, the permission nodes behind common commands, least-privilege group design, REST/API access, and the checks that fix most “you do not have permission” errors. Command names and nodes can change between releases, so verify them against the TShock version installed on your server.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What TShock adds to a Terraria server
TShock is a server-side Terraria toolbox. It adds account and group management, permission-controlled commands, server-side characters, anti-cheat features, item bans, regions, warps, and world-management utilities. The important administrative distinction is that TShock does not treat a group named “admin” as automatically privileged. Capabilities come from permission nodes assigned to that group.
That model separates identity from authority. A player may be in a group called moderator, but the name itself grants nothing. If the group has tshock.admin.kick and tshock.admin.mute, those actions work; if it lacks tshock.admin.group, the same moderator cannot manage groups. This is the basis for safer, narrowly scoped roles.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
First-time setup: create the owner account
Run the initial setup from the server console and the game client in the following order. The setup account has all privileges, so protect it with a unique, strong password and do not use it for ordinary play.
- Start the TShock server. Read the setup code printed in the server console.
- Join the server with a Terraria client.
- In chat, run
/setup [setupcode], replacing the brackets and placeholder with the code shown by the console. - Create the first privileged account with
/user add [username] [password] owner. - Authenticate that account with
/login [username] [password]. - Run
/setupagain to finish the setup process.
Keep the owner-equivalent account for server administration. For regular moderation, create a separate account and place it in a custom group with only the permissions needed for that job.
Free tools Windows power users keep installed
One-click scans. No signup required.
Command prefixes and basic syntax
TShock’s default command prefix is /. Its default silent prefix is .; a silent command performs an action without displaying the normal command output to other players. Both specifiers are configurable, so use the prefixes configured on your server if they differ from the defaults.
Arguments shown in square brackets are placeholders, not characters to type. For example, /login [username] [password] means that you enter the actual account name and password after /login.
| Command | Purpose | Typical use |
|---|---|---|
/login [username] [password] |
Authenticate a registered account | Sign in before using account-specific privileges |
/user add [username] [password] [group] |
Create an account in a selected group | Create a moderator, builder, or administrator account during setup |
/user group [username] [group] |
Move an account to another group | Promote or demote a player without changing the group definition |
/group add [group] [permissions] |
Create a group | Define a role with an initial permission list |
/group addperm [group] [permission] |
Grant a permission to a group | Add one command capability without granting a broad role |
/group delperm [group] [permission] |
Remove a permission | Revoke an action while leaving other role settings unchanged |
/group list |
List groups | Check available roles and spelling |
/group listperm [group] |
Show a group’s permissions | Audit direct permissions before troubleshooting access |
/group parent [child] [parent] |
Set group inheritance | Let a specialized role inherit a deliberately chosen baseline |
How TShock permission checks work
A permission check follows this path:
- The player authenticates with
/loginif the command requires an account. - The account is associated with a TShock group.
- TShock checks whether that group has the command’s permission node.
- If the group has a parent, inherited permissions are considered as configured.
- The command runs only if the required node is present. A wildcard can grant broad access, but it also greatly expands the consequences of a mistake.
Group labels such as moderator or administrator are presentation choices. They do not create authority by themselves. Build roles by writing down the actions each role must perform, then assign only the corresponding nodes.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Core command-to-permission mappings
The following mappings are the practical starting point for in-game administration. Confirm spelling against the permissions reference for your installed release, particularly after an upgrade.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →| Action | Command | Permission node | What it allows |
|---|---|---|---|
| Kick a player | /kick |
tshock.admin.kick |
Remove a player from the server |
| Ban a player | /ban |
tshock.admin.ban |
Apply a ban through TShock’s ban command |
| Mute a player | /mute |
tshock.admin.mute |
Restrict a player’s chat activity through the mute command |
| Manage groups | /group |
tshock.admin.group |
Create, edit, inspect, and arrange groups |
| Manage regions | /region |
tshock.admin.region |
Use region-protection administration commands |
| Manage warps | /warp |
tshock.admin.warp |
Use warp administration commands |
| Save the world | /save |
tshock.world.save |
Trigger a world save |
| View world information | /world |
tshock.world.info |
Use the world-information command |
| Register an account | /register |
tshock.account.register |
Create a registered player account |
| Log in | /login |
tshock.account.login |
Authenticate a registered account |
| Maintenance and version actions | /checkupdates, /off, /restart, /version |
tshock.cfg.maintenance |
Run the listed configuration, shutdown, restart, or version commands |
These nodes describe access, not a guarantee that every command has identical arguments in every release. A successful permission check can still be followed by an argument, target, or configuration error.
Creating least-privilege groups
Start with roles that match real responsibilities rather than copying the owner-equivalent role. A small community might need member, moderator, builder, and administrator groups. The exact names are yours; the permissions determine the behavior.
Member
Use the default player role for ordinary gameplay. Give it only the account or world permissions that your server intentionally exposes. Do not add wildcard access merely to make routine commands work.
Moderator
A moderator commonly needs player-safety tools, not server configuration. A focused role can receive tshock.admin.kick and tshock.admin.mute. Add tshock.admin.ban only if moderators are expected to issue bans. Leave tshock.admin.group, maintenance, and world-editing permissions out unless the job explicitly requires them.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Builder
A builder role should be designed around the construction tools your server permits. Do not infer that a builder needs moderation or group-management access. If region administration is required, assign tshock.admin.region separately and document why.
Administrator
An administrator may need a wider combination of moderation, region, warp, world, and maintenance nodes. Prefer an explicit list so an administrator’s scope remains reviewable. Reserve the owner-equivalent role for the few accounts that must manage every part of the server.
Adding one permission without making a player superadmin
To give one player one capability, create or use a narrowly defined group, add the single node, then assign the player to that group. For example, a “chatmod” role can be limited to mute access:
- Create the group, using the group command syntax supported by your release:
/group add chatmod. - Grant the node:
/group addperm chatmod tshock.admin.mute. - Assign the account:
/user group [username] chatmod. - Audit the result with
/group listperm chatmod.
If your installed version requires a permissions argument when creating a group, provide the release-specific form shown by its command help, then use /group addperm for subsequent additions. This avoids giving the account a wildcard or owner-equivalent role just to enable one action.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC 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 & 11Inheritance: useful, but deliberate
/group parent [child] [parent] makes a child group inherit permissions from a parent. Inheritance is useful when several roles share a stable baseline. For example, a moderator could inherit member permissions and add kick and mute nodes.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Inheritance also makes effective permissions less obvious if it is layered repeatedly. Keep the hierarchy short, document why each parent exists, and inspect the child with /group listperm [group]. When removing access, check both the child’s direct permissions and every parent; deleting a direct node cannot remove a capability still inherited elsewhere.
Wildcard permissions and why to avoid them by default
The versioned group guide documents * as a wildcard group target for permission assignment. A wildcard is convenient for a trusted owner-equivalent role, but it grants a broad set of capabilities at once. It can unintentionally include destructive maintenance, group-management, world, or REST actions as new permissions are introduced in later releases.
- Use individual nodes for moderators and builders.
- Use inheritance for shared, reviewed baselines.
- Keep wildcard access restricted to accounts that genuinely need full control.
- Review wildcard groups after every TShock upgrade.
Prefixes, suffixes, and chat presentation
The group guide also supports optional presentation settings such as prefixes, suffixes, and RGB chat colors. These settings help players recognize roles, but they do not replace permission nodes. A colored “Moderator” label is not evidence that tshock.admin.kick is present; verify the group’s permissions directly.
REST/API permissions are separate
REST access belongs to a separate family of nodes. In-game moderation permission does not automatically mean that an API client should be able to perform the same action. Grant REST capabilities independently and use the narrowest node needed by the integration.
| REST node | Scope | Least-privilege guidance |
|---|---|---|
tshock.rest.command |
Run raw TShock commands through REST | Use only when an integration truly needs arbitrary command execution; it is broader than a single-purpose endpoint |
tshock.rest.groups.manage |
Manage groups through REST | Reserve for trusted automation that must change roles |
tshock.rest.groups.view |
View group information through REST | Prefer this for read-only dashboards or audits |
tshock.rest.kick |
Kick through REST | Grant without group-management access when that is all the integration needs |
tshock.rest.cfg |
Configuration-related REST access | Keep separate from ordinary moderation and protect the API credentials |
Treat API credentials as administrative secrets. A service that only needs to kick should not receive raw command execution, group-management, or configuration nodes.
Why TShock says you do not have permission
A permission error usually means one of four things: the account is not authenticated, the account is in an unexpected group, the required node is absent, or inheritance is not what you think it is. Check in this order before granting broad access.
- Confirm the account. Run
/login [username] [password]and make sure you are using the registered account that was assigned the role. A guest or a different character may still be in the default group. - Confirm group membership. Check which group the account belongs to and correct it with
/user group [username] [group]if necessary. - Inspect direct permissions. Run
/group listperm [group]. Look for the exact node, including its spelling and punctuation. - Inspect parents. If the group inherits from another group, inspect each parent and verify that the intended node is actually inherited.
- Check the command’s release-specific mapping. Documentation is evolving, and some pages are versioned or marked as migrated. Use the permissions reference and command help for the release running on your server.
- Retest with the correct prefix. If the server changed its command specifier from
/, the command may be interpreted as chat text rather than a TShock command. Check the configured command and silent prefixes.
Do not solve an isolated failure by assigning a wildcard immediately. That hides the original cause and may give the account unrelated control.
Operational checklists
Before opening the server
- Complete the two-stage
/setupprocess and create the owner-equivalent account. - Use a strong, unique password for that account.
- Create custom groups for routine staff instead of using the owner role.
- Write down each role’s required actions and map them to nodes.
- Audit every group with
/group listand/group listperm [group].
When promoting a player
- Choose the smallest existing role that matches the job.
- Use
/user group [username] [group]rather than editing unrelated groups. - Check parent inheritance before adding a duplicate permission.
- Test the intended command and one command that should remain blocked.
After a TShock upgrade
- Confirm the installed release and compare its command help with your procedures.
- Recheck permission nodes for critical commands.
- Review wildcard groups and parent chains for newly introduced capabilities.
- Retest in-game and REST access separately.
Choosing between in-game commands and REST
| Need | Best interface | Reason |
|---|---|---|
| A staff member moderating while playing | In-game command | Uses the logged-in account and normal group permissions |
| A dashboard that only displays roles | REST with tshock.rest.groups.view |
Read-only access is narrower than management or raw commands |
| An automated kick workflow | REST with tshock.rest.kick |
Limits the integration to its single moderation action |
| An automation system that must change groups | REST with tshock.rest.groups.manage |
Explicitly grants role-management scope |
| Full server ownership | Owner-equivalent account and carefully protected administration | Broad control should not be exposed to ordinary staff or generic integrations |
Version compatibility and documentation limits
TShock’s project documentation is still evolving. Some pages are versioned or identified as migrated, and command details can differ between releases. Treat the current permissions reference as the starting point, then verify command spelling, arguments, and nodes against the release installed on your server.
Record your TShock version alongside your group definitions. When a command suddenly stops working after an update, compare the installed release’s help and permissions documentation before changing the role model. This is especially important for maintenance commands, wildcard groups, inherited permissions, and REST endpoints.
A practical permission design
A maintainable server can use a short hierarchy: a member baseline, a moderator child with kick and mute, and a senior administrative role with explicitly reviewed region, warp, world, or maintenance permissions. Keep group management separate from ordinary moderation unless staff genuinely need to create or alter roles. Give API clients their own narrowly scoped permissions rather than reusing a human administrator account.
Review the design whenever responsibilities change. The goal is not the fewest groups; it is a permission map that a new server operator can understand, audit, and repair without guessing.
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.
