This is TShock 4.2.7 for Terraria 126.96.36.199. Included in this release is the Terraria Server API 1.17. Need help? Find us in Slack or here on the forums for support. Download via Github Releases.
Notable changes in TShock:
Notable changes in TerrariaServerAPI:
- SSC will now create & delete SSC data when accounts are added and deleted.
- When seeding the database for SSC, NetItem's max inventory size will be used rather than an arbitrary size.
- Added a permission, tshock.godmode.other, which grants a player the ability to grant god mode to another player.
- Added silent command prefixes, with limited support in TShock commands. The silent command prefix, set in the config file, defines the prefix to be used when executing a command silently. For example, /bloodmoon vs !bloodmoon will either output to the originating player only, or the entire server.
- TShock now saves the world when the last player exists.
- TShock now changes the window title to reflect an empty server when the last player exits.
- Added support for logging to the database, in addition to a text file.
- Changed the version command to no longer return the active and maximum players on the server.
- Removed all deprecated TShock methods that were kept for more than one version back.
- Console title now says "TShock for Terraria," not "TerrariaShock." Removed ASCII startup logo.
- Re-added stat tracker.
- The /stats command has been renamed /serverinfo.
- Added hooks for region enter, region exit, region creation, and region deletion.
Page 11 of 13
Created by Maka
- Mar 7, 2015
When we started the TShock project, we always had some form of realtime chat. This ranged in purposes, from support to just general chatter. We've used two IRC networks, irc.shankshock.com (our self hosted solution) and Rizon, but both require complex clients to setup and use in any effective manner. When we upgraded to XenForo 1.4.5, we lost the ability for EzIRC to relay chat to IRC, and at the same time realized we no longer had control over the #tshock channel on Rizon. From there, we silently switched to using the shoutbox for chat, but this proved to be more than unstable -- chat messages would be delayed, and using the shoutbox was a frustrating experience from mobile.
From all of this, we've decided to move to Slack, a high powered real time chat application for teams. You have to register an account, but you can add a profile photo and join several different channels for discussing TShock in there. We have a support room, so you can ask for help, and everything is archived and chat can be viewed several days back. It's searchable, and it has custom emoji, just like the forums.
You can sign up using the banner on the right hand side of the forums. It sends you an invite, and you can login and chat with everyone. If you're a plugin developer, you can chat with only the TShock developers directly if you like, and you can request a channel (via the concierge channel) for your own plugins too.
I'm excited to see the possibilities you come up with. Here's what it looks like:
Oh yeah -- this means that you won't be seeing any more updates to the shoutbox archive. I've got more time to go stop the madness from spreading, though, so that's a good thing!
See you all later!
Created by nicatronTg
- Mar 2, 2015
This is primarily news for plugin authors: Next week, on Monday, March 9th, we will be releasing TShock 4.2.7 and TerrariaServer-API 1.17. Because this changes the API version, we're giving an advance heads up.
On Friday, March 6th, we will be locking out plugin submissions for the 1.16 API release. During the weekend, you can submit plugin updates that ensure compatibility with 1.17. They will be held in the moderation queue (unapproved) until the API release on Monday. This will allow plugin authors to publish the newest versions of their plugins for the API change while not breaking compatibility with 1.16 until we push the release forward.
Once 1.17 is released, we will continue to allow 1.16 plugins to persist in RM for a short while, but they may be tagged unsupported or abandoned if no activity/development happens to upgrade in a long duration following the release.
In other news, we've cleared out the plugin release forum of all non-resource manager plugins (side for @MarioE's work). Plugin authors who have not upgraded to RM should do so to get their threads moved back into the plugin release discussion forum.
Created by nicatronTg
- Feb 28, 2015
Since we've added Resource Manager, we now have the capability of hosting more than TShock addons, but tools made by the community as well. We have traditionally allowed for plugins to be posted only with source code, for the following benefits:
- To encourage community development and contribution.
- To allow resurrection of plugins from older API versions and to promote them for newer releases of TShock.
- To encourage security by allowing audits of publicly released code.
Please provide feedback as to whether or not we should allow closed source plugin and tool releases by voting in this poll and discussing the ramifications.
Created by Olink
- Aug 9, 2014
For those that were not around when this project was initially created (about a month before 1.2), White Lotus is a project that bridges the gap between user and server in terraria, by allowing you to link actual TShock accounts to a Steam account.
How it works
- You define a group, for users that are Steam Authed via White Lotus, and you give them the permissions that you want only Authed users to have (such as building).
- You sign up at our website and create a server account. This account allows you to customize your rest ip/port, default group, unique identifier, and other things.
- A user joins your server. He is put into whatever your guest group is. It is up to you as the server owner if you wish to restrict their permissions etc.
- A message is broadcasted to the user mentioning that this is a White Lotus server and that they need to create an account @ White Lotus to gain benefits on your server.
- The user goes to White Lotus
- User logs into steam, via steams web api, and we get a token back from steam confirming who they are.
- User puts in the unique key you defined when you created your server.
- User enters username and password. Only the username is stored on our database, the password is sent to Tshock for the user creation step.
- The user can now log into their account on your TShock server.
- You can now ban that user, using TShocks commands, or using the steamban feature. The steam ban feature will ban that steam id from being used on your server ever again. This will prevent proxies, name changes, uuid changes, etc.
- You can optionally enable the global ban feature. If a user creates or logs into a steam account where their steam id is banned on more than 'x' servers (your threshold) they are auto steam banned from your server. You can also simply enable notifications, which broadcast a message to everyone on your server with a certain permission that the user has 'x' global bans....
Page 11 of 13