TeamSpeak Server can get really messy, if they have a lot of channels. This simple bot will help you a bit, organizing your TeamSpeak Server.

1. A TeamSpeak 3 Server (obviously)
2. A (v)Server, where you can run this bot
3. A query login
4. The TS3 Query data (IP, Port, etc)

As you've might expected, setting up this kind of bot, will take some effort. But it shouldnt take longer then 10-15 min. at max., so lets get started.

Before starting with this bot, you have to set up your TeamSpeak 3 Server. Read carefully, otherwise the bot will not work as expected! As a reference and example, this is how your server could look like, when you're starting:

So when connected to your server, click on "Tools" -> "ServerQuery Login". In this window enter a username for your bot (i.E. tsbot).

Then press ok and a username and password field will show up. You can use this in your .env file as TS_USERNAME and TS_PASSWORD.

By default you'll need to setup 2 server groups:

1. The first one is a team group, this is a group every supporter, developer, mapper, ... needs to have. Otherwise the bot will not recognize your team members. The group does not need any fancy rights, its just for the bot. This is for the TS_TEAM_GROUP setting, in your .env file
2. The second group is a standby group, which will be assiged when a supporter/developer/... will give its spare time, to support users. Like on 1st, this group does not require any special rights. This is for the TS_SUPPORT_GROUP setting, in your .env file

After you've setup your groups, you'll need to create a channel on your server, where your staff can go on- and off duty (TS_REGISTRATION_CHANNEL). This channel can be anywhere on your server, but if you take my advice: place them on top of your support channel.

Managed channels are channels, who are managed by your bot. This can be Team-, Support-, Talk- or even Game channels. Due its complexity, there are no declaraions inside the .env file. You'll find these inside the src/bot/plugins/channelbot.ts file, starting at line 15.

private _managedChannels: IChannelDefinition[] = [
        { pattern: 'Team #', upperChannel: 'Team-Talk' },
        { pattern: 'Support #', upperChannel: 'Support' },
    ];

Every managed channel has 2 parameters a pattern and an upperChannel. The upperChannel is the parent channel, where all child channels will be created in a numeric order with the given pattern. So if the pattern is i.E. "Support #", the channel names will be Support #1, Support #2, Support #3, ...

After you've setup your your managed channels, you'll also need to setup the waiting area. This is the area, your regular users will join, to get support. This can be one or more channels. The configuration can be done inside the file src/bot/plugins/supportbot.ts at line 18.

private _managedSupportChannel: string[] = ['Waitingroom', 'Appointment'];

After setting all up, you have to build/transpile the code to plain js. You can do that via npm run build, when the build has finished, you'll end up with 2 files in the build directory. The first one is bundle.plain.js this file is for local debugging, the second one is the minified and obfuscated version of the code. You don't need your node_modules folder, because everything is baked into this file.

There is an easy way to test if everything works as expected. Just run:

npm run debug

If there were any errors, you'll see it.

To get the script running, just copy the bundle.js & .env file to your server and run it.