TeamSpeak System
The TeamSpeak System allows managers to store the guild's TeamSpeak server address and password in the bot, so any registered member can retrieve this information instantly with a Discord slash command.
Table of Contents
- System Overview
- Discord Commands (Members)
- Permissions
- Dashboard Setup (Managers)
- Multiple Servers
- Testing the Configuration
- Troubleshooting
System Overview
The TeamSpeak System is a simple but essential module. It stores one TeamSpeak configuration per Discord server and exposes it via Discord slash command, restricted to registered guild members only.
- One configuration per Discord server.
- IP and password are stored securely in the database — they are never exposed in a public channel.
- The response to the command is always ephemeral (only visible to the user who ran it).
- Server setup (
/setup start) must be completed before saving TeamSpeak information.
Discord Commands
Any member with the registered member role can use either command:
/teamspeak
/teamspeak
Returns a Discord embed with the TeamSpeak server address and password.
/ts
/ts
Alias for /teamspeak. Identical behavior, shorter to type.
What the embed shows
| Field | Value |
|---|---|
| Server IP/Address | The TeamSpeak address configured by management |
| Password | The server password, or "No password set" if none is configured |
Permissions
| Who | Can do |
|---|---|
| Any registered member (has the configured member role) | Use /teamspeak and /ts to retrieve server info |
| Managers / Administrators (dashboard access) | Configure and update the TeamSpeak settings in the dashboard |
Dashboard Setup
Configure TeamSpeak from the Dashboard. You need to have management access for the guild.
Step by step
- Open the dashboard and select your Discord server.
- Click TeamSpeak in the sidebar.
- Fill in the Server IP/Address field. This is required.
- Fill in the Password field. This is optional — leave it empty if the server has no password.
- Click Save Configuration.
/teamspeak, they will receive the updated information.
Fields
| Field | Required | Description |
|---|---|---|
| Server IP/Address | ✅ Yes | The IP address or domain of the TeamSpeak server (e.g. ts.myguild.com or 192.168.1.100) |
| Password | ❌ Optional | The server password. Leave blank if none is required. |
Multiple Servers
If your guild uses more than one TeamSpeak server (for example, one for each time zone or sub-group), you can list all of them in the same configuration field. Simply put each IP on a new line and each password on the corresponding new line.
Example — 3 servers, 3 passwords
# Server IP/Address field:
ts.na.myguild.com
ts.eu.myguild.com
ts.asia.myguild.com
# Password field (same order as IPs):
passwordNA
passwordEU
passwordASIA
When members run /teamspeak, the embed will display all lines exactly as entered,
so they can identify and connect to the correct server for their region.
Example — servers without password mixed with servers with password
# Server IP/Address field:
ts.na.myguild.com
ts.eu.myguild.com
# Password field:
passwordNA
(no password)
Testing the Configuration
After saving, you can verify the configuration is correct before announcing it to members.
How to test
- Go to Dashboard → TeamSpeak for your guild.
- Scroll down to the Current Configuration section.
- Click Send Test Message.
- The bot will send the TeamSpeak embed to a text channel in your Discord server (preferably a general, test, admin, or bot channel).
- Head to that channel in Discord and confirm that the IP and password look correct.
Troubleshooting
"You need the [role] to use this command"
The member does not have the registered member role. They need to complete registration with
/register first, or an admin can use /force-register on their behalf.
"TeamSpeak information has not been configured for this server yet"
No configuration has been saved for this server. A manager must open Dashboard → TeamSpeak and fill in the Server IP/Address and save.
"The member role is not configured"
The bot setup (/setup start) has not been completed. Complete the server configuration first
before using the TeamSpeak module.
Test message went to a wrong channel
The test message is sent automatically to the first available text channel named "general", "test", "admin", or "bot" that the bot can access. If none of those channels exist, it falls back to the first available text channel. To control where the test message goes, temporarily rename a channel to contain one of those keywords, run the test, then rename it back.
Test button shows "No TeamSpeak configuration found"
The Current Configuration section only appears after a configuration has been saved. Fill in the Server IP/Address field and click Save Configuration first.