
*) Click the Export button at the top of the Identities window and save the. This ONLY applies to non-MC players.Īgain, this is being done to prevent trolls, music spammers, etc from causing issues and to enhance your TS3 experience!

If you have a friend or know someone that doesn't play MC you can submit a request with their TS UID (see instructions below) to a Staff Member to be verified. This can be done on either the 1.6 or 1.7/1.8 lobby (see instructions below). You will now only be able to join the Lobby (normal muted one) and Other Games channel until you verify your account. This is to provide a better experience for both players and staff.

The Discord backend has also seen several of additions - you can for example now bind server roles to SinusBot accounts just like you can bind them to server groups on TeamSpeak.Due to recent issues with trolls, spammers, etc we are adding additional security to the TS3 server. We've integrated the Native Client functionality from the Chromium project into the bot - that means that you can use the same offline TTS engine you probably know from the Chrome browser or your Android phone. Just add or modify the ExternalFileBase in your config.ini to point to your music directory. Or if you want to use (S)FTP to manage your files, you can use that as well. This means that if you already have your music collection on the server, you don't need to manually import it into the bot anymore. With version 1.0 you can store files outside of the bot itself and have the bot "import" and use them on-the-fly. Please be careful when installing scripts, especially when they want to use the restricted modules. When previously you had to edit your config.ini to specifically allow a script to access a database or the filesystem, you can now view the required privileges of a script and accept them automatically when you activate it - just like you do with apps on your phone. More info can be found in the changelog of Alpha 1.įor users of scripts, it has been made easier to grant a script permission to use restricted modules. This comes with a couple of changes that script authors need to adapt their scripts to. The change will bring many advantages such as ES6 compatibility and an increased control over the resources used by it. The scripting engine has been changed to v8 - that's the engine that also powers the Chrome browser and node.js.

This entry might change until the 1.0 version has become stable.
